agentleFS
pinkroosteraipinkroosterai/PinkRoosterMcp/.claude/skills/pm-status/SKILL.md

pm-status

Skill2 starsChanged 8 months agoMITView on GitHub

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.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 4 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Call mcp__pinkrooster__get_project_status with projectPath set to the directory above

    line 20
  2. Very specific:

    If no project found, tell the user and offer to register it: "No project found.

    line 22
  3. Distinctive:

    Never modify any entities — this skill is read-only

    line 74
  4. Distinctive:

    Always show the blocked items section even if empty (say "None")

    line 75
  5. Distinctive:

    Always show planning opportunities even if empty (say "None")

    line 76
  6. Very specific:

    If the project has no data yet, show empty tables and suggest: "Create work items with /pm-plan <description>"

    line 77
  7. Distinctive:

    Always include actionable skill suggestions in each section so the user can act immediately

    line 79

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Project Status Dashboard

Show a formatted project status dashboard by chaining PinkRooster MCP tools.

Step 1: Resolve Project

Get the project status using the current working directory:

  • Current directory: !pwd
  • Call mcp__pinkrooster__get_project_status with projectPath set to the directory above
  • Extract the projectId from the response (e.g., proj-1)
  • If no project found, tell the user and offer to register it: "No project found. Run mcp__pinkrooster__create_or_update_project with name, description, and projectPath to register."

Step 2: Get Next Actions

Call mcp__pinkrooster__get_next_actions with:

  • projectId from Step 1
  • limit: use $ARGUMENTS if provided, otherwise default to 10

Step 3: Format Dashboard

Present 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>`"

Constraints

  • Never modify any entities — this skill is read-only
  • Always show the blocked items section even if empty (say "None")
  • Always show planning opportunities even if empty (say "None")
  • If the project has no data yet, show empty tables and suggest: "Create work items with /pm-plan <description>"
  • Format priority tags: [Critical], [High], [Medium], [Low]
  • Always include actionable skill suggestions in each section so the user can act immediately

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.