fix: replace /gsd: slash command format with /gsd- skill format in all user-facing content (#1579)
* fix: replace /gsd: command format with /gsd- skill format in all suggestions All next-step suggestions shown to users were still using the old colon format (/gsd:xxx) which cannot be copy-pasted as skills. Migrated all occurrences across agents/, commands/, get-shit-done/, docs/, README files, bin/install.js (hardcoded defaults for claude runtime), and get-shit-done/bin/lib/*.cjs (generate-claude-md templates and error messages). Updated tests to assert new hyphen format instead of old colon format. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: migrate remaining /gsd: format to /gsd- in hooks, workflows, and sdk Addresses remaining user-facing occurrences missed in the initial migration: - hooks/: fix 4 user-facing messages (pause-work, update, fast, quick) and 2 comments in gsd-workflow-guard.js - get-shit-done/workflows/: fix 21 Skill() literal calls that Claude executes directly (installer does not transform workflow content) - sdk/prompt-sanitizer.ts: update regex to strip /gsd- format in addition to legacy /gsd: format; update JSDoc comment - tests/: update autonomous-ui-steps, prompt-sanitizer to assert new format Note: commands/gsd/*.md frontmatter (name: gsd:xxx) intentionally unchanged — installer derives skillName from directory path, not the name field. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(plan-phase): preserve --chain flag in auto-advance sync and handle ui-phase gate in chain mode Bug 1: step 15 sync-flag check only guarded against --auto, causing _auto_chain_active to be cleared when plan-phase is invoked without --auto in ARGUMENTS even though a --chain pipeline was active. Added --chain to the guard condition, matching discuss-phase behaviour. Bug 2: UI Design Contract gate (step 5.6) always exited the workflow when UI-SPEC was missing, breaking the discuss --chain pipeline silently. When _auto_chain_active is true, the gate now auto-invokes gsd-ui-phase --auto via Skill() and continues to step 6 without prompting. Manual invocations retain the existing AskUserQuestion flow. * fix: remove <sub>/clear</sub> pattern and duplicate old-format command in discuss-phase.md --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
166
docs/FEATURES.md
166
docs/FEATURES.md
@@ -93,7 +93,7 @@
|
||||
|
||||
### 1. Project Initialization
|
||||
|
||||
**Command:** `/gsd:new-project [--auto @file.md]`
|
||||
**Command:** `/gsd-new-project [--auto @file.md]`
|
||||
|
||||
**Purpose:** Transform a user's idea into a fully structured project with research, scoped requirements, and a phased roadmap.
|
||||
|
||||
@@ -132,13 +132,13 @@
|
||||
- Research agents have web search capability for current ecosystem information
|
||||
- Granularity setting controls phase count: `coarse` (3-5), `standard` (5-8), `fine` (8-12)
|
||||
- `--auto` mode extracts all information from the provided document without interactive questioning
|
||||
- Existing codebase context (from `/gsd:map-codebase`) is loaded if present
|
||||
- Existing codebase context (from `/gsd-map-codebase`) is loaded if present
|
||||
|
||||
---
|
||||
|
||||
### 2. Phase Discussion
|
||||
|
||||
**Command:** `/gsd:discuss-phase [N] [--auto] [--batch]`
|
||||
**Command:** `/gsd-discuss-phase [N] [--auto] [--batch]`
|
||||
|
||||
**Purpose:** Capture user's implementation preferences and decisions before research and planning begin. Eliminates the gray areas that cause AI to guess.
|
||||
|
||||
@@ -165,7 +165,7 @@
|
||||
|
||||
### 3. UI Design Contract
|
||||
|
||||
**Command:** `/gsd:ui-phase [N]`
|
||||
**Command:** `/gsd-ui-phase [N]`
|
||||
|
||||
**Purpose:** Lock design decisions before planning so that all components in a phase share consistent visual standards.
|
||||
|
||||
@@ -197,7 +197,7 @@
|
||||
|
||||
### 4. Phase Planning
|
||||
|
||||
**Command:** `/gsd:plan-phase [N] [--auto] [--skip-research] [--skip-verify]`
|
||||
**Command:** `/gsd-plan-phase [N] [--auto] [--skip-research] [--skip-verify]`
|
||||
|
||||
**Purpose:** Research the implementation domain and produce verified, atomic execution plans.
|
||||
|
||||
@@ -208,7 +208,7 @@
|
||||
- REQ-PLAN-04: System MUST include `read_first` and `acceptance_criteria` sections in every plan
|
||||
- REQ-PLAN-05: System MUST run plan checker verification loop (up to 3 iterations) unless `--skip-verify` is set
|
||||
- REQ-PLAN-06: System MUST support `--skip-research` flag to bypass research phase
|
||||
- REQ-PLAN-07: System MUST prompt user to run `/gsd:ui-phase` if frontend phase detected and no UI-SPEC.md exists (UI safety gate)
|
||||
- REQ-PLAN-07: System MUST prompt user to run `/gsd-ui-phase` if frontend phase detected and no UI-SPEC.md exists (UI safety gate)
|
||||
- REQ-PLAN-08: System MUST include Nyquist validation mapping when `workflow.nyquist_validation` is enabled
|
||||
- REQ-PLAN-09: System MUST verify all phase requirements are covered by at least one plan before planning completes (requirements coverage gate)
|
||||
|
||||
@@ -247,7 +247,7 @@
|
||||
|
||||
### 5. Phase Execution
|
||||
|
||||
**Command:** `/gsd:execute-phase <N>`
|
||||
**Command:** `/gsd-execute-phase <N>`
|
||||
|
||||
**Purpose:** Execute all plans in a phase using wave-based parallelization with fresh context windows per executor.
|
||||
|
||||
@@ -291,7 +291,7 @@
|
||||
|
||||
### 6. Work Verification
|
||||
|
||||
**Command:** `/gsd:verify-work [N]`
|
||||
**Command:** `/gsd-verify-work [N]`
|
||||
|
||||
**Purpose:** User acceptance testing — walk the user through testing each deliverable and auto-diagnose failures.
|
||||
|
||||
@@ -309,7 +309,7 @@
|
||||
|
||||
### 6.5. Ship
|
||||
|
||||
**Command:** `/gsd:ship [N] [--draft]`
|
||||
**Command:** `/gsd-ship [N] [--draft]`
|
||||
|
||||
**Purpose:** Bridge local completion → merged PR. After verification passes, push branch, create PR with auto-generated body from planning artifacts, optionally trigger review, and track in STATE.md.
|
||||
|
||||
@@ -328,7 +328,7 @@
|
||||
|
||||
### 7. UI Review
|
||||
|
||||
**Command:** `/gsd:ui-review [N]`
|
||||
**Command:** `/gsd-ui-review [N]`
|
||||
|
||||
**Purpose:** Retroactive 6-pillar visual audit of implemented frontend code. Works standalone on any project.
|
||||
|
||||
@@ -353,7 +353,7 @@
|
||||
|
||||
### 8. Milestone Management
|
||||
|
||||
**Commands:** `/gsd:audit-milestone`, `/gsd:complete-milestone`, `/gsd:new-milestone [name]`
|
||||
**Commands:** `/gsd-audit-milestone`, `/gsd-complete-milestone`, `/gsd-new-milestone [name]`
|
||||
|
||||
**Purpose:** Verify milestone completion, archive, tag release, and start the next development cycle.
|
||||
|
||||
@@ -368,7 +368,7 @@
|
||||
- REQ-MILE-08: New milestone MUST follow same flow as new-project (questions → research → requirements → roadmap)
|
||||
- REQ-MILE-09: New milestone MUST NOT reset existing workflow configuration
|
||||
|
||||
**Gap Closure:** `/gsd:plan-milestone-gaps` creates phases to close gaps identified by audit.
|
||||
**Gap Closure:** `/gsd-plan-milestone-gaps` creates phases to close gaps identified by audit.
|
||||
|
||||
---
|
||||
|
||||
@@ -376,7 +376,7 @@
|
||||
|
||||
### 9. Phase Management
|
||||
|
||||
**Commands:** `/gsd:add-phase`, `/gsd:insert-phase [N]`, `/gsd:remove-phase [N]`
|
||||
**Commands:** `/gsd-add-phase`, `/gsd-insert-phase [N]`, `/gsd-remove-phase [N]`
|
||||
|
||||
**Purpose:** Dynamic roadmap modification during development.
|
||||
|
||||
@@ -391,7 +391,7 @@
|
||||
|
||||
### 10. Quick Mode
|
||||
|
||||
**Command:** `/gsd:quick [--full] [--discuss] [--research]`
|
||||
**Command:** `/gsd-quick [--full] [--discuss] [--research]`
|
||||
|
||||
**Purpose:** Ad-hoc task execution with GSD guarantees but a faster path.
|
||||
|
||||
@@ -410,7 +410,7 @@
|
||||
|
||||
### 11. Autonomous Mode
|
||||
|
||||
**Command:** `/gsd:autonomous [--from N]`
|
||||
**Command:** `/gsd-autonomous [--from N]`
|
||||
|
||||
**Purpose:** Run all remaining phases autonomously — discuss → plan → execute per phase.
|
||||
|
||||
@@ -425,7 +425,7 @@
|
||||
|
||||
### 12. Freeform Routing
|
||||
|
||||
**Command:** `/gsd:do`
|
||||
**Command:** `/gsd-do`
|
||||
|
||||
**Purpose:** Analyze freeform text and route to the appropriate GSD command.
|
||||
|
||||
@@ -439,7 +439,7 @@
|
||||
|
||||
### 13. Note Capture
|
||||
|
||||
**Command:** `/gsd:note`
|
||||
**Command:** `/gsd-note`
|
||||
|
||||
**Purpose:** Zero-friction idea capture without interrupting workflow. Append timestamped notes, list all notes, or promote notes to structured todos.
|
||||
|
||||
@@ -454,7 +454,7 @@
|
||||
|
||||
### 14. Auto-Advance (Next)
|
||||
|
||||
**Command:** `/gsd:next`
|
||||
**Command:** `/gsd-next`
|
||||
|
||||
**Purpose:** Automatically detect current project state and advance to the next logical workflow step, eliminating the need to remember which phase/step you're on.
|
||||
|
||||
@@ -462,18 +462,18 @@
|
||||
- REQ-NEXT-01: System MUST read STATE.md, ROADMAP.md, and phase directories to determine current position
|
||||
- REQ-NEXT-02: System MUST detect whether discuss, plan, execute, or verify is needed
|
||||
- REQ-NEXT-03: System MUST invoke the correct command automatically
|
||||
- REQ-NEXT-04: System MUST suggest `/gsd:new-project` if no project exists
|
||||
- REQ-NEXT-05: System MUST suggest `/gsd:complete-milestone` when all phases are complete
|
||||
- REQ-NEXT-04: System MUST suggest `/gsd-new-project` if no project exists
|
||||
- REQ-NEXT-05: System MUST suggest `/gsd-complete-milestone` when all phases are complete
|
||||
|
||||
**State Detection Logic:**
|
||||
| State | Action |
|
||||
|-------|--------|
|
||||
| No `.planning/` directory | Suggest `/gsd:new-project` |
|
||||
| Phase has no CONTEXT.md | Run `/gsd:discuss-phase` |
|
||||
| Phase has no PLAN.md files | Run `/gsd:plan-phase` |
|
||||
| Phase has plans but no SUMMARY.md | Run `/gsd:execute-phase` |
|
||||
| Phase executed but no VERIFICATION.md | Run `/gsd:verify-work` |
|
||||
| All phases complete | Suggest `/gsd:complete-milestone` |
|
||||
| No `.planning/` directory | Suggest `/gsd-new-project` |
|
||||
| Phase has no CONTEXT.md | Run `/gsd-discuss-phase` |
|
||||
| Phase has no PLAN.md files | Run `/gsd-plan-phase` |
|
||||
| Phase has plans but no SUMMARY.md | Run `/gsd-execute-phase` |
|
||||
| Phase executed but no VERIFICATION.md | Run `/gsd-verify-work` |
|
||||
| All phases complete | Suggest `/gsd-complete-milestone` |
|
||||
|
||||
---
|
||||
|
||||
@@ -488,12 +488,12 @@
|
||||
- REQ-NYQ-02: System MUST map each requirement to a specific test command
|
||||
- REQ-NYQ-03: System MUST identify Wave 0 tasks (test scaffolding needed before implementation)
|
||||
- REQ-NYQ-04: Plan checker MUST enforce Nyquist compliance as 8th verification dimension
|
||||
- REQ-NYQ-05: System MUST support retroactive validation via `/gsd:validate-phase`
|
||||
- REQ-NYQ-05: System MUST support retroactive validation via `/gsd-validate-phase`
|
||||
- REQ-NYQ-06: System MUST be disableable via `workflow.nyquist_validation: false`
|
||||
|
||||
**Produces:** `{phase}-VALIDATION.md` — Test coverage contract
|
||||
|
||||
**Retroactive Validation (`/gsd:validate-phase [N]`):**
|
||||
**Retroactive Validation (`/gsd-validate-phase [N]`):**
|
||||
- Scans implementation and maps requirements to tests
|
||||
- Identifies gaps where requirements lack automated verification
|
||||
- Spawns auditor to generate tests (max 3 attempts)
|
||||
@@ -521,7 +521,7 @@
|
||||
**Requirements:**
|
||||
- REQ-POSTVER-01: System MUST check against phase goals, not just task completion
|
||||
- REQ-POSTVER-02: System MUST produce VERIFICATION.md with pass/fail analysis
|
||||
- REQ-POSTVER-03: System MUST log issues for `/gsd:verify-work` to address
|
||||
- REQ-POSTVER-03: System MUST log issues for `/gsd-verify-work` to address
|
||||
- REQ-POSTVER-04: System MUST be disableable via `workflow.verifier: false`
|
||||
|
||||
---
|
||||
@@ -542,7 +542,7 @@
|
||||
|
||||
### 19. Health Validation
|
||||
|
||||
**Command:** `/gsd:health [--repair]`
|
||||
**Command:** `/gsd-health [--repair]`
|
||||
|
||||
**Purpose:** Validate `.planning/` directory integrity and auto-repair issues.
|
||||
|
||||
@@ -565,7 +565,7 @@
|
||||
- REQ-REGR-03: Regressions MUST be surfaced before post-execution verification
|
||||
- REQ-REGR-04: System MUST identify which prior phase's tests were broken
|
||||
|
||||
**When:** Runs automatically during `/gsd:execute-phase` before the verifier step.
|
||||
**When:** Runs automatically during `/gsd-execute-phase` before the verifier step.
|
||||
|
||||
---
|
||||
|
||||
@@ -579,7 +579,7 @@
|
||||
- REQ-COVGATE-03: Uncovered requirements MUST block planning completion
|
||||
- REQ-COVGATE-04: System MUST report which specific requirements lack plan coverage
|
||||
|
||||
**When:** Runs automatically at the end of `/gsd:plan-phase` after the plan checker loop.
|
||||
**When:** Runs automatically at the end of `/gsd-plan-phase` after the plan checker loop.
|
||||
|
||||
---
|
||||
|
||||
@@ -607,7 +607,7 @@
|
||||
|
||||
### 23. Session Management
|
||||
|
||||
**Commands:** `/gsd:pause-work`, `/gsd:resume-work`, `/gsd:progress`
|
||||
**Commands:** `/gsd-pause-work`, `/gsd-resume-work`, `/gsd-progress`
|
||||
|
||||
**Purpose:** Maintain project continuity across context resets and sessions.
|
||||
|
||||
@@ -624,7 +624,7 @@
|
||||
|
||||
### 24. Session Reporting
|
||||
|
||||
**Command:** `/gsd:session-report`
|
||||
**Command:** `/gsd-session-report`
|
||||
|
||||
**Purpose:** Generate a structured post-session summary document capturing work performed, outcomes achieved, and estimated resource usage.
|
||||
|
||||
@@ -663,7 +663,7 @@
|
||||
|
||||
### 26. Model Profiles
|
||||
|
||||
**Command:** `/gsd:set-profile <quality|balanced|budget|inherit>`
|
||||
**Command:** `/gsd-set-profile <quality|balanced|budget|inherit>`
|
||||
|
||||
**Purpose:** Control which AI model each agent uses, balancing quality vs cost.
|
||||
|
||||
@@ -699,7 +699,7 @@
|
||||
|
||||
### 27. Codebase Mapping
|
||||
|
||||
**Command:** `/gsd:map-codebase [area]`
|
||||
**Command:** `/gsd-map-codebase [area]`
|
||||
|
||||
**Purpose:** Analyze an existing codebase before starting a new project, so GSD understands what exists.
|
||||
|
||||
@@ -707,7 +707,7 @@
|
||||
- REQ-MAP-01: System MUST spawn parallel mapper agents for each analysis area
|
||||
- REQ-MAP-02: System MUST produce structured documents in `.planning/codebase/`
|
||||
- REQ-MAP-03: System MUST detect: tech stack, architecture patterns, coding conventions, concerns
|
||||
- REQ-MAP-04: Subsequent `/gsd:new-project` MUST load codebase mapping and focus questions on what's being added
|
||||
- REQ-MAP-04: Subsequent `/gsd-new-project` MUST load codebase mapping and focus questions on what's being added
|
||||
- REQ-MAP-05: Optional `[area]` argument MUST scope mapping to a specific area
|
||||
|
||||
**Produces:**
|
||||
@@ -727,7 +727,7 @@
|
||||
|
||||
### 28. Debug System
|
||||
|
||||
**Command:** `/gsd:debug [description]`
|
||||
**Command:** `/gsd-debug [description]`
|
||||
|
||||
**Purpose:** Systematic debugging with persistent state across context resets.
|
||||
|
||||
@@ -745,7 +745,7 @@
|
||||
|
||||
### 29. Todo Management
|
||||
|
||||
**Commands:** `/gsd:add-todo [desc]`, `/gsd:check-todos`
|
||||
**Commands:** `/gsd-add-todo [desc]`, `/gsd-check-todos`
|
||||
|
||||
**Purpose:** Capture ideas and tasks during sessions for later work.
|
||||
|
||||
@@ -759,7 +759,7 @@
|
||||
|
||||
### 30. Statistics Dashboard
|
||||
|
||||
**Command:** `/gsd:stats`
|
||||
**Command:** `/gsd-stats`
|
||||
|
||||
**Purpose:** Display project metrics — phases, plans, requirements, git history, and timeline.
|
||||
|
||||
@@ -773,7 +773,7 @@
|
||||
|
||||
### 31. Update System
|
||||
|
||||
**Command:** `/gsd:update`
|
||||
**Command:** `/gsd-update`
|
||||
|
||||
**Purpose:** Update GSD to the latest version with changelog preview.
|
||||
|
||||
@@ -782,13 +782,13 @@
|
||||
- REQ-UPDATE-02: System MUST display changelog for new version before updating
|
||||
- REQ-UPDATE-03: System MUST be runtime-aware and target the correct directory
|
||||
- REQ-UPDATE-04: System MUST back up locally modified files to `gsd-local-patches/`
|
||||
- REQ-UPDATE-05: `/gsd:reapply-patches` MUST restore local modifications after update
|
||||
- REQ-UPDATE-05: `/gsd-reapply-patches` MUST restore local modifications after update
|
||||
|
||||
---
|
||||
|
||||
### 32. Settings Management
|
||||
|
||||
**Command:** `/gsd:settings`
|
||||
**Command:** `/gsd-settings`
|
||||
|
||||
**Purpose:** Interactive configuration of workflow toggles and model profile.
|
||||
|
||||
@@ -821,7 +821,7 @@
|
||||
|
||||
### 33. Test Generation
|
||||
|
||||
**Command:** `/gsd:add-tests [N]`
|
||||
**Command:** `/gsd-add-tests [N]`
|
||||
|
||||
**Purpose:** Generate tests for a completed phase based on UAT criteria and implementation.
|
||||
|
||||
@@ -913,14 +913,14 @@ fix(03-01): correct auth token expiry
|
||||
|
||||
**Statusline Display:**
|
||||
```
|
||||
[⬆ /gsd:update │] model │ [current task │] directory [█████░░░░░ 50%]
|
||||
[⬆ /gsd-update │] model │ [current task │] directory [█████░░░░░ 50%]
|
||||
```
|
||||
|
||||
Color coding: <50% green, <65% yellow, <80% orange, ≥80% red with skull emoji
|
||||
|
||||
### 38. Developer Profiling
|
||||
|
||||
**Command:** `/gsd:profile-user [--questionnaire] [--refresh]`
|
||||
**Command:** `/gsd-profile-user [--questionnaire] [--refresh]`
|
||||
|
||||
**Purpose:** Analyze Claude Code session history to build behavioral profiles across 8 dimensions, generating artifacts that personalize Claude's responses to the developer's style.
|
||||
|
||||
@@ -936,7 +936,7 @@ Color coding: <50% green, <65% yellow, <80% orange, ≥80% red with skull emoji
|
||||
|
||||
**Generated Artifacts:**
|
||||
- `USER-PROFILE.md` — Full behavioral profile with evidence citations
|
||||
- `/gsd:dev-preferences` command — Load preferences in any session
|
||||
- `/gsd-dev-preferences` command — Load preferences in any session
|
||||
- `CLAUDE.md` profile section — Auto-discovered by Claude Code
|
||||
|
||||
**Flags:**
|
||||
@@ -978,14 +978,14 @@ After Level 3 wiring verification passes, spot-check individual exports for actu
|
||||
|
||||
### 40. Verification Debt Tracking
|
||||
|
||||
**Command:** `/gsd:audit-uat`
|
||||
**Command:** `/gsd-audit-uat`
|
||||
|
||||
**Purpose:** Prevent silent loss of UAT/verification items when projects advance past phases with outstanding tests. Surfaces verification debt across all prior phases so items are never forgotten.
|
||||
|
||||
**Components:**
|
||||
|
||||
**1. Cross-Phase Health Check** (progress.md Step 1.6)
|
||||
Every `/gsd:progress` call scans ALL phases in the current milestone for outstanding items (pending, skipped, blocked, human_needed). Displays a non-blocking warning section with actionable links.
|
||||
Every `/gsd-progress` call scans ALL phases in the current milestone for outstanding items (pending, skipped, blocked, human_needed). Displays a non-blocking warning section with actionable links.
|
||||
|
||||
**2. `status: partial`** (verify-work.md, UAT.md)
|
||||
New UAT status that distinguishes between "session ended" and "all tests resolved". Prevents `status: complete` when tests are still pending, blocked, or skipped without reason.
|
||||
@@ -1000,12 +1000,12 @@ When verification returns `human_needed`, items are persisted as a trackable HUM
|
||||
`phase complete` CLI returns verification debt warnings in its JSON output. Transition workflow surfaces outstanding items before confirmation.
|
||||
|
||||
**Requirements:**
|
||||
- REQ-DEBT-01: System MUST surface outstanding UAT/verification items from ALL prior phases in `/gsd:progress`
|
||||
- REQ-DEBT-01: System MUST surface outstanding UAT/verification items from ALL prior phases in `/gsd-progress`
|
||||
- REQ-DEBT-02: System MUST distinguish incomplete testing (partial) from completed testing (complete)
|
||||
- REQ-DEBT-03: System MUST categorize blocked tests with `blocked_by` tags
|
||||
- REQ-DEBT-04: System MUST persist human_needed verification items as trackable UAT files
|
||||
- REQ-DEBT-05: System MUST warn (non-blocking) during phase completion and transition when verification debt exists
|
||||
- REQ-DEBT-06: `/gsd:audit-uat` MUST scan all phases, categorize items by testability, and produce a human test plan
|
||||
- REQ-DEBT-06: `/gsd-audit-uat` MUST scan all phases, categorize items by testability, and produce a human test plan
|
||||
|
||||
---
|
||||
|
||||
@@ -1013,7 +1013,7 @@ When verification returns `human_needed`, items are persisted as a trackable HUM
|
||||
|
||||
### 41. Fast Mode
|
||||
|
||||
**Command:** `/gsd:fast [task description]`
|
||||
**Command:** `/gsd-fast [task description]`
|
||||
|
||||
**Purpose:** Execute trivial tasks inline without spawning subagents or generating PLAN.md files. For tasks too small to justify planning overhead: typo fixes, config changes, small refactors, forgotten commits, simple additions.
|
||||
|
||||
@@ -1023,15 +1023,15 @@ When verification returns `human_needed`, items are persisted as a trackable HUM
|
||||
- REQ-FAST-03: System MUST track the task in `.planning/quick/` for state consistency
|
||||
- REQ-FAST-04: System MUST NOT be used for tasks requiring research, multi-step planning, or verification
|
||||
|
||||
**When to use vs `/gsd:quick`:**
|
||||
- `/gsd:fast` — One-sentence tasks executable in under 2 minutes (typo, config change, small addition)
|
||||
- `/gsd:quick` — Anything needing research, multi-step planning, or verification
|
||||
**When to use vs `/gsd-quick`:**
|
||||
- `/gsd-fast` — One-sentence tasks executable in under 2 minutes (typo, config change, small addition)
|
||||
- `/gsd-quick` — Anything needing research, multi-step planning, or verification
|
||||
|
||||
---
|
||||
|
||||
### 42. Cross-AI Peer Review
|
||||
|
||||
**Command:** `/gsd:review --phase N [--gemini] [--claude] [--codex] [--coderabbit] [--all]`
|
||||
**Command:** `/gsd-review --phase N [--gemini] [--claude] [--codex] [--coderabbit] [--all]`
|
||||
|
||||
**Purpose:** Invoke external AI CLIs (Gemini, Claude, Codex, CodeRabbit) to independently review phase plans. Produces structured REVIEWS.md with per-reviewer feedback.
|
||||
|
||||
@@ -1040,7 +1040,7 @@ When verification returns `human_needed`, items are persisted as a trackable HUM
|
||||
- REQ-REVIEW-02: System MUST build a structured review prompt from phase plans
|
||||
- REQ-REVIEW-03: System MUST invoke each selected CLI independently
|
||||
- REQ-REVIEW-04: System MUST collect responses and produce `REVIEWS.md`
|
||||
- REQ-REVIEW-05: Reviews MUST be consumable by `/gsd:plan-phase --reviews`
|
||||
- REQ-REVIEW-05: Reviews MUST be consumable by `/gsd-plan-phase --reviews`
|
||||
|
||||
**Produces:** `{phase}-REVIEWS.md` — Per-reviewer structured feedback
|
||||
|
||||
@@ -1048,17 +1048,17 @@ When verification returns `human_needed`, items are persisted as a trackable HUM
|
||||
|
||||
### 43. Backlog Parking Lot
|
||||
|
||||
**Commands:** `/gsd:add-backlog <description>`, `/gsd:review-backlog`, `/gsd:plant-seed <idea>`
|
||||
**Commands:** `/gsd-add-backlog <description>`, `/gsd-review-backlog`, `/gsd-plant-seed <idea>`
|
||||
|
||||
**Purpose:** Capture ideas that aren't ready for active planning. Backlog items use 999.x numbering to stay outside the active phase sequence. Seeds are forward-looking ideas with trigger conditions that surface automatically at the right milestone.
|
||||
|
||||
**Requirements:**
|
||||
- REQ-BACKLOG-01: Backlog items MUST use 999.x numbering to stay outside active phase sequence
|
||||
- REQ-BACKLOG-02: Phase directories MUST be created immediately so `/gsd:discuss-phase` and `/gsd:plan-phase` work on them
|
||||
- REQ-BACKLOG-03: `/gsd:review-backlog` MUST support promote, keep, and remove actions per item
|
||||
- REQ-BACKLOG-02: Phase directories MUST be created immediately so `/gsd-discuss-phase` and `/gsd-plan-phase` work on them
|
||||
- REQ-BACKLOG-03: `/gsd-review-backlog` MUST support promote, keep, and remove actions per item
|
||||
- REQ-BACKLOG-04: Promoted items MUST be renumbered into the active milestone sequence
|
||||
- REQ-SEED-01: Seeds MUST capture the full WHY and WHEN to surface conditions
|
||||
- REQ-SEED-02: `/gsd:new-milestone` MUST scan seeds and present matches
|
||||
- REQ-SEED-02: `/gsd-new-milestone` MUST scan seeds and present matches
|
||||
|
||||
**Produces:**
|
||||
| Artifact | Description |
|
||||
@@ -1070,9 +1070,9 @@ When verification returns `human_needed`, items are persisted as a trackable HUM
|
||||
|
||||
### 44. Persistent Context Threads
|
||||
|
||||
**Command:** `/gsd:thread [name | description]`
|
||||
**Command:** `/gsd-thread [name | description]`
|
||||
|
||||
**Purpose:** Lightweight cross-session knowledge stores for work that spans multiple sessions but doesn't belong to any specific phase. Lighter weight than `/gsd:pause-work` — no phase state, no plan context.
|
||||
**Purpose:** Lightweight cross-session knowledge stores for work that spans multiple sessions but doesn't belong to any specific phase. Lighter weight than `/gsd-pause-work` — no phase state, no plan context.
|
||||
|
||||
**Requirements:**
|
||||
- REQ-THREAD-01: System MUST support create, list, and resume modes
|
||||
@@ -1087,7 +1087,7 @@ When verification returns `human_needed`, items are persisted as a trackable HUM
|
||||
|
||||
### 45. PR Branch Filtering
|
||||
|
||||
**Command:** `/gsd:pr-branch [target branch]`
|
||||
**Command:** `/gsd-pr-branch [target branch]`
|
||||
|
||||
**Purpose:** Create a clean branch suitable for pull requests by filtering out `.planning/` commits. Reviewers see only code changes, not GSD planning artifacts.
|
||||
|
||||
@@ -1115,7 +1115,7 @@ When verification returns `human_needed`, items are persisted as a trackable HUM
|
||||
PreToolUse hook that scans Write/Edit calls targeting `.planning/` for injection patterns. Advisory-only — logs detection for awareness without blocking legitimate operations.
|
||||
|
||||
**3. Workflow Guard Hook** (`gsd-workflow-guard.js`)
|
||||
PreToolUse hook that detects when Claude attempts file edits outside a GSD workflow context. Advises using `/gsd:quick` or `/gsd:fast` instead of direct edits. Configurable via `hooks.workflow_guard` (default: false).
|
||||
PreToolUse hook that detects when Claude attempts file edits outside a GSD workflow context. Advises using `/gsd-quick` or `/gsd-fast` instead of direct edits. Configurable via `hooks.workflow_guard` (default: false).
|
||||
|
||||
**4. CI-Ready Injection Scanner** (`prompt-injection-scan.test.cjs`)
|
||||
Test suite that scans all agent, workflow, and command files for embedded injection vectors.
|
||||
@@ -1142,7 +1142,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 48. Discussion Audit Trail
|
||||
|
||||
**Purpose:** Auto-generate `DISCUSSION-LOG.md` during `/gsd:discuss-phase` for full audit trail of decisions made during discussion.
|
||||
**Purpose:** Auto-generate `DISCUSSION-LOG.md` during `/gsd-discuss-phase` for full audit trail of decisions made during discussion.
|
||||
|
||||
**Requirements:**
|
||||
- REQ-DISCLOG-01: System MUST auto-generate DISCUSSION-LOG.md during discuss-phase
|
||||
@@ -1155,7 +1155,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 49. Forensics
|
||||
|
||||
**Command:** `/gsd:forensics [description]`
|
||||
**Command:** `/gsd-forensics [description]`
|
||||
|
||||
**Purpose:** Post-mortem investigation of failed or stuck GSD workflows.
|
||||
|
||||
@@ -1181,7 +1181,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 50. Milestone Summary
|
||||
|
||||
**Command:** `/gsd:milestone-summary [version]`
|
||||
**Command:** `/gsd-milestone-summary [version]`
|
||||
|
||||
**Purpose:** Generate comprehensive project summary from milestone artifacts for team onboarding.
|
||||
|
||||
@@ -1204,7 +1204,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 51. Workstream Namespacing
|
||||
|
||||
**Command:** `/gsd:workstreams`
|
||||
**Command:** `/gsd-workstreams`
|
||||
|
||||
**Purpose:** Parallel workstreams for concurrent work on different milestone areas.
|
||||
|
||||
@@ -1227,7 +1227,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 52. Manager Dashboard
|
||||
|
||||
**Command:** `/gsd:manager`
|
||||
**Command:** `/gsd-manager`
|
||||
|
||||
**Purpose:** Interactive command center for managing multiple phases from one terminal.
|
||||
|
||||
@@ -1247,7 +1247,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 53. Assumptions Discussion Mode
|
||||
|
||||
**Command:** `/gsd:discuss-phase` with `workflow.discuss_mode: 'assumptions'`
|
||||
**Command:** `/gsd-discuss-phase` with `workflow.discuss_mode: 'assumptions'`
|
||||
|
||||
**Purpose:** Replace interview-style questioning with codebase-first assumption analysis.
|
||||
|
||||
@@ -1273,20 +1273,20 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 54. UI Phase Auto-Detection
|
||||
|
||||
**Part of:** `/gsd:new-project` and `/gsd:progress`
|
||||
**Part of:** `/gsd-new-project` and `/gsd-progress`
|
||||
|
||||
**Purpose:** Automatically detect UI-heavy projects and surface `/gsd:ui-phase` recommendation.
|
||||
**Purpose:** Automatically detect UI-heavy projects and surface `/gsd-ui-phase` recommendation.
|
||||
|
||||
**Requirements:**
|
||||
- REQ-UI-DETECT-01: System MUST detect UI signals in project description (keywords, framework references)
|
||||
- REQ-UI-DETECT-02: System MUST annotate ROADMAP.md phases with `ui_hint` when applicable
|
||||
- REQ-UI-DETECT-03: System MUST suggest `/gsd:ui-phase` in next steps for UI-heavy phases
|
||||
- REQ-UI-DETECT-04: System MUST NOT make `/gsd:ui-phase` mandatory
|
||||
- REQ-UI-DETECT-03: System MUST suggest `/gsd-ui-phase` in next steps for UI-heavy phases
|
||||
- REQ-UI-DETECT-04: System MUST NOT make `/gsd-ui-phase` mandatory
|
||||
|
||||
**Process:**
|
||||
1. **Detect** — Scan project description and tech stack for UI signals (keywords, framework references)
|
||||
2. **Annotate** — Add `ui_hint` markers to applicable phases in ROADMAP.md
|
||||
3. **Surface** — Include `/gsd:ui-phase` recommendation in next steps for UI-heavy phases
|
||||
3. **Surface** — Include `/gsd-ui-phase` recommendation in next steps for UI-heavy phases
|
||||
|
||||
---
|
||||
|
||||
@@ -1365,7 +1365,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 59. Schema Drift Detection
|
||||
|
||||
**Command:** Automatic during `/gsd:execute-phase`
|
||||
**Command:** Automatic during `/gsd-execute-phase`
|
||||
|
||||
**Purpose:** Detect when ORM schema files are modified without corresponding migration or push commands, preventing false-positive verification.
|
||||
|
||||
@@ -1388,7 +1388,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 60. Security Enforcement
|
||||
|
||||
**Command:** `/gsd:secure-phase <N>`
|
||||
**Command:** `/gsd-secure-phase <N>`
|
||||
|
||||
**Purpose:** Threat-model-anchored security verification for phase implementations.
|
||||
|
||||
@@ -1419,7 +1419,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 61. Documentation Generation
|
||||
|
||||
**Command:** `/gsd:docs-update`
|
||||
**Command:** `/gsd-docs-update`
|
||||
|
||||
**Purpose:** Generate and verify project documentation with accuracy checks.
|
||||
|
||||
@@ -1442,7 +1442,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 62. Discuss Chain Mode
|
||||
|
||||
**Flag:** `/gsd:discuss-phase <N> --chain`
|
||||
**Flag:** `/gsd-discuss-phase <N> --chain`
|
||||
|
||||
**Purpose:** Auto-chain discuss, plan, and execute phases in one flow to reduce manual command sequencing.
|
||||
|
||||
@@ -1460,7 +1460,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 63. Single-Phase Autonomous
|
||||
|
||||
**Flag:** `/gsd:autonomous --only N`
|
||||
**Flag:** `/gsd-autonomous --only N`
|
||||
|
||||
**Purpose:** Execute just one phase autonomously instead of all remaining phases.
|
||||
|
||||
@@ -1478,7 +1478,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 64. Scope Reduction Detection
|
||||
|
||||
**Part of:** `/gsd:plan-phase`
|
||||
**Part of:** `/gsd-plan-phase`
|
||||
|
||||
**Purpose:** Prevent silent requirement dropping during plan generation with three-layer defense.
|
||||
|
||||
@@ -1497,7 +1497,7 @@ Test suite that scans all agent, workflow, and command files for embedded inject
|
||||
|
||||
### 65. Claim Provenance Tagging
|
||||
|
||||
**Part of:** `/gsd:research-phase`
|
||||
**Part of:** `/gsd-research-phase`
|
||||
|
||||
**Purpose:** Ensure research claims are tagged with source evidence and assumptions are logged separately.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user