From pm
Lists all spec GitHub Issues with their status and task counts. Use when the user wants to discover existing specs or get a project overview.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm:spec-listThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Lists all feature specs as GitHub Issues labeled with `spec`.
Lists all feature specs as GitHub Issues labeled with spec.
!```bash
echo "--- Fetching spec issues ---"
gh issue list --label "spec" --state all --limit 200
--json number,title,state,url,labels
--jq '[.[] | select(.labels | map(.name) | contains(["done"]) | not)] | if length == 0 then "No spec issues found. Create your first spec with: /pm:spec-init " else "SPEC_ISSUES:\n" + (. | tojson) end'
2>/dev/null || echo "[]"
## Instructions
Display the spec list shown above. If no specs exist, prompt the user to create one with `/pm:spec-init <title>`.
Format the output as:
| Issue | Title | State |
|---|---|---|
| #12 | [Spec]: user auth | 🔄 OPEN |
| #8 | [Spec]: dark mode | ✅ CLOSED |
For each spec, suggest the appropriate next step based on its state and labels:
- Has no `planned` label → `/pm:spec-plan <number>`
- Has `planned` but no `ready` label → `/pm:spec-decompose <number>`
- Has `ready` label, issue open → `/pm:spec-status <number>`
- Issue is CLOSED → spec complete
npx claudepluginhub boringhappy/codemate --plugin pmManages feature specifications lifecycle: creates from requirements in draft/, tracks progress, moves to active (max 3) or completed folders. Use for planning, status checks, activation, or completion.
Displays dashboard of specification status from .specs/ directory, including workflow progress, quality scores, pending items, and issues. Useful for tracking spec-driven development workflows with --all or spec-id.
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.