メニュー
Unified revise for plans OR specs. Auto-detects target from critique report. Use when "revise", "fix plan/specs", or after /critique returns FIX_AND_SHIP. For initial creation, use /plan instead.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Guide CLAUDE.md updates based on doc-guard suggestions. This skill should be used when updating documentation, fixing docs, addressing doc-guard suggestions, or updating CLAUDE.md. Activates when user requests "update documentation", "fix docs", "doc-guard suggestions", or "update CLAUDE.md".
Monitor blocked workers and help respond to them. Loop checks ft inbox, shows blocked workers, lets you respond naturally.
Adds tasks to FormalTask with mandatory discovery and validated criteria. Use when "add task", "create task", or "/task-add". For batch creation, use /epic-decompose instead.
Groups uncommitted changes into logical commits, walks through each grouping for approval, then optionally syncs with remote. Resolves merge conflicts interactively with context from recent remote and local history. Use when "commit my changes", "group commits", "smart commit", "commit and sync", or "organize my changes". Never resolves conflicts without user confirmation.
Unified critique for plans, specs, OR task artifacts. Auto-detects target. Spawns auditors. Commits tasks to DB when READY. Use "critique", "review", "is this ready".
Systematic debugging with graded exploration and agent escalation. MUST BE USED when encountering errors, test failures, or unexpected behavior.
| name | revise |
| description | Unified revise for plans OR specs. Auto-detects target from critique report. Use when "revise", "fix plan/specs", or after /critique returns FIX_AND_SHIP. For initial creation, use /plan instead. |
| argument-hint | <project-name> |
| inherit | ["review"] |
| tools | ["auggie","warpgrep"] |
| ultrathink | true |
| required_todos | ["load-critique","extract-blockers","verify-before-fixing","apply-fixes","verify-fixes","output"] |
Read steps/load-critique.md and execute Phase 0 (skill_init, plan loading, finding extraction) and Phase 0.5 (user confirmation).
Read steps/extract-blockers.md and execute Phase 1 (group by priority, display P0/P1 counts, all mandatory).
Read steps/verify-findings.md and execute Phase 2 (grep codebase, VALID/INVALID/STALE marking, new findings).
Read steps/apply-fixes.md and execute Phase 3 (PLAN fixes with resolution, CriterionV2 history, SPECS in-place edits).
Read steps/verify-resolution.md and execute Phase 4 (lightweight re-checks) and Phase 5 (publish report, findings table, git commit).
- Verify EVERY finding against codebase BEFORE fixing -- critiques lie - VALID/INVALID/STALE marking is MANDATORY -- document evidence - ALL P0s AND P1s must be resolved (partial = fail) - Plan revisions update in place, set resolution on history entries (fixed/rejected/deferred) - Spec revisions edit in place - Don't expand scope -- fix only what critique found (but fix it completely when verification reveals larger scope)