229 件（coco-research のリポジトリ） ・ 人気順
概要と使いどころ
Use when an idea, task, or issue surfaces mid-session and the user wants it captured as a todo instead of doing it now. Infers the area, checks duplicates, and writes the todo file plus a STATE.md update.
日本語の概要は準備中です。原文の説明を表示しています。
Use before /gsd-manager to fill in missing Depends on fields in ROADMAP.md. Analyzes file overlap, semantic dependencies and data flow between phases, then suggests dependency updates to confirm.
日本語の概要は準備中です。原文の説明を表示しています。
Use after /gsd-audit-uat when the user wants the findings fixed, not just listed. Classifies each issue as auto-fixable or manual and fixes the auto-fixable ones with test verification and atomic commits; --severity sets the floor.
日本語の概要は準備中です。原文の説明を表示しています。
Use before archiving a milestone, or when the user asks whether a milestone met its definition of done. Aggregates phase VERIFICATION.md files, tech debt and deferred gaps, then runs a cross-phase integration check.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks what UAT or verification items are still outstanding across phases, or wants a prioritized manual test plan. Scans every phase for pending, skipped, blocked and human_needed items and flags stale docs.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks what is pending, what to do next, or to list todos (optionally filtered by area). Lists pending todos, loads full context for the selected one, and routes to work now, add to a phase, brainstorm, or create a phase.
日本語の概要は準備中です。原文の説明を表示しています。
Use when .planning/phases/ has accumulated directories from completed milestones. Shows a dry-run of what moves to .planning/milestones/v{X.Y}-phases/ and archives only after confirmation.
日本語の概要は準備中です。原文の説明を表示しています。
Use after a phase's code is written, or when the user asks to review changed files for bugs, security issues, or quality. Spawns the gsd-code-reviewer agent at quick, standard, or deep depth and writes the phase REVIEW.md.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to generate, update, refresh or verify project documentation, or to check that docs still match the codebase. Writes up to 9 doc files, each verified against real paths; supports --force and --verify-only.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to execute a phase's plans, resume the remaining plans, or run only one wave. Discovers plans, groups them into dependency waves, spawns a fresh subagent per plan, then verifies the phase.
日本語の概要は準備中です。原文の説明を表示しています。
Use for a trivial task the user can describe in one sentence: a typo, config change, small refactor or forgotten commit. Executes inline with no subagents and no PLAN.md; anything needing research or planning belongs to /gsd-quick.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a GSD run failed, stalled, or produced the wrong result and the cause is unclear. Reads git history and .planning/ state and phase artifacts to diagnose root cause, then writes a report to .planning/forensics/.
日本語の概要は準備中です。原文の説明を表示しています。
Use when .planning/ looks inconsistent, files are missing, or state seems wrong. Validates .planning/ integrity, reports missing files, bad config, and orphaned plans, and --repair fixes what it finds.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks what GSD commands exist or how to use GSD. Outputs the complete GSD command reference verbatim, with no project analysis, status, or next-step suggestions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to bring an external plan file into GSD planning, or passes --from <filepath>. Detects conflicts against PROJECT.md decisions, writes it as a GSD PLAN.md, and validates it with gsd-plan-checker.
日本語の概要は準備中です。原文の説明を表示しています。
Use when urgent work surfaces mid-milestone and must land between two planned phases without renumbering the roadmap. Inserts it as a decimal phase such as 72.1 after the phase the user names.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks where to get help, how to join the GSD community, or where to report a problem. Displays the Discord invite link and what the server is for.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks which GSD workspaces exist, or where their isolated work lives. Scans the workspaces root for WORKSPACE.md manifests and prints name, path, repo count, strategy and project status.
日本語の概要は準備中です。原文の説明を表示しています。
Use to keep moving without inspecting progress, or when the user asks what is next in the GSD workflow. Reads STATE.md, ROADMAP.md and phase dirs to invoke the next step; --force skips safety and verification gates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says note this, jot this down, asks to list my notes, or wants a note promoted to a todo. Appends a timestamped note file in one Write with one confirmation line, no questions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to pause work mid-phase or hand it off to a new session. Writes .continue-here.md with position, completed and remaining work, decisions and blockers, commits it as WIP, and prints resume instructions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a milestone audit reported gaps and you want the fix phases created in one pass. Reads MILESTONE-AUDIT.md, groups gaps into phases, adds them to ROADMAP.md and offers to plan each one.
日本語の概要は準備中です。原文の説明を表示しています。
Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone
日本語の概要は準備中です。原文の説明を表示しています。
Use when opening a pull request and the diff is cluttered with .planning/ commits. Creates a clean branch filtered of GSD planning artifacts so reviewers see only code changes.
日本語の概要は準備中です。原文の説明を表示しています。