.claude/skills/pm-status/SKILL.md
Show project status dashboard with issue/FR/WP counts, active items, blocked items, and priority next actions. Use when the user asks about project status, progress, what's happening, what needs attention, or what to work on.
npx skillsauth add pinkroosterai/PinkRoosterMcp pm-statusInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Show a formatted project status dashboard by chaining PinkRooster MCP tools.
Get the project status using the current working directory:
pwdmcp__pinkrooster__get_project_status with projectPath set to the directory aboveprojectId from the response (e.g., proj-1)mcp__pinkrooster__create_or_update_project with name, description, and projectPath to register."Call mcp__pinkrooster__get_next_actions with:
projectId from Step 1limit: use $ARGUMENTS if provided, otherwise default to 10Present the results in this exact format:
## Project: {name} ({projectId})
### Health Summary
| Entity | Active | Blocked | Completed | Total |
|--------|--------|---------|-----------|-------|
| Issues | ... | ... | ... | ... |
| Feature Requests | ... | ... | ... | ... |
| Work Packages | ... | ... | ... | ... |
### Blocked Items
(List any blocked issues, WPs, or tasks. If none, show "None — no blockers.")
- **{entityId}** "{name}" — blocked by {blocker} | state: Blocked
(If blocked items exist, add: "Deep-dive analysis: `/pm-triage`")
### Next Actions (top {limit})
1. [{priority}] {entityId} "{name}" ({state}) — {type}
2. ...
Start working: `/pm-next` | Implement specific item: `/pm-implement {topEntityId}`
### Planning Opportunities
(Feature requests that are Approved/Scheduled but have no linked work package)
- **{frId}** "{name}" — {status}, no linked WP → `/pm-scaffold {frId}`
(If none, show "None — all tracked items have work packages.")
### Suggested Actions
(Generate contextual suggestions based on project state. Show the most relevant 3-5.)
- If blocked items exist → "Analyze blockers and priorities: `/pm-triage`"
- If Proposed FRs exist without user stories → "Refine FR for better scaffolding: `/pm-refine-fr {frId}`"
- If Approved/Scheduled FRs have no WP → "Scaffold a work package: `/pm-scaffold {frId}`"
- If scaffolded WPs are ready (NotStarted) → "Start implementing: `/pm-next`"
- If terminal/cancelled items are accumulating → "Remove stale entities: `/pm-housekeeping`"
- If no open FRs or issues exist → "Discover new feature opportunities: `/pm-explore`"
- If the project has no data yet → "Create work items with `/pm-plan <description>`"
/pm-plan <description>"tools
Verify acceptance criteria for a phase or entire work package. Runs verification based on each criterion's method (AutomatedTest, Manual, AgentReview) and records results via the MCP tool.
development
Diagnose the root cause of a bug, error, crash, or unexpected behavior. Traces through code, logs, services, database state, and git history to find why something is broken. Researches error messages online for known issues. Produces a diagnosis with evidence and suggested fix. Use when the user reports a problem, error message, stack trace, test failure, or says things like "why is this happening", "this is broken", "I'm getting an error", "something's wrong with...", "debug this", or "figure out why...".
development
Review and prioritize open issues and feature requests. Analyzes severity, age, and codebase impact to recommend priority adjustments and next steps.
development
Scaffold a complete work package with phases, tasks, and dependencies based on a feature description or linked issue/FR. Analyzes the codebase to produce realistic target files and implementation notes. Auto-transitions linked entities to planning states. Use when the user wants to break down work, plan implementation, create a WP, or says "scaffold", "break this down", "plan the implementation", or "create tasks for...".