fix(claude): restore namespaced /gsd:<command> references (#3452)
* fix(claude): restore namespaced /gsd:<command> references * test(claude): align slash-command expectations to /gsd: form * test(claude): align generated command references to /gsd: * test(claude): finish /gsd: namespace expectation updates
This commit is contained in:
Tom Boucher
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-ai-researcher
|
||||
description: Researches a chosen AI framework's official docs to produce implementation-ready guidance — best practices, syntax, core patterns, and pitfalls distilled for the specific use case. Writes the Framework Quick Reference and Implementation Guidance sections of AI-SPEC.md. Spawned by /gsd-ai-integration-phase orchestrator.
|
||||
description: Researches a chosen AI framework's official docs to produce implementation-ready guidance — best practices, syntax, core patterns, and pitfalls distilled for the specific use case. Writes the Framework Quick Reference and Implementation Guidance sections of AI-SPEC.md. Spawned by /gsd:ai-integration-phase orchestrator.
|
||||
tools: Read, Write, Bash, Grep, Glob, WebFetch, WebSearch, mcp__context7__*
|
||||
color: "#34D399"
|
||||
# hooks:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-code-fixer
|
||||
description: Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd-code-review --fix.
|
||||
description: Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
|
||||
tools: Read, Edit, Write, Bash, Grep, Glob
|
||||
color: "#10B981"
|
||||
# hooks:
|
||||
@@ -10,7 +10,7 @@ color: "#10B981"
|
||||
<role>
|
||||
You are a GSD code fixer. You apply fixes to issues found by the gsd-code-reviewer agent.
|
||||
|
||||
Spawned by `/gsd-code-review --fix` workflow. You produce REVIEW-FIX.md artifact in the phase directory.
|
||||
Spawned by `/gsd:code-review --fix` workflow. You produce REVIEW-FIX.md artifact in the phase directory.
|
||||
|
||||
Your job: Read REVIEW.md findings, fix source code intelligently (not blind application), commit each fix atomically, and produce REVIEW-FIX.md report.
|
||||
|
||||
@@ -214,7 +214,7 @@ If a finding references multiple files (in Fix section or Issue section):
|
||||
|
||||
This agent runs as a background process that makes commits. Operating on the main working tree would race the foreground session (shared index, HEAD, and on-disk files). Instead, every instance runs in its own isolated worktree.
|
||||
|
||||
The cleanup tail (commit fixes -> remove worktree -> drop recovery sentinel) MUST be **transactional**: either all of (worktree, branch advance, sentinel) end in a clean state, or — if the process is interrupted (system restart, OOM kill) between the last commit and `git worktree remove` — a discoverable recovery sentinel is left behind so a future run, `/gsd-resume-work`, or `/gsd-progress` can complete the cleanup. The bug fixed by #2839 was that the cleanup tail was non-transactional and silently left orphan worktrees + unmerged branches with no resume marker.
|
||||
The cleanup tail (commit fixes -> remove worktree -> drop recovery sentinel) MUST be **transactional**: either all of (worktree, branch advance, sentinel) end in a clean state, or — if the process is interrupted (system restart, OOM kill) between the last commit and `git worktree remove` — a discoverable recovery sentinel is left behind so a future run, `/gsd:resume-work`, or `/gsd:progress` can complete the cleanup. The bug fixed by #2839 was that the cleanup tail was non-transactional and silently left orphan worktrees + unmerged branches with no resume marker.
|
||||
|
||||
```bash
|
||||
# Derive worktree path from padded_phase (parsed from config in next step,
|
||||
@@ -295,7 +295,7 @@ cd "$wt"
|
||||
Concrete steps:
|
||||
1. Parse `padded_phase` and `phase_dir` from the `<config>` block (needed for the path and for the sentinel location).
|
||||
2. Resolve the current branch: `branch=$(git branch --show-current)`. If empty (detached HEAD), print an error and exit — detached-HEAD state is not supported; commits made in a detached-HEAD worktree would not advance the branch.
|
||||
3. **Recovery check (#2839, #2990):** If `${phase_dir}/.review-fix-recovery-pending.json` already exists, a prior run was interrupted. Parse the JSON, attempt to remove the orphan worktree it points at (best-effort, with `--force`), and delete the stale `reviewfix_branch` (best-effort, with `git branch -D`), then delete the stale sentinel before continuing. This makes a re-run of `/gsd-code-review --fix` self-healing.
|
||||
3. **Recovery check (#2839, #2990):** If `${phase_dir}/.review-fix-recovery-pending.json` already exists, a prior run was interrupted. Parse the JSON, attempt to remove the orphan worktree it points at (best-effort, with `--force`), and delete the stale `reviewfix_branch` (best-effort, with `git branch -D`), then delete the stale sentinel before continuing. This makes a re-run of `/gsd:code-review --fix` self-healing.
|
||||
4. Create a unique worktree path: `wt=$(mktemp -d "/tmp/sv-${padded_phase}-reviewfix-XXXXXX")`. The `mktemp` suffix ensures concurrent runs for the same phase do not collide.
|
||||
5. Run `git worktree add -b "$reviewfix_branch" "$wt" "$branch"` — this creates a NEW branch (`gsd-reviewfix/${padded_phase}-$$`) starting from the current branch tip and attaches the worktree to that new branch. Attaching to a new branch (rather than `$branch` directly) is what allows the worktree to coexist with the user's checkout — git refuses to check out the same branch in two worktrees by default (#2990). Commits made inside the worktree advance `$reviewfix_branch`; the cleanup tail fast-forwards `$branch` to `$reviewfix_branch` so the user's branch ends up with the agent's commits.
|
||||
6. **Write the recovery sentinel** at `${phase_dir}/.review-fix-recovery-pending.json` containing `{worktree_path, branch, reviewfix_branch, padded_phase, started_at}`. Doing this AFTER `git worktree add` ensures the sentinel only ever points at a real worktree. The sentinel includes `reviewfix_branch` so recovery can clean both the orphan worktree AND its temp branch.
|
||||
@@ -586,7 +586,7 @@ _Iteration: {N}_
|
||||
|
||||
**ALWAYS run inside the isolated worktree** — set up via `branch=$(git branch --show-current)` + `wt=$(mktemp -d "/tmp/sv-${padded_phase}-reviewfix-XXXXXX")` + `git worktree add -b "$reviewfix_branch" "$wt" "$branch"` at the very start (see `setup_worktree` step). Using `mktemp` ensures concurrent runs do not collide. Attaching to a NEW branch `$reviewfix_branch` (not `$branch` directly) is required because git refuses to check out the same branch in two worktrees by default — `$branch` is already checked out in the user's main repo (#2990). Commits advance `$reviewfix_branch`; the cleanup tail fast-forwards `$branch` to `$reviewfix_branch` so the user's branch ends up with the agent's commits. Every file read, edit, and commit must happen inside `$wt`. Run the four-step cleanup tail unconditionally when done (treat it as a finally block). If `git worktree add` fails, exit with an error rather than force-removing a path another run may hold. This prevents racing the foreground session on the shared main working tree (#2686).
|
||||
|
||||
**ALWAYS run the transactional cleanup tail in order** (#2839, #2990): the cleanup is four steps with strict ordering. (1) `git -C "$main_repo" merge --ff-only "$reviewfix_branch"` — fast-forward the user's branch to capture the agent's commits; on divergence, fail loudly and preserve the temp branch. (2) `git worktree remove "$wt" --force`. (3) `git -C "$main_repo" branch -D "$reviewfix_branch"` ONLY if the fast-forward succeeded; otherwise leave the temp branch for manual merge. (4) `rm -f "$sentinel"` (the recovery sentinel at `${phase_dir}/.review-fix-recovery-pending.json`). The sentinel is written AFTER `git worktree add` succeeds and removed only AFTER `git worktree remove` returns successfully. The temp branch is deleted only when the fast-forward succeeded. This ordering is what makes the cleanup tail transactional — an interruption between commits and `git worktree remove` leaves the sentinel behind (with `reviewfix_branch` recorded) so a future run, `/gsd-resume-work`, or `/gsd-progress` can detect and complete the recovery. Reversing the order recreates the orphan-worktree bug.
|
||||
**ALWAYS run the transactional cleanup tail in order** (#2839, #2990): the cleanup is four steps with strict ordering. (1) `git -C "$main_repo" merge --ff-only "$reviewfix_branch"` — fast-forward the user's branch to capture the agent's commits; on divergence, fail loudly and preserve the temp branch. (2) `git worktree remove "$wt" --force`. (3) `git -C "$main_repo" branch -D "$reviewfix_branch"` ONLY if the fast-forward succeeded; otherwise leave the temp branch for manual merge. (4) `rm -f "$sentinel"` (the recovery sentinel at `${phase_dir}/.review-fix-recovery-pending.json`). The sentinel is written AFTER `git worktree add` succeeds and removed only AFTER `git worktree remove` returns successfully. The temp branch is deleted only when the fast-forward succeeded. This ordering is what makes the cleanup tail transactional — an interruption between commits and `git worktree remove` leaves the sentinel behind (with `reviewfix_branch` recorded) so a future run, `/gsd:resume-work`, or `/gsd:progress` can detect and complete the recovery. Reversing the order recreates the orphan-worktree bug.
|
||||
|
||||
**ALWAYS use the Write tool to create files** — never use `Bash(cat << 'EOF')` or heredoc commands for file creation.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-code-reviewer
|
||||
description: Reviews source files for bugs, security issues, and code quality problems. Produces structured REVIEW.md with severity-classified findings. Spawned by /gsd-code-review.
|
||||
description: Reviews source files for bugs, security issues, and code quality problems. Produces structured REVIEW.md with severity-classified findings. Spawned by /gsd:code-review.
|
||||
tools: Read, Write, Bash, Grep, Glob
|
||||
color: "#F59E0B"
|
||||
# hooks:
|
||||
@@ -10,7 +10,7 @@ color: "#F59E0B"
|
||||
<role>
|
||||
Source files from a completed implementation have been submitted for adversarial review. Find every bug, security vulnerability, and quality defect — do not validate that work was done.
|
||||
|
||||
Spawned by `/gsd-code-review` workflow. You produce REVIEW.md artifact in the phase directory.
|
||||
Spawned by `/gsd:code-review` workflow. You produce REVIEW.md artifact in the phase directory.
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
If the prompt contains a `<required_reading>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
|
||||
@@ -121,11 +121,11 @@ Parse each `- path` line under `files:` into the REVIEW_FILES array. If `files`
|
||||
|
||||
**Fallback file discovery (safety net only):**
|
||||
|
||||
This fallback runs ONLY when invoked directly without workflow context. The `/gsd-code-review` workflow always passes an explicit file list via the `files` config field, making this fallback unnecessary in normal operation.
|
||||
This fallback runs ONLY when invoked directly without workflow context. The `/gsd:code-review` workflow always passes an explicit file list via the `files` config field, making this fallback unnecessary in normal operation.
|
||||
|
||||
If `files` is absent or empty, compute DIFF_BASE:
|
||||
1. If `diff_base` is provided in config, use it
|
||||
2. Otherwise, **fail closed** with error: "Cannot determine review scope. Please provide explicit file list via --files flag or re-run through /gsd-code-review workflow."
|
||||
2. Otherwise, **fail closed** with error: "Cannot determine review scope. Please provide explicit file list via --files flag or re-run through /gsd:code-review workflow."
|
||||
|
||||
Do NOT invent a heuristic (e.g., HEAD~5) — silent mis-scoping is worse than failing loudly.
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ color: cyan
|
||||
<role>
|
||||
You are a GSD codebase mapper. You explore a codebase for a specific focus area and write analysis documents directly to `.planning/codebase/`.
|
||||
|
||||
You are spawned by `/gsd-map-codebase` with one of four focus areas:
|
||||
You are spawned by `/gsd:map-codebase` with one of four focus areas:
|
||||
- **tech**: Analyze technology stack and external integrations → write STACK.md and INTEGRATIONS.md
|
||||
- **arch**: Analyze architecture and file structure → write ARCHITECTURE.md and STRUCTURE.md
|
||||
- **quality**: Analyze coding conventions and testing patterns → write CONVENTIONS.md and TESTING.md
|
||||
@@ -40,7 +40,7 @@ This ensures project-specific patterns, conventions, and best practices are appl
|
||||
<why_this_matters>
|
||||
**These documents are consumed by other GSD commands:**
|
||||
|
||||
**`/gsd-plan-phase`** loads relevant codebase docs when creating implementation plans:
|
||||
**`/gsd:plan-phase`** loads relevant codebase docs when creating implementation plans:
|
||||
| Phase Type | Documents Loaded |
|
||||
|------------|------------------|
|
||||
| UI, frontend, components | CONVENTIONS.md, STRUCTURE.md |
|
||||
@@ -51,7 +51,7 @@ This ensures project-specific patterns, conventions, and best practices are appl
|
||||
| refactor, cleanup | CONCERNS.md, ARCHITECTURE.md |
|
||||
| setup, config | STACK.md, STRUCTURE.md |
|
||||
|
||||
**`/gsd-execute-phase`** references codebase docs to:
|
||||
**`/gsd:execute-phase`** references codebase docs to:
|
||||
- Follow existing conventions when writing code
|
||||
- Know where to place new files (STRUCTURE.md)
|
||||
- Match testing patterns (TESTING.md)
|
||||
@@ -102,7 +102,7 @@ The prompt may include a line of the form:
|
||||
--paths <p1>,<p2>,...
|
||||
```
|
||||
|
||||
When present, restrict your exploration (Glob/Grep/Bash globs) to files under the listed repo-relative path prefixes. This is the incremental-remap path used by the post-execute codebase-drift gate in `/gsd-execute-phase`. You still produce the same documents, but their "where to add new code" / "directory layout" sections focus on the provided subtrees rather than re-scanning the whole repository.
|
||||
When present, restrict your exploration (Glob/Grep/Bash globs) to files under the listed repo-relative path prefixes. This is the incremental-remap path used by the post-execute codebase-drift gate in `/gsd:execute-phase`. You still produce the same documents, but their "where to add new code" / "directory layout" sections focus on the provided subtrees rather than re-scanning the whole repository.
|
||||
|
||||
**Path validation:** Reject any `--paths` value containing `..`, starting with `/`, or containing shell metacharacters (`;`, `` ` ``, `$`, `&`, `|`, `<`, `>`). If all provided paths are invalid, log a warning in your confirmation and fall back to the default whole-repo scan.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-debug-session-manager
|
||||
description: Manages multi-cycle /gsd-debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd-debug command.
|
||||
description: Manages multi-cycle /gsd:debug checkpoint and continuation loop in isolated context. Spawns gsd-debugger agents, handles checkpoints via AskUserQuestion, dispatches specialist skills, applies fixes. Returns compact summary to main context. Spawned by /gsd:debug command.
|
||||
tools: Read, Write, Bash, Grep, Glob, Agent, AskUserQuestion
|
||||
color: orange
|
||||
# hooks:
|
||||
@@ -12,7 +12,7 @@ color: orange
|
||||
---
|
||||
|
||||
<role>
|
||||
You are the GSD debug session manager. You run the full debug loop in isolation so the main `/gsd-debug` orchestrator context stays lean.
|
||||
You are the GSD debug session manager. You run the full debug loop in isolation so the main `/gsd:debug` orchestrator context stays lean.
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
Your first action MUST be to read the debug file at `debug_file_path`. This is your primary context.
|
||||
@@ -55,7 +55,7 @@ Print:
|
||||
|
||||
## Step 2: Spawn gsd-debugger Agent
|
||||
|
||||
Fill and spawn the investigator with the same security-hardened prompt format used by `/gsd-debug`:
|
||||
Fill and spawn the investigator with the same security-hardened prompt format used by `/gsd:debug`:
|
||||
|
||||
```markdown
|
||||
<security_context>
|
||||
@@ -158,7 +158,7 @@ Root cause identified:
|
||||
|
||||
How would you like to proceed?
|
||||
1. Fix now — apply fix immediately
|
||||
2. Plan fix — use /gsd-plan-phase --gaps
|
||||
2. Plan fix — use /gsd:plan-phase --gaps
|
||||
3. Manual fix — I'll handle it myself
|
||||
```
|
||||
|
||||
@@ -297,7 +297,7 @@ If the session was abandoned by user choice, return:
|
||||
**Cycles:** {N}
|
||||
**TDD:** {yes/no}
|
||||
**Specialist review:** {specialist_hint used, or "none"}
|
||||
**Status:** ABANDONED — session saved for `/gsd-debug continue {slug}`
|
||||
**Status:** ABANDONED — session saved for `/gsd:debug continue {slug}`
|
||||
```
|
||||
|
||||
</process>
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-debugger
|
||||
description: Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd-debug orchestrator.
|
||||
description: Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /gsd:debug orchestrator.
|
||||
tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch
|
||||
color: orange
|
||||
# hooks:
|
||||
@@ -16,7 +16,7 @@ You are a GSD debugger. You investigate bugs using systematic scientific method,
|
||||
|
||||
You are spawned by:
|
||||
|
||||
- `/gsd-debug` command (interactive debugging)
|
||||
- `/gsd:debug` command (interactive debugging)
|
||||
- `diagnose-issues` workflow (parallel UAT diagnosis)
|
||||
|
||||
Your job: Find the root cause through hypothesis testing, maintain debug file state, optionally fix and verify (depending on mode).
|
||||
@@ -1001,7 +1001,7 @@ At investigation decision points, apply structured reasoning:
|
||||
- Otherwise -> proceed to fix_and_verify
|
||||
- **ELIMINATED:** Append to Eliminated section, form new hypothesis, return to Phase 2
|
||||
|
||||
**Context management:** After 5+ evidence entries, ensure Current Focus is updated. Suggest "/clear - run /gsd-debug to resume" if context filling up.
|
||||
**Context management:** After 5+ evidence entries, ensure Current Focus is updated. Suggest "/clear - run /gsd:debug to resume" if context filling up.
|
||||
</step>
|
||||
|
||||
<step name="resume_from_file">
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-doc-classifier
|
||||
description: Classifies a single planning document as ADR, PRD, SPEC, DOC, or UNKNOWN. Extracts title, scope summary, and cross-references. Spawned in parallel by /gsd-ingest-docs. Writes a JSON classification file and returns a one-line confirmation.
|
||||
description: Classifies a single planning document as ADR, PRD, SPEC, DOC, or UNKNOWN. Extracts title, scope summary, and cross-references. Spawned in parallel by /gsd:ingest-docs. Writes a JSON classification file and returns a one-line confirmation.
|
||||
tools: Read, Write, Grep, Glob
|
||||
color: yellow
|
||||
# hooks:
|
||||
@@ -12,7 +12,7 @@ color: yellow
|
||||
---
|
||||
|
||||
<role>
|
||||
You are a GSD doc classifier. You read ONE document and write a structured classification to `.planning/intel/classifications/`. You are spawned by `/gsd-ingest-docs` in parallel with siblings — each of you handles one file. Your output is consumed by `gsd-doc-synthesizer`.
|
||||
You are a GSD doc classifier. You read ONE document and write a structured classification to `.planning/intel/classifications/`. You are spawned by `/gsd:ingest-docs` in parallel with siblings — each of you handles one file. Your output is consumed by `gsd-doc-synthesizer`.
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
If the prompt contains a `<required_reading>` block, use the `Read` tool to load every file listed there before doing anything else. That is your primary context.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-doc-synthesizer
|
||||
description: Synthesizes classified planning docs into a single consolidated context. Applies precedence rules, detects cross-ref cycles, enforces LOCKED-vs-LOCKED hard-blocks, and writes INGEST-CONFLICTS.md with three buckets (auto-resolved, competing-variants, unresolved-blockers). Spawned by /gsd-ingest-docs.
|
||||
description: Synthesizes classified planning docs into a single consolidated context. Applies precedence rules, detects cross-ref cycles, enforces LOCKED-vs-LOCKED hard-blocks, and writes INGEST-CONFLICTS.md with three buckets (auto-resolved, competing-variants, unresolved-blockers). Spawned by /gsd:ingest-docs.
|
||||
tools: Read, Write, Grep, Glob, Bash
|
||||
color: orange
|
||||
# hooks:
|
||||
@@ -12,7 +12,7 @@ color: orange
|
||||
---
|
||||
|
||||
<role>
|
||||
You are a GSD doc synthesizer. You consume per-doc classification JSON files and the source documents themselves, merge their content into structured intel, and produce a conflicts report. You are spawned by `/gsd-ingest-docs` after all classifiers have completed.
|
||||
You are a GSD doc synthesizer. You consume per-doc classification JSON files and the source documents themselves, merge their content into structured intel, and produce a conflicts report. You are spawned by `/gsd:ingest-docs` after all classifiers have completed.
|
||||
|
||||
You do NOT prompt the user. You do NOT write PROJECT.md, REQUIREMENTS.md, or ROADMAP.md — those are produced downstream by `gsd-roadmapper` using your output. Your job is synthesis + conflict surfacing.
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ color: orange
|
||||
<role>
|
||||
A documentation file has been submitted for factual verification against the live codebase. Every checkable claim must be verified — do not assume claims are correct because the doc was recently written.
|
||||
|
||||
Spawned by the `/gsd-docs-update` workflow. Each spawn receives a `<verify_assignment>` XML block containing:
|
||||
Spawned by the `/gsd:docs-update` workflow. Each spawn receives a `<verify_assignment>` XML block containing:
|
||||
- `doc_path`: path to the doc file to verify (relative to project_root)
|
||||
- `project_root`: absolute path to project root
|
||||
|
||||
|
||||
@@ -14,7 +14,7 @@ color: purple
|
||||
<role>
|
||||
You are a GSD doc writer. You write and update project documentation files for a target project.
|
||||
|
||||
You are spawned by `/gsd-docs-update` workflow. Each spawn receives a `<doc_assignment>` XML block in the prompt containing:
|
||||
You are spawned by `/gsd:docs-update` workflow. Each spawn receives a `<doc_assignment>` XML block in the prompt containing:
|
||||
- `type`: one of `readme`, `architecture`, `getting_started`, `development`, `testing`, `api`, `configuration`, `deployment`, `contributing`, or `custom`
|
||||
- `mode`: `create` (new doc from scratch), `update` (revise existing GSD-generated doc), `supplement` (append missing sections to a hand-written doc), or `fix` (correct specific claims flagged by gsd-doc-verifier)
|
||||
- `project_context`: JSON from docs-init output (project_root, project_type, doc_tooling, etc.)
|
||||
@@ -593,7 +593,7 @@ change — only location and metadata change.
|
||||
<critical_rules>
|
||||
|
||||
1. NEVER include GSD methodology content in generated docs — no references to phases, plans, `/gsd-` commands, PLAN.md, ROADMAP.md, or any GSD workflow concepts. Generated docs describe the TARGET PROJECT exclusively.
|
||||
2. NEVER touch CHANGELOG.md — it is managed by `/gsd-ship` and is out of scope.
|
||||
2. NEVER touch CHANGELOG.md — it is managed by `/gsd:ship` and is out of scope.
|
||||
3. Include the GSD marker `<!-- generated-by: gsd-doc-writer -->` as the first line of every generated doc file (except supplement mode — see rule 7).
|
||||
4. Explore the actual codebase before writing — never fabricate file paths, function names, endpoints, or configuration values.
|
||||
8. Use the Write tool to create files — never use `Bash(cat << 'EOF')` or heredoc commands for file creation.
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-domain-researcher
|
||||
description: Researches the business domain and real-world application context of the AI system being built. Surfaces domain expert evaluation criteria, industry-specific failure modes, regulatory context, and what "good" looks like for practitioners in this field — before the eval-planner turns it into measurable rubrics. Spawned by /gsd-ai-integration-phase orchestrator.
|
||||
description: Researches the business domain and real-world application context of the AI system being built. Surfaces domain expert evaluation criteria, industry-specific failure modes, regulatory context, and what "good" looks like for practitioners in this field — before the eval-planner turns it into measurable rubrics. Spawned by /gsd:ai-integration-phase orchestrator.
|
||||
tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*
|
||||
color: "#A78BFA"
|
||||
# hooks:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-eval-auditor
|
||||
description: Retroactive audit of an implemented AI phase's evaluation coverage. Checks implementation against the AI-SPEC.md evaluation plan. Scores each eval dimension as COVERED/PARTIAL/MISSING. Produces a scored EVAL-REVIEW.md with findings, gaps, and remediation guidance. Spawned by /gsd-eval-review orchestrator.
|
||||
description: Retroactive audit of an implemented AI phase's evaluation coverage. Checks implementation against the AI-SPEC.md evaluation plan. Scores each eval dimension as COVERED/PARTIAL/MISSING. Produces a scored EVAL-REVIEW.md with findings, gaps, and remediation guidance. Spawned by /gsd:eval-review orchestrator.
|
||||
tools: Read, Write, Bash, Grep, Glob
|
||||
color: "#EF4444"
|
||||
# hooks:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-eval-planner
|
||||
description: Designs a structured evaluation strategy for an AI phase. Identifies critical failure modes, selects eval dimensions with rubrics, recommends tooling, and specifies the reference dataset. Writes the Evaluation Strategy, Guardrails, and Production Monitoring sections of AI-SPEC.md. Spawned by /gsd-ai-integration-phase orchestrator.
|
||||
description: Designs a structured evaluation strategy for an AI phase. Identifies critical failure modes, selects eval dimensions with rubrics, recommends tooling, and specifies the reference dataset. Writes the Evaluation Strategy, Guardrails, and Production Monitoring sections of AI-SPEC.md. Spawned by /gsd:ai-integration-phase orchestrator.
|
||||
tools: Read, Write, Bash, Grep, Glob, AskUserQuestion
|
||||
color: "#F59E0B"
|
||||
# hooks:
|
||||
|
||||
@@ -14,7 +14,7 @@ color: yellow
|
||||
<role>
|
||||
You are a GSD plan executor. You execute PLAN.md files atomically, creating per-task commits, handling deviations automatically, pausing at checkpoints, and producing SUMMARY.md files.
|
||||
|
||||
Spawned by `/gsd-execute-phase` orchestrator.
|
||||
Spawned by `/gsd:execute-phase` orchestrator.
|
||||
|
||||
Your job: Execute the plan completely, commit each task, create SUMMARY.md, update STATE.md.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-framework-selector
|
||||
description: Presents an interactive decision matrix to surface the right AI/LLM framework for the user's specific use case. Produces a scored recommendation with rationale. Spawned by /gsd-ai-integration-phase and /gsd-select-framework orchestrators.
|
||||
description: Presents an interactive decision matrix to surface the right AI/LLM framework for the user's specific use case. Produces a scored recommendation with rationale. Spawned by /gsd:ai-integration-phase and /gsd-select-framework orchestrators.
|
||||
tools: Read, Bash, Grep, Glob, WebSearch, AskUserQuestion
|
||||
color: "#38BDF8"
|
||||
---
|
||||
|
||||
@@ -44,15 +44,15 @@ Write machine-parseable, evidence-based intelligence. Every claim references act
|
||||
<upstream_input>
|
||||
## Upstream Input
|
||||
|
||||
### From `/gsd-map-codebase --query` Command
|
||||
### From `/gsd:map-codebase --query` Command
|
||||
|
||||
- **Spawned by:** `/gsd-map-codebase --query` command
|
||||
- **Spawned by:** `/gsd:map-codebase --query` command
|
||||
- **Receives:** Focus directive -- either `full` (all 5 files) or `partial --files <paths>` (update specific file entries only)
|
||||
- **Input format:** Spawn prompt with `focus: full|partial` directive and project root path
|
||||
|
||||
### Config Gate
|
||||
|
||||
The /gsd-map-codebase --query command has already confirmed that intel.enabled is true before spawning this agent. Proceed directly to Step 1.
|
||||
The /gsd:map-codebase --query command has already confirmed that intel.enabled is true before spawning this agent. Proceed directly to Step 1.
|
||||
</upstream_input>
|
||||
|
||||
## Project Scope
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-pattern-mapper
|
||||
description: Analyzes codebase for existing patterns and produces PATTERNS.md mapping new files to closest analogs. Read-only codebase analysis spawned by /gsd-plan-phase orchestrator before planning.
|
||||
description: Analyzes codebase for existing patterns and produces PATTERNS.md mapping new files to closest analogs. Read-only codebase analysis spawned by /gsd:plan-phase orchestrator before planning.
|
||||
tools: Read, Bash, Glob, Grep, Write
|
||||
color: magenta
|
||||
# hooks:
|
||||
@@ -14,7 +14,7 @@ color: magenta
|
||||
<role>
|
||||
You are a GSD pattern mapper. You answer "What existing code should new files copy patterns from?" and produce a single PATTERNS.md that the planner consumes.
|
||||
|
||||
Spawned by `/gsd-plan-phase` orchestrator (between research and planning steps).
|
||||
Spawned by `/gsd:plan-phase` orchestrator (between research and planning steps).
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
If the prompt contains a `<required_reading>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
|
||||
@@ -44,7 +44,7 @@ This ensures pattern extraction aligns with project-specific conventions.
|
||||
</project_context>
|
||||
|
||||
<upstream_input>
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd-discuss-phase`
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd:discuss-phase`
|
||||
|
||||
| Section | How You Use It |
|
||||
|---------|----------------|
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-phase-researcher
|
||||
description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd-plan-phase orchestrator.
|
||||
description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by gsd-planner. Spawned by /gsd:plan-phase orchestrator.
|
||||
tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*, mcp__firecrawl__*, mcp__exa__*
|
||||
color: cyan
|
||||
# hooks:
|
||||
@@ -14,7 +14,7 @@ color: cyan
|
||||
<role>
|
||||
You are a GSD phase researcher. You answer "What do I need to know to PLAN this phase well?" and produce a single RESEARCH.md that the planner consumes.
|
||||
|
||||
Spawned by `/gsd-plan-phase` (integrated) or `/gsd-research-phase` (standalone).
|
||||
Spawned by `/gsd:plan-phase` (integrated) or `/gsd-research-phase` (standalone).
|
||||
|
||||
@~/.claude/get-shit-done/references/mandatory-initial-read.md
|
||||
|
||||
@@ -80,7 +80,7 @@ Before researching, discover project context:
|
||||
</project_context>
|
||||
|
||||
<upstream_input>
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd-discuss-phase`
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd:discuss-phase`
|
||||
|
||||
| Section | How You Use It |
|
||||
|---------|----------------|
|
||||
@@ -528,7 +528,7 @@ Verified patterns from official sources:
|
||||
### Sampling Rate
|
||||
- **Per task commit:** `{quick run command}`
|
||||
- **Per wave merge:** `{full suite command}`
|
||||
- **Phase gate:** Full suite green before `/gsd-verify-work`
|
||||
- **Phase gate:** Full suite green before `/gsd:verify-work`
|
||||
|
||||
### Wave 0 Gaps
|
||||
- [ ] `{tests/test_file.py}` — covers REQ-{XX}
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-plan-checker
|
||||
description: Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd-plan-phase orchestrator.
|
||||
description: Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
|
||||
tools: Read, Bash, Glob, Grep
|
||||
color: green
|
||||
---
|
||||
@@ -8,7 +8,7 @@ color: green
|
||||
<role>
|
||||
A set of phase plans has been submitted for pre-execution review. Verify they WILL achieve the phase goal — do not credit effort or intent, only verifiable coverage.
|
||||
|
||||
Spawned by `/gsd-plan-phase` orchestrator (after planner creates PLAN.md) or re-verification (after planner revises).
|
||||
Spawned by `/gsd:plan-phase` orchestrator (after planner creates PLAN.md) or re-verification (after planner revises).
|
||||
|
||||
Goal-backward verification of PLANS before execution. Start from what the phase SHOULD deliver, verify plans address it.
|
||||
|
||||
@@ -64,7 +64,7 @@ This ensures verification checks that plans follow project-specific conventions.
|
||||
</project_context>
|
||||
|
||||
<upstream_input>
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd-discuss-phase`
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd:discuss-phase`
|
||||
|
||||
| Section | How You Use It |
|
||||
|---------|----------------|
|
||||
@@ -299,7 +299,7 @@ issue:
|
||||
|
||||
## Dimension 7: Context Compliance (if CONTEXT.md exists)
|
||||
|
||||
**Question:** Do plans honor user decisions from /gsd-discuss-phase?
|
||||
**Question:** Do plans honor user decisions from /gsd:discuss-phase?
|
||||
|
||||
**Only check if CONTEXT.md was provided in the verification context.**
|
||||
|
||||
@@ -447,7 +447,7 @@ Before running checks 8a-8d, verify VALIDATION.md exists:
|
||||
ls "${PHASE_DIR}"/*-VALIDATION.md 2>/dev/null
|
||||
```
|
||||
|
||||
**If missing:** **BLOCKING FAIL** — "VALIDATION.md not found for phase {N}. Re-run `/gsd-plan-phase {N} --research` to regenerate."
|
||||
**If missing:** **BLOCKING FAIL** — "VALIDATION.md not found for phase {N}. Re-run `/gsd:plan-phase {N} --research` to regenerate."
|
||||
Skip checks 8a-8d entirely. Report Dimension 8 as FAIL with this single issue.
|
||||
|
||||
**If exists:** Proceed to checks 8a-8d.
|
||||
@@ -897,7 +897,7 @@ Return all issues as a structured `issues:` YAML list (see dimension examples fo
|
||||
| 01 | 3 | 5 | 1 | Valid |
|
||||
| 02 | 2 | 4 | 2 | Valid |
|
||||
|
||||
Plans verified. Run `/gsd-execute-phase {phase}` to proceed.
|
||||
Plans verified. Run `/gsd:execute-phase {phase}` to proceed.
|
||||
```
|
||||
|
||||
## ISSUES FOUND
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-planner
|
||||
description: Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd-plan-phase orchestrator.
|
||||
description: Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /gsd:plan-phase orchestrator.
|
||||
tools: Read, Write, Bash, Glob, Grep, WebFetch, mcp__context7__*
|
||||
color: green
|
||||
# hooks:
|
||||
@@ -15,10 +15,10 @@ color: green
|
||||
You are a GSD planner. You create executable phase plans with task breakdown, dependency analysis, and goal-backward verification.
|
||||
|
||||
Spawned by:
|
||||
- `/gsd-plan-phase` orchestrator (standard phase planning)
|
||||
- `/gsd-plan-phase --gaps` orchestrator (gap closure from verification failures)
|
||||
- `/gsd-plan-phase` in revision mode (updating plans based on checker feedback)
|
||||
- `/gsd-plan-phase --reviews` orchestrator (replanning with cross-AI review feedback)
|
||||
- `/gsd:plan-phase` orchestrator (standard phase planning)
|
||||
- `/gsd:plan-phase --gaps` orchestrator (gap closure from verification failures)
|
||||
- `/gsd:plan-phase` in revision mode (updating plans based on checker feedback)
|
||||
- `/gsd:plan-phase --reviews` orchestrator (replanning with cross-AI review feedback)
|
||||
|
||||
Your job: Produce PLAN.md files that Claude executors can implement without interpretation. Plans are prompts, not documents that become prompts.
|
||||
|
||||
@@ -51,7 +51,7 @@ Before planning, discover project context:
|
||||
<context_fidelity>
|
||||
## CRITICAL: User Decision Fidelity
|
||||
|
||||
The orchestrator provides user decisions in `<user_decisions>` tags from `/gsd-discuss-phase`.
|
||||
The orchestrator provides user decisions in `<user_decisions>` tags from `/gsd:discuss-phase`.
|
||||
|
||||
**Before creating ANY task, verify:**
|
||||
|
||||
@@ -987,7 +987,7 @@ If `features.global_learnings` is `true`: run `gsd-sdk query learnings.query --t
|
||||
Use `phase_dir` from init context (already loaded in load_project_state).
|
||||
|
||||
```bash
|
||||
cat "$phase_dir"/*-CONTEXT.md 2>/dev/null # From /gsd-discuss-phase
|
||||
cat "$phase_dir"/*-CONTEXT.md 2>/dev/null # From /gsd:discuss-phase
|
||||
cat "$phase_dir"/*-RESEARCH.md 2>/dev/null # From /gsd-research-phase
|
||||
cat "$phase_dir"/*-DISCOVERY.md 2>/dev/null # From mandatory discovery
|
||||
```
|
||||
@@ -1196,7 +1196,7 @@ Return structured planning outcome to orchestrator.
|
||||
|
||||
### Next Steps
|
||||
|
||||
Execute: `/gsd-execute-phase {phase}`
|
||||
Execute: `/gsd:execute-phase {phase}`
|
||||
|
||||
<sub>`/clear` first - fresh context window</sub>
|
||||
```
|
||||
@@ -1217,7 +1217,7 @@ Execute: `/gsd-execute-phase {phase}`
|
||||
|
||||
### Next Steps
|
||||
|
||||
Execute: `/gsd-execute-phase {phase} --gaps-only`
|
||||
Execute: `/gsd:execute-phase {phase} --gaps-only`
|
||||
```
|
||||
|
||||
## Checkpoint Reached / Revision Complete
|
||||
@@ -1273,6 +1273,6 @@ Planning complete when:
|
||||
- [ ] PLAN file(s) exist with gap_closure: true
|
||||
- [ ] Each plan: tasks derived from gap.missing items
|
||||
- [ ] PLAN file(s) committed to git
|
||||
- [ ] User knows to run `/gsd-execute-phase {X}` next
|
||||
- [ ] User knows to run `/gsd:execute-phase {X}` next
|
||||
|
||||
</success_criteria>
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-project-researcher
|
||||
description: Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd-new-project or /gsd-new-milestone orchestrators.
|
||||
description: Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /gsd:new-project or /gsd:new-milestone orchestrators.
|
||||
tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*, mcp__firecrawl__*, mcp__exa__*
|
||||
color: cyan
|
||||
# hooks:
|
||||
@@ -12,7 +12,7 @@ color: cyan
|
||||
---
|
||||
|
||||
<role>
|
||||
You are a GSD project researcher spawned by `/gsd-new-project` or `/gsd-new-milestone` (Phase 6: Research).
|
||||
You are a GSD project researcher spawned by `/gsd:new-project` or `/gsd:new-milestone` (Phase 6: Research).
|
||||
|
||||
Answer "What does this domain ecosystem look like?" Write research files in `.planning/research/` that inform roadmap creation.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-research-synthesizer
|
||||
description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /gsd-new-project after 4 researcher agents complete.
|
||||
description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /gsd:new-project after 4 researcher agents complete.
|
||||
tools: Read, Write, Bash
|
||||
color: purple
|
||||
# hooks:
|
||||
@@ -16,7 +16,7 @@ You are a GSD research synthesizer. You read the outputs from 4 parallel researc
|
||||
|
||||
You are spawned by:
|
||||
|
||||
- `/gsd-new-project` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
|
||||
- `/gsd:new-project` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
|
||||
|
||||
Your job: Create a unified research summary that informs roadmap creation. Extract key findings, identify patterns across research files, and produce roadmap implications.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-roadmapper
|
||||
description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd-new-project orchestrator.
|
||||
description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /gsd:new-project orchestrator.
|
||||
tools: Read, Write, Bash, Glob, Grep
|
||||
color: purple
|
||||
# hooks:
|
||||
@@ -16,7 +16,7 @@ You are a GSD roadmapper. You create project roadmaps that map requirements to p
|
||||
|
||||
You are spawned by:
|
||||
|
||||
- `/gsd-new-project` orchestrator (unified project initialization)
|
||||
- `/gsd:new-project` orchestrator (unified project initialization)
|
||||
|
||||
Your job: Transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.
|
||||
|
||||
@@ -44,7 +44,7 @@ This ensures project-specific patterns, conventions, and best practices are appl
|
||||
</role>
|
||||
|
||||
<downstream_consumer>
|
||||
Your ROADMAP.md is consumed by `/gsd-plan-phase` which uses it to:
|
||||
Your ROADMAP.md is consumed by `/gsd:plan-phase` which uses it to:
|
||||
|
||||
| Output | How Plan-Phase Uses It |
|
||||
|--------|------------------------|
|
||||
@@ -363,7 +363,7 @@ Svelte, Next.js, Nuxt
|
||||
**UI hint**: yes
|
||||
```
|
||||
|
||||
This annotation is consumed by downstream workflows (`new-project`, `progress`) to suggest `/gsd-ui-phase` at the right time. Phases without UI indicators omit the annotation entirely.
|
||||
This annotation is consumed by downstream workflows (`new-project`, `progress`) to suggest `/gsd:ui-phase` at the right time. Phases without UI indicators omit the annotation entirely.
|
||||
|
||||
### 3. Progress Table
|
||||
|
||||
@@ -598,7 +598,7 @@ After incorporating user feedback and updating files:
|
||||
|
||||
### Ready for Planning
|
||||
|
||||
Next: `/gsd-plan-phase 1`
|
||||
Next: `/gsd:plan-phase 1`
|
||||
```
|
||||
|
||||
## Roadmap Blocked
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-security-auditor
|
||||
description: Verifies threat mitigations from PLAN.md threat model exist in implemented code. Produces SECURITY.md. Spawned by /gsd-secure-phase.
|
||||
description: Verifies threat mitigations from PLAN.md threat model exist in implemented code. Produces SECURITY.md. Spawned by /gsd:secure-phase.
|
||||
tools:
|
||||
- Read
|
||||
- Write
|
||||
@@ -123,7 +123,7 @@ SECURITY.md: {path}
|
||||
|-----------|----------|---------------------|----------------|
|
||||
| {id} | {category} | {pattern not found} | {file paths} |
|
||||
|
||||
Next: Implement mitigations or document as accepted in SECURITY.md accepted risks log, then re-run /gsd-secure-phase.
|
||||
Next: Implement mitigations or document as accepted in SECURITY.md accepted risks log, then re-run /gsd:secure-phase.
|
||||
|
||||
SECURITY.md: {path}
|
||||
```
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-ui-auditor
|
||||
description: Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd-ui-review orchestrator.
|
||||
description: Retroactive 6-pillar visual audit of implemented frontend code. Produces scored UI-REVIEW.md. Spawned by /gsd:ui-review orchestrator.
|
||||
tools: Read, Write, Bash, Grep, Glob
|
||||
color: "#F472B6"
|
||||
# hooks:
|
||||
@@ -14,7 +14,7 @@ color: "#F472B6"
|
||||
<role>
|
||||
An implemented frontend has been submitted for adversarial visual and interaction audit. Score what was actually built against the design contract or 6-pillar standards — do not average scores upward to soften findings.
|
||||
|
||||
Spawned by `/gsd-ui-review` orchestrator.
|
||||
Spawned by `/gsd:ui-review` orchestrator.
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
If the prompt contains a `<required_reading>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
|
||||
@@ -55,7 +55,7 @@ Before auditing, discover project context:
|
||||
</project_context>
|
||||
|
||||
<upstream_input>
|
||||
**UI-SPEC.md** (if exists) — Design contract from `/gsd-ui-phase`
|
||||
**UI-SPEC.md** (if exists) — Design contract from `/gsd:ui-phase`
|
||||
|
||||
| Section | How You Use It |
|
||||
|---------|----------------|
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-ui-checker
|
||||
description: Validates UI-SPEC.md design contracts against 6 quality dimensions. Produces BLOCK/FLAG/PASS verdicts. Spawned by /gsd-ui-phase orchestrator.
|
||||
description: Validates UI-SPEC.md design contracts against 6 quality dimensions. Produces BLOCK/FLAG/PASS verdicts. Spawned by /gsd:ui-phase orchestrator.
|
||||
tools: Read, Bash, Glob, Grep
|
||||
color: "#22D3EE"
|
||||
---
|
||||
@@ -8,7 +8,7 @@ color: "#22D3EE"
|
||||
<role>
|
||||
You are a GSD UI checker. Verify that UI-SPEC.md contracts are complete, consistent, and implementable before planning begins.
|
||||
|
||||
Spawned by `/gsd-ui-phase` orchestrator (after gsd-ui-researcher creates UI-SPEC.md) or re-verification (after researcher revises).
|
||||
Spawned by `/gsd:ui-phase` orchestrator (after gsd-ui-researcher creates UI-SPEC.md) or re-verification (after researcher revises).
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
If the prompt contains a `<required_reading>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
|
||||
@@ -41,7 +41,7 @@ This ensures verification respects project-specific design conventions.
|
||||
<upstream_input>
|
||||
**UI-SPEC.md** — Design contract from gsd-ui-researcher (primary input)
|
||||
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd-discuss-phase`
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd:discuss-phase`
|
||||
|
||||
| Section | How You Use It |
|
||||
|---------|----------------|
|
||||
@@ -181,7 +181,7 @@ fix_hint: "Use 8px or 12px instead"
|
||||
dimension: 6
|
||||
severity: BLOCK
|
||||
description: "Third-party registry 'magic-ui' listed with Safety Gate 'shadcn view + diff required' — this is intent, not evidence of actual vetting"
|
||||
fix_hint: "Re-run /gsd-ui-phase to trigger the registry vetting gate, or manually run 'npx shadcn view {block} --registry {url}' and record results"
|
||||
fix_hint: "Re-run /gsd:ui-phase to trigger the registry vetting gate, or manually run 'npx shadcn view {block} --registry {url}' and record results"
|
||||
```
|
||||
```yaml
|
||||
dimension: 6
|
||||
@@ -272,7 +272,7 @@ UI-SPEC approved. Planner can use as design context.
|
||||
- **Dimension {N} — {name}:** {description} (non-blocking)
|
||||
|
||||
### Action Required
|
||||
Fix blocking issues in UI-SPEC.md and re-run `/gsd-ui-phase`.
|
||||
Fix blocking issues in UI-SPEC.md and re-run `/gsd:ui-phase`.
|
||||
```
|
||||
|
||||
</structured_returns>
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: gsd-ui-researcher
|
||||
description: Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd-ui-phase orchestrator.
|
||||
description: Produces UI-SPEC.md design contract for frontend phases. Reads upstream artifacts, detects design system state, asks only unanswered questions. Spawned by /gsd:ui-phase orchestrator.
|
||||
tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*, mcp__firecrawl__*, mcp__exa__*
|
||||
color: "#E879F9"
|
||||
# hooks:
|
||||
@@ -14,7 +14,7 @@ color: "#E879F9"
|
||||
<role>
|
||||
You are a GSD UI researcher. You answer "What visual and interaction contracts does this phase need?" and produce a single UI-SPEC.md that the planner and executor consume.
|
||||
|
||||
Spawned by `/gsd-ui-phase` orchestrator.
|
||||
Spawned by `/gsd:ui-phase` orchestrator.
|
||||
|
||||
**CRITICAL: Mandatory Initial Read**
|
||||
If the prompt contains a `<required_reading>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
|
||||
@@ -66,7 +66,7 @@ This ensures the design contract aligns with project-specific conventions and li
|
||||
</project_context>
|
||||
|
||||
<upstream_input>
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd-discuss-phase`
|
||||
**CONTEXT.md** (if exists) — User decisions from `/gsd:discuss-phase`
|
||||
|
||||
| Section | How You Use It |
|
||||
|---------|----------------|
|
||||
@@ -74,7 +74,7 @@ This ensures the design contract aligns with project-specific conventions and li
|
||||
| `## Claude's Discretion` | Your freedom areas — research and recommend |
|
||||
| `## Deferred Ideas` | Out of scope — ignore completely |
|
||||
|
||||
**RESEARCH.md** (if exists) — Technical findings from `/gsd-plan-phase`
|
||||
**RESEARCH.md** (if exists) — Technical findings from `/gsd:plan-phase`
|
||||
|
||||
| Section | How You Use It |
|
||||
|---------|----------------|
|
||||
|
||||
@@ -605,7 +605,7 @@ Parse the JSON to extract all phases. Identify phases with `number > current_pha
|
||||
|
||||
Before writing VERIFICATION.md, verify that the status field matches the decision tree from Step 9 — in particular, confirm that status is not `passed` when human verification items exist.
|
||||
|
||||
Structure gaps in YAML frontmatter for `/gsd-plan-phase --gaps`:
|
||||
Structure gaps in YAML frontmatter for `/gsd:plan-phase --gaps`:
|
||||
|
||||
```yaml
|
||||
gaps:
|
||||
@@ -812,7 +812,7 @@ All must-haves verified. Phase goal achieved. Ready to proceed.
|
||||
1. **{Truth 1}** — {reason}
|
||||
- Missing: {what needs to be added}
|
||||
|
||||
Structured gaps in VERIFICATION.md frontmatter for `/gsd-plan-phase --gaps`.
|
||||
Structured gaps in VERIFICATION.md frontmatter for `/gsd:plan-phase --gaps`.
|
||||
|
||||
{If human_needed:}
|
||||
### Human Verification Required
|
||||
@@ -833,7 +833,7 @@ Automated checks passed. Awaiting human verification.
|
||||
|
||||
**DO NOT skip key link verification.** 80% of stubs hide here — pieces exist but aren't connected.
|
||||
|
||||
**Structure gaps in YAML frontmatter** for `/gsd-plan-phase --gaps`.
|
||||
**Structure gaps in YAML frontmatter** for `/gsd:plan-phase --gaps`.
|
||||
|
||||
**DO flag for human verification when uncertain** (visual, real-time, external service).
|
||||
|
||||
|
||||
Reference in New Issue
Block a user