Shep Kit:Status
Quick feature status and "what to do next" guide. Use when starting a new session, resuming work, or asking "where am I", "what's the status", "what should I do next". Gives a zero-to-hero walkthrough of the current feature branch. Part of the Shep autonomous SDLC platform — https://shep.bot
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Shep Kit:Status when an AI agent needs a reusable SKILL.md workflow for this job: Quick feature status and "what to do next" guide. Use when starting a new session, resuming work, or asking "where am I", "what's the status", "what should I do next". Gives a zero-to-hero walkthrough of the current feature branch. Part of the Shep autonomous SDLC platform — https://shep.bot
When not to use it
Skip Shep Kit:Status when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/shep-kitstatus # Save SKILL.md to ~/.claude/skills/shep-kitstatus/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/shep-kitstatus/SKILL.md. For a shared project, commit the folder at .claude/skills/shep-kitstatus/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Shep Kit:Status skill for this task: Detect current branch — git branch --show-current. Confirm any required inputs or files before making changes.
What supports this recommendation?
74/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 82/100
- Practical detail
- 74/100
- Source evidence
- 62/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Feature Status & Next Steps
Quickly orient the user on the current feature branch: what's done, what to try, and how to proceed.
## Workflow
1. **Detect current branch** — `git branch --show-current` 2. **Find the matching spec** — look for a `specs/NNN-*` directory whose `feature.yaml` branch field matches the current branch 3. **Read these files (in parallel):** - `specs/NNN-*/feature.yaml` — lifecycle, phase, progress, completed phases - `specs/NNN-*/tasks.yaml` — task list with states - `specs/NNN-*/spec.yaml` — summary, success criteria 4. **Read recent commits** — `git log --oneline -10` to see what was done 5. **Produce the status report** (see format below)
## Output Format
Present a concise, user-friendly status report using this structure:
``` ## [Feature Name] — Status
**Branch:** `feat/NNN-feature-name` **Phase:** <current phase from feature.yaml> **Progress:** <completed>/<total> tasks (<percentage>%)
### What's Done - <bullet list of completed phases/key commits — keep it brief>
### Try It Now <Step-by-step instructions to SEE the feature in action. Be specific:> 1. **Build:** `pnpm build` 2. **CLI:** `shep settings model` → pick a model 3. **CLI:** `shep feat new --model claude-opus-4-6 "test feature"` 4. **Web UI:** `pnpm dev:web` → open http://localhost:3000 → Settings → Model picker 5. **Tests:** `pnpm test` → all green
<Tailor these steps to the actual feature. Reference specific commands, URLs, UI paths, clicks.>
### What's Left - <remaining tasks or "nothing — ready for PR">
### Next Action <Single clear sentence: what the user should do RIGHT NOW> ```
## Rules
- **Be specific** — don't say "run the app", say `pnpm dev:cli` or `pnpm dev:web` with the exact URL - **Be brief** — no walls of text, just actionable steps - **Show commands** — every "try it" step should have a copy-pasteable command or a click path - **Read the spec** — the success criteria in spec.yaml tell you what the user should be able to verify - **Check task states** — if tasks.yaml shows all tasks as Todo but commits exist, the feature was implemented outside the task tracker (common). Use commits + build status as ground truth. - **If implementation is complete** — focus the report on "Try It Now" and verification steps - **If implementation is in progress** — highlight what's done, what's next, and any blockers
Intended uses
- Detect current branch — git branch --show-current
- Find the matching spec — look for a specs/NNN- directory whose feature.yaml branch field matches the current branch
- Read these files (in parallel):
- specs/NNN-/feature.yaml — lifecycle, phase, progress, completed phases
- specs/NNN-/tasks.yaml — task list with states
- specs/NNN-/spec.yaml — summary, success criteria
- Read recent commits — git log --oneline -10 to see what was done
- Produce the status report (see format below)
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.