Use when the user wants to see what the agent assumes about a phase's approach, order, scope, risks and dependencies before planning starts, instead of running a full discuss session. Read-only; ends with a prompt for feedback.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when a completed phase needs unit or E2E tests, or the user asks to add tests for phase N. Classifies implementation files into TDD, E2E, or skip, gets plan approval, then generates RED-GREEN tests from SUMMARY.md and UAT criteria.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when the user says 'cognee', asks about knowledge graph or graph memory, wants to switch memory backends, or needs a status check, dataset init, or graph view. Covers Cognee endpoints plus the Brain fallback.
The English summary is being prepared. Showing the original description.
Use when starting GSD in a repo that has no .planning/ yet, or the user wants a new project set up. Questioning, optional research, requirements, and roadmap produce .planning/PROJECT.md, REQUIREMENTS.md, ROADMAP.md, and STATE.md.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when the user wants to think through an idea before committing to a plan, e.g. /gsd-explore auth strategy. Runs a Socratic session, optionally spawns research, then routes output to notes, seeds, requirements, or new phases.
The English summary is being prepared. Showing the original description.
Use when a planned but unstarted phase should come off the roadmap. Removes the phase, renumbers the phases after it into a clean sequence, and commits the change as the historical record.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when the current milestone has shipped and it is time to scope the next one, or when the user asks to start a new milestone. Updates PROJECT.md, then runs questioning, research, requirements, and roadmap.
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)