メニュー
Scan docs/superpowers/ for active specs and plans. Show status table with cycle stage, progress, and blockers. Suggest what to tackle next. Works in any repo with the superpowers pipeline.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | todo |
| description | Scan docs/superpowers/ for active specs and plans. Show status table with cycle stage, progress, and blockers. Suggest what to tackle next. Works in any repo with the superpowers pipeline. |
| tags | ["scan","propose","planning","meta","plan"] |
Scan the project's docs/superpowers/ folder for active design specs and implementation plans. Show what's in flight, what's blocked, and what to do next.
Scan for files in these locations (check both, either may not exist):
docs/superpowers/specs/*.md — design specs from brainstormingdocs/superpowers/plans/*.md — implementation plansIf neither directory exists or both are empty:
"No active work. Start something with
/brainstormor give me a task."
Stop here.
For each file found, read it and determine:
Cycle stage — infer from content:
| Signal | Stage |
|---|---|
| No checkboxes, discussion-style content, "approaches", "options" | brainstorming |
| Spec file exists but no matching plan file | spec-ready (needs /write-plan) |
Plan file with all - [ ] unchecked | planning (ready to execute) |
Plan file with mix of - [ ] and - [x] | executing |
Plan file with all - [x] checked | review (needs verification) |
| File contains "DONE" or "COMPLETED" marker | done (should be cleaned up) |
Progress — count checkboxes:
{checked}/{total} (e.g., 3/7)—Blocker — scan for signals:
userblocked ({dependency})noneFile | Stage | Progress | Blocker
specs/2025-03-15-auth-design.md | spec-ready | — | none
plans/2025-03-15-auth.md | executing | 3/7 | none
specs/2025-04-01-dashboard-design.md | brainstorming| — | user (needs decision on layout)
Below the table, recommend what to tackle next. Priority order:
/execute-plan)/review)/write-plan)/execute-plan)Format as a short prioritized list:
Next up:
1. Continue executing plans/2025-03-15-auth.md (3/7 done, unblocked)
2. Write plan for specs/2025-04-01-dashboard-design.md (spec approved, no plan yet)
3. Clean up plans/2025-02-20-old-feature.md (all tasks done)
If specs and plans exist for the same feature (matched by date prefix or name):
auth-design.md → auth.mddocs/superpowers/ to exist (created by /sp-bootstrap).Cross-reference project docs for drift, stale references, and contradictions. Outputs timestamped report. Universal baseline — works with any docs/ structure from sp-bootstrap.
Stage and commit current session changes with a proper conventional commit message. No push.
Use when a non-trivial decision needs deep deliberation grounded in the project's full canonical context. Loads all canonical project docs, states the frame (target user, binding constraints, what's already decided), then enters open conversation with the user. This is a context-loading skill, not an output-producing one.
Scan frontend code for domain logic that violates Frontend=Intent, Backend=Logic. Outputs structured violation report. Universal baseline — extend with project-specific patterns.
Use when caller wants to observe how a stranger encounters a flow, artifact, or sandbox — triggers like "simulate a user journey", "test our onboarding / checkout / signup", "will my ICP convert", "how does a cold reader experience this README", "first-time user test", "cognitive walkthrough", or any request to evaluate friction from a non-builder perspective.
Absorb one or more feature branches into the base branch. Recommends merge vs rebase per branch. Designed for lazy absorption of parallel Claude session branches.