5,077 件 ・ 関連度順
概要と使いどころ
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 when the user asks to add a phase, feature, or scope to the end of the current milestone roadmap. Adds the next sequential phase directory, updates ROADMAP.md, and tracks the change in STATE.md.
日本語の概要は準備中です。原文の説明を表示しています。
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 says run the rest autonomously, overnight, or hands-off through the remaining phases. Runs discuss, plan, execute per phase, pausing only for user decisions, then milestone audit, complete, and cleanup.
日本語の概要は準備中です。原文の説明を表示しています。
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 .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 wants a dashboard of all phases or to run more than one phase in parallel. Shows phase status with recommended next actions, runs discuss inline, and dispatches plan and execute as background agents.
日本語の概要は準備中です。原文の説明を表示しています。
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 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 every phase in a milestone is complete and the user wants to archive it, tag the release, and start the next version. Archives roadmap and requirements to .planning/milestones/, updates PROJECT.md, then tags the version.
日本語の概要は準備中です。原文の説明を表示しています。
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 the user asks to profile how they work, adapt assistant responses to them, or refresh an existing developer profile. Generates USER-PROFILE.md from session analysis or a questionnaire.
日本語の概要は準備中です。原文の説明を表示しています。
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 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 when you know what you want but not which /gsd-* command to run. Routes freeform text to the best matching GSD command, confirms the match, then hands off without doing the work itself.
日本語の概要は準備中です。原文の説明を表示しています。
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 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 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 a GSD update, when local modifications were backed up to gsd-local-patches/ and must be merged back. Three-way compares the pristine baseline, the backup, and the new install, flagging conflicts instead of skipping files.
日本語の概要は準備中です。原文の説明を表示しています。
Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone
日本語の概要は準備中です。原文の説明を表示しています。
Use when a phase has unresolved decisions before planning and no CONTEXT.md exists. Asks adaptive questions on the phase's gray areas and writes {phase_num}-CONTEXT.md with locked decisions; --auto, --chain, --power change the questioning.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。