Menu
Show all active pipeline topics and their phase/progress. Use when the user asks 'where are we', 'status', 'what's in flight', or when resuming and unsure which design to continue. Read-only discovery. Not a pipeline phase.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use this before any creative work — creating features, building components, adding functionality, or modifying behavior. Explores intent and design before implementation. Use this skill whenever the user describes something they want to build, change, or improve, even if they don't say 'brainstorm' — phrases like 'I want to add X', 'let's build Y', 'we need a way to Z', or 'help me design' all apply.
Review a completed requirement's code — trace the logic, check spec alignment against the acceptance criteria, fix code smells, and run a production hazard check. Runs after each requirement in pwk-executing-tasks. Unlocked: may edit code to apply smell fixes.
Use after all requirements are complete to delete consumed plan docs, curate lessons, update documentation, and ship the work.
Turn a design doc's requirements into a behavioral spec — acceptance criteria + integration tests per requirement. Use after pwk-brainstorming, before pwk-executing-tasks. Use when the user says 'let's plan', 'write a plan', 'break this down', or after a brainstorm when ready to move to implementation.
Disciplined debugging loop for hard bugs and performance regressions. Use when a test fails unexpectedly, a bug is found during execution, or something is broken. Use this skill whenever the user reports a bug, says 'this doesn't work', 'something's wrong', 'help me debug', or when tests fail for unclear reasons. Works at any point in the workflow — brainstorm, execute, or standalone.
Implement a plan requirement-by-requirement with test-first discipline and full autonomy. Run after pwk-writing-plans. Each requirement: write integration tests (red) → checkpoint → implement to green → checkpoint → pwk-code-review.
| name | pwk-status |
| description | Show all active pipeline topics and their phase/progress. Use when the user asks 'where are we', 'status', 'what's in flight', or when resuming and unsure which design to continue. Read-only discovery. Not a pipeline phase. |
Report on all in-flight pipelines (split designs may run in parallel across worktrees). Read-only. This skill does not unlock the guard — it needs no writes, so it runs fine inside the brainstorm/plan read-only phase. If you want source edits after a status check, invoke the skill for the next phase yourself (the guard follows the skill).
Glob docs/plans/*-design.md, *-implementation.md, *-progress.md.
For each <topic>, infer the furthest artifact present:
*-design.md → brainstorm done, plan next*-implementation.md but no progress → plan done, execute next*-progress.md → execute phase — show done/total requirement countPrint a one-line table, e.g.:
| Topic | Phase | Progress | Branch |
|---------|---------|----------|------------------|
| auth | execute | 2/3 done | auth |
| billing | plan | — | ../repo-billing |
If none, say so and suggest /skill:pwk-brainstorming.
Keep it short — this is orientation, not analysis. No writes; the <topic> slug is the identity.