Provides a quick summary of active feature development status and progress.
Install
mkdir -p .claude/skills/status-dilhanz && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/13327" && unzip -o skill.zip -d .claude/skills/status-dilhanz && rm skill.zipInstalls to .claude/skills/status-dilhanz
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Show feature progress and status across all featuresKey capabilities
- →Check if `.planning/features/` exists
- →List all feature directories
- →Extract feature name, status, and problem summary from `CONTEXT.md`
- →Extract total tasks and done tasks from `PLAN.md`
- →Identify the current phase and its status from `PLAN.md`
- →Note verification status from `VERIFY.md`
How it works
The skill reads local feature files (`CONTEXT.md`, `PLAN.md`, `VERIFY.md`) within the `.planning/features/` directory to extract and display the status, progress, and problem summaries of all active features. It also identifies the current development phase and suggests the next step.
Inputs & outputs
When to use status
- →Check project progress
- →View status of all active features
- →Monitor phase completion
About status
Reads local feature files to generate a formatted status table. It tracks overall task completion, current development phase, and verification status for all ongoing projects.
Show feature progress and status across all features
When not to use it
- →When asking about git status
- →When asking about non-Ship topics
Limitations
- →The skill relies on the `.planning/features/` directory structure
- →Information is extracted from specific markdown files (`CONTEXT.md`, `PLAN.md`, `VERIFY.md`)
- →Next step suggestions are based on predefined status transitions
How it compares
This skill automates the aggregation and presentation of feature progress and status from local files, providing a centralized and formatted overview, unlike manually checking individual feature documents.
Compared to similar skills
status side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| status (this skill) | 0 | 6mo | Review | Beginner |
| session-handoff | 13 | 4mo | Review | Beginner |
| spec-to-backlog | 8 | 5mo | No flags | Intermediate |
| create-handoff | 3 | 8mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by dilhanz
View all by dilhanz →You might also like
session-handoff
davila7
Creates comprehensive handoff documents for seamless AI agent session transfers. Triggered when: (1) user requests handoff/memory/context save, (2) context window approaches capacity, (3) major task milestone completed, (4) work session ending, (5) user says 'save state', 'create handoff', 'I need to pause', 'context is getting full', (6) resuming work with 'load handoff', 'resume from', 'continue where we left off'. Proactively suggests handoffs after substantial work (multiple file edits, complex debugging, architecture decisions). Solves long-running agent context exhaustion by enabling fresh agents to continue with zero ambiguity.
spec-to-backlog
atlassian
Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When Claude needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.
create-handoff
parcadei
Create handoff document for transferring work to another session
moai-workflow-project
modu-ai
Integrated project management system with documentation, language initialization, and template optimization modules. Use when setting up projects, generating documentation, configuring multilingual support, or optimizing templates.
granola-core-workflow-b
jeremylongshore
Post-meeting note processing and sharing workflow with Granola. Use when reviewing meeting notes, sharing with team members, or processing action items after meetings. Trigger with phrases like "granola post meeting", "share granola notes", "granola follow up", "process meeting notes", "granola action items".
reporting
comeredon
Final pipeline execution report format. Defines the structure, agent registry, Mermaid gantt chart, and change summary. Used by AnalystAgent in Phase 6.