9,937 件 ・ 関連度順
概要と使いどころ
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 .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 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 after gsd-code-review has written REVIEW.md, when you want its Critical and Warning findings fixed. Spawns the fixer agent, commits each fix atomically and writes REVIEW-FIX.md (--all, --auto to iterate).
日本語の概要は準備中です。原文の説明を表示しています。
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 what the codebase intel knows, or runs /gsd-intel query, status, diff, or refresh. Queries or rebuilds the .planning/intel/ files, and stops with a disabled message when intel is off in .planning/config.json.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。
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 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 onboarding to an unfamiliar codebase, before a major refactor, on a brownfield project before /gsd-new-project, or to refresh .planning/codebase/. Spawns up to 4 parallel mapper agents that write 7 documents.
日本語の概要は準備中です。原文の説明を表示しています。
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 onboarding someone to a finished milestone or preparing a team review. Reads ROADMAP, REQUIREMENTS, CONTEXT, SUMMARY, and VERIFICATION artifacts into one MILESTONE_SUMMARY in .planning/reports/, then offers Q&A.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user says 'cognee store', 'push to cognee', 'save to graph', 'remember this' or 'log this decision', or when session decisions must be stored. Writes entities, decisions and events over POST /api/v1/remember.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need an isolated copy of one or more repos with its own .planning/, or want to work on several repos in parallel. Creates worktrees or clones plus WORKSPACE.md; then run /gsd-new-project inside.
日本語の概要は準備中です。原文の説明を表示しています。
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 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.
日本語の概要は準備中です。原文の説明を表示しています。