pi-gsd 2.0.22 → 2.0.23

package/.gsd/harnesses/pi/get-shit-done/agents/gsd-codebase-mapper.md

@@ -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
@@ -29,18 +29,18 @@ If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool t
 <why_this_matters>
 **These documents are consumed by other GSD commands:**
 
-**`/gsd:plan-phase`** loads relevant codebase docs when creating implementation plans:
-| Phase Type | Documents Loaded |
-|------------|------------------|
-| UI, frontend, components | CONVENTIONS.md, STRUCTURE.md |
-| API, backend, endpoints | ARCHITECTURE.md, CONVENTIONS.md |
-| database, schema, models | ARCHITECTURE.md, STACK.md |
-| testing, tests | TESTING.md, CONVENTIONS.md |
-| integration, external API | INTEGRATIONS.md, STACK.md |
-| refactor, cleanup | CONCERNS.md, ARCHITECTURE.md |
-| setup, config | STACK.md, STRUCTURE.md |
-
-**`/gsd:execute-phase`** references codebase docs to:
+**`/gsd-plan-phase`** loads relevant codebase docs when creating implementation plans:
+| Phase Type                | Documents Loaded                |
+| ------------------------- | ------------------------------- |
+| UI, frontend, components  | CONVENTIONS.md, STRUCTURE.md    |
+| API, backend, endpoints   | ARCHITECTURE.md, CONVENTIONS.md |
+| database, schema, models  | ARCHITECTURE.md, STACK.md       |
+| testing, tests            | TESTING.md, CONVENTIONS.md      |
+| integration, external API | INTEGRATIONS.md, STACK.md       |
+| refactor, cleanup         | CONCERNS.md, ARCHITECTURE.md    |
+| setup, config             | STACK.md, STRUCTURE.md          |
+
+**`/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)

package/.gsd/harnesses/pi/get-shit-done/agents/gsd-debugger.md

@@ -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
 permissionMode: acceptEdits
 color: orange
@@ -17,7 +17,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).
@@ -76,12 +76,12 @@ When debugging, return to foundational truths:
 
 ## Cognitive Biases to Avoid
 
-| Bias | Trap | Antidote |
-|------|------|----------|
-| **Confirmation** | Only look for evidence supporting your hypothesis | Actively seek disconfirming evidence. "What would prove me wrong?" |
-| **Anchoring** | First explanation becomes your anchor | Generate 3+ independent hypotheses before investigating any |
-| **Availability** | Recent bugs → assume similar cause | Treat each bug as novel until evidence suggests otherwise |
-| **Sunk Cost** | Spent 2 hours on one path, keep going despite evidence | Every 30 min: "If I started fresh, is this still the path I'd take?" |
+| Bias             | Trap                                                   | Antidote                                                             |
+| ---------------- | ------------------------------------------------------ | -------------------------------------------------------------------- |
+| **Confirmation** | Only look for evidence supporting your hypothesis      | Actively seek disconfirming evidence. "What would prove me wrong?"   |
+| **Anchoring**    | First explanation becomes your anchor                  | Generate 3+ independent hypotheses before investigating any          |
+| **Availability** | Recent bugs → assume similar cause                     | Treat each bug as novel until evidence suggests otherwise            |
+| **Sunk Cost**    | Spent 2 hours on one path, keep going despite evidence | Every 30 min: "If I started fresh, is this still the path I'd take?" |
 
 ## Systematic Investigation Disciplines
 
@@ -217,13 +217,13 @@ try {
 
 ## Hypothesis Testing Pitfalls
 
-| Pitfall | Problem | Solution |
-|---------|---------|----------|
-| Testing multiple hypotheses at once | You change three things and it works - which one fixed it? | Test one hypothesis at a time |
-| Confirmation bias | Only looking for evidence that confirms your hypothesis | Actively seek disconfirming evidence |
-| Acting on weak evidence | "It seems like maybe this could be..." | Wait for strong, unambiguous evidence |
-| Not documenting results | Forget what you tested, repeat experiments | Write down each hypothesis and result |
-| Abandoning rigor under pressure | "Let me just try this..." | Double down on method when pressure increases |
+| Pitfall                             | Problem                                                    | Solution                                      |
+| ----------------------------------- | ---------------------------------------------------------- | --------------------------------------------- |
+| Testing multiple hypotheses at once | You change three things and it works - which one fixed it? | Test one hypothesis at a time                 |
+| Confirmation bias                   | Only looking for evidence that confirms your hypothesis    | Actively seek disconfirming evidence          |
+| Acting on weak evidence             | "It seems like maybe this could be..."                     | Wait for strong, unambiguous evidence         |
+| Not documenting results             | Forget what you tested, repeat experiments                 | Write down each hypothesis and result         |
+| Abandoning rigor under pressure     | "Let me just try this..."                                  | Double down on method when pressure increases |
 
 </hypothesis_testing>
 
@@ -445,16 +445,16 @@ MISMATCH: Checker looks in wrong directory → hooks "not found" → reported as
 
 ## Technique Selection
 
-| Situation | Technique |
-|-----------|-----------|
-| Large codebase, many files | Binary search |
-| Confused about what's happening | Rubber duck, Observability first |
-| Complex system, many interactions | Minimal reproduction |
-| Know the desired output | Working backwards |
-| Used to work, now doesn't | Differential debugging, Git bisect |
-| Many possible causes | Comment out everything, Binary search |
-| Paths, URLs, keys constructed from variables | Follow the indirection |
-| Always | Observability first (before making changes) |
+| Situation                                    | Technique                                   |
+| -------------------------------------------- | ------------------------------------------- |
+| Large codebase, many files                   | Binary search                               |
+| Confused about what's happening              | Rubber duck, Observability first            |
+| Complex system, many interactions            | Minimal reproduction                        |
+| Know the desired output                      | Working backwards                           |
+| Used to work, now doesn't                    | Differential debugging, Git bisect          |
+| Many possible causes                         | Comment out everything, Binary search       |
+| Paths, URLs, keys constructed from variables | Follow the indirection                      |
+| Always                                       | Observability first (before making changes) |
 
 ## Combining Techniques
 
@@ -872,15 +872,15 @@ files_changed: []
 
 ## Update Rules
 
-| Section | Rule | When |
-|---------|------|------|
-| Frontmatter.status | OVERWRITE | Each phase transition |
-| Frontmatter.updated | OVERWRITE | Every file update |
-| Current Focus | OVERWRITE | Before every action |
-| Symptoms | IMMUTABLE | After gathering complete |
-| Eliminated | APPEND | When hypothesis disproved |
-| Evidence | APPEND | After each finding |
-| Resolution | OVERWRITE | As understanding evolves |
+| Section             | Rule      | When                      |
+| ------------------- | --------- | ------------------------- |
+| Frontmatter.status  | OVERWRITE | Each phase transition     |
+| Frontmatter.updated | OVERWRITE | Every file update         |
+| Current Focus       | OVERWRITE | Before every action       |
+| Symptoms            | IMMUTABLE | After gathering complete  |
+| Eliminated          | APPEND    | When hypothesis disproved |
+| Evidence            | APPEND    | After each finding        |
+| Resolution          | OVERWRITE | As understanding evolves  |
 
 **CRITICAL:** Update the file BEFORE taking action, not after. If context resets mid-action, the file shows what was about to happen.
 
@@ -895,7 +895,7 @@ gathering -> investigating -> fixing -> verifying -> awaiting_human_verify -> re
 
 ## Resume Behavior
 
-When reading debug file after /clear:
+When reading debug file after /new:
 1. Parse frontmatter -> know status
 2. Read Current Focus -> know exactly what was happening
 3. Read Eliminated -> know what NOT to retry
@@ -992,7 +992,7 @@ Gather symptoms through questioning. Update file after EACH answer.
   - 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 "/new - run /gsd-debug to resume" if context filling up.
 </step>
 
 <step name="resume_from_file">
@@ -1366,7 +1366,7 @@ Check for mode flags in prompt context:
 - [ ] Current Focus always reflects NOW
 - [ ] Evidence appended for every finding
 - [ ] Eliminated prevents re-investigation
-- [ ] Can resume perfectly from any /clear
+- [ ] Can resume perfectly from any /new
 - [ ] Root cause confirmed with evidence before fixing
 - [ ] Fix verified against original symptoms
 - [ ] Appropriate return format based on mode

package/.gsd/harnesses/pi/get-shit-done/agents/gsd-executor.md

@@ -15,7 +15,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.
 
@@ -322,13 +322,13 @@ git add src/types/user.ts
 
 **3. Commit type:**
 
-| Type       | When                                            |
-| ---------- | ----------------------------------------------- |
-| `feat`     | New feature, endpoint, component                |
-| `fix`      | Bug fix, error correction                       |
-| `test`     | Test-only changes (TDD RED)                     |
-| `refactor` | Code cleanup, no behavior change                |
-| `chore`    | Config, tooling, dependencies                   |
+| Type       | When                             |
+| ---------- | -------------------------------- |
+| `feat`     | New feature, endpoint, component |
+| `fix`      | Bug fix, error correction        |
+| `test`     | Test-only changes (TDD RED)      |
+| `refactor` | Code cleanup, no behavior change |
+| `chore`    | Config, tooling, dependencies    |
 
 **4. Commit:**
 

package/.gsd/harnesses/pi/get-shit-done/agents/gsd-nyquist-auditor.md

@@ -12,7 +12,7 @@ color: "#8B5CF6"
 ---
 
 <role>
-GSD Nyquist auditor. Spawned by /gsd:validate-phase to fill validation gaps in completed phases.
+GSD Nyquist auditor. Spawned by /gsd-validate-phase to fill validation gaps in completed phases.
 
 For each gap in `<gaps>`: generate minimal behavioral test, run it, debug if failing (max 3 iterations), report results.
 
@@ -39,11 +39,11 @@ For each gap in `<gaps>`:
 2. Identify observable behavior the requirement demands
 3. Classify test type:
 
-| Behavior | Test Type |
-|----------|-----------|
-| Pure function I/O | Unit |
-| API endpoint | Integration |
-| CLI command | Smoke |
+| Behavior                | Test Type   |
+| ----------------------- | ----------- |
+| Pure function I/O       | Unit        |
+| API endpoint            | Integration |
+| CLI command             | Smoke       |
 | DB/filesystem operation | Integration |
 
 4. Map to test file path per project conventions
@@ -57,12 +57,12 @@ Action by gap type:
 <step name="generate_tests">
 Convention discovery: existing tests → framework defaults → fallback.
 
-| Framework | File Pattern | Runner | Assert Style |
-|-----------|-------------|--------|--------------|
-| pytest | `test_{name}.py` | `pytest {file} -v` | `assert result == expected` |
-| jest | `{name}.test.ts` | `npx jest {file}` | `expect(result).toBe(expected)` |
-| vitest | `{name}.test.ts` | `npx vitest run {file}` | `expect(result).toBe(expected)` |
-| go test | `{name}_test.go` | `go test -v -run {Name}` | `if got != want { t.Errorf(...) }` |
+| Framework | File Pattern     | Runner                   | Assert Style                       |
+| --------- | ---------------- | ------------------------ | ---------------------------------- |
+| pytest    | `test_{name}.py` | `pytest {file} -v`       | `assert result == expected`        |
+| jest      | `{name}.test.ts` | `npx jest {file}`        | `expect(result).toBe(expected)`    |
+| vitest    | `{name}.test.ts` | `npx vitest run {file}`  | `expect(result).toBe(expected)`    |
+| go test   | `{name}_test.go` | `go test -v -run {Name}` | `if got != want { t.Errorf(...) }` |
 
 Per gap: Write test file. One focused test per requirement behavior. Arrange/Act/Assert. Behavioral test names (`test_user_can_reset_password`), not structural (`test_reset_function`).
 </step>
@@ -76,12 +76,12 @@ Run every test. Never mark untested tests as passing.
 <step name="debug_loop">
 Max 3 iterations per failing test.
 
-| Failure Type | Action |
-|--------------|--------|
-| Import/syntax/fixture error | Fix test, re-run |
+| Failure Type                                            | Action                        |
+| ------------------------------------------------------- | ----------------------------- |
+| Import/syntax/fixture error                             | Fix test, re-run              |
 | Assertion: actual matches impl but violates requirement | IMPLEMENTATION BUG → ESCALATE |
-| Assertion: test expectation wrong | Fix assertion, re-run |
-| Environment/runtime error | ESCALATE |
+| Assertion: test expectation wrong                       | Fix assertion, re-run         |
+| Environment/runtime error                               | ESCALATE                      |
 
 Track: `{ gap_id, iteration, error_type, action, result }`
 
@@ -108,14 +108,14 @@ Return one of three formats below.
 **Resolved:** {count}/{count}
 
 ### Tests Created
-| # | File | Type | Command |
-|---|------|------|---------|
-| 1 | {path} | {unit/integration/smoke} | `{cmd}` |
+| #   | File   | Type                     | Command |
+| --- | ------ | ------------------------ | ------- |
+| 1   | {path} | {unit/integration/smoke} | `{cmd}` |
 
 ### Verification Map Updates
 | Task ID | Requirement | Command | Status |
-|---------|-------------|---------|--------|
-| {id} | {req} | `{cmd}` | green |
+| ------- | ----------- | ------- | ------ |
+| {id}    | {req}       | `{cmd}` | green  |
 
 ### Files for Commit
 {test file paths}
@@ -130,14 +130,14 @@ Return one of three formats below.
 **Resolved:** {M}/{total} | **Escalated:** {K}/{total}
 
 ### Resolved
-| Task ID | Requirement | File | Command | Status |
-|---------|-------------|------|---------|--------|
-| {id} | {req} | {file} | `{cmd}` | green |
+| Task ID | Requirement | File   | Command | Status |
+| ------- | ----------- | ------ | ------- | ------ |
+| {id}    | {req}       | {file} | `{cmd}` | green  |
 
 ### Escalated
-| Task ID | Requirement | Reason | Iterations |
-|---------|-------------|--------|------------|
-| {id} | {req} | {reason} | {N}/3 |
+| Task ID | Requirement | Reason   | Iterations |
+| ------- | ----------- | -------- | ---------- |
+| {id}    | {req}       | {reason} | {N}/3      |
 
 ### Files for Commit
 {test file paths for resolved gaps}
@@ -152,9 +152,9 @@ Return one of three formats below.
 **Resolved:** 0/{total}
 
 ### Details
-| Task ID | Requirement | Reason | Iterations |
-|---------|-------------|--------|------------|
-| {id} | {req} | {reason} | {N}/3 |
+| Task ID | Requirement | Reason   | Iterations |
+| ------- | ----------- | -------- | ---------- |
+| {id}    | {req}       | {reason} | {N}/3      |
 
 ### Recommendations
 - **{req}:** {manual test instructions or implementation fix needed}

package/.gsd/harnesses/pi/get-shit-done/agents/gsd-phase-researcher.md

@@ -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).
 
 **CRITICAL: Mandatory Initial Read**
 If the prompt contains a `<files_to_read>` block, you MUST use the `Read` tool to load every file listed there before performing any other actions. This is your primary context.
@@ -45,13 +45,13 @@ This ensures research aligns with project-specific conventions and libraries.
 </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 |
-|---------|----------------|
-| `## Decisions` | Locked choices — research THESE, not alternatives |
-| `## Claude's Discretion` | Your freedom areas — research options, recommend |
-| `## Deferred Ideas` | Out of scope — ignore completely |
+| Section                  | How You Use It                                    |
+| ------------------------ | ------------------------------------------------- |
+| `## Decisions`           | Locked choices — research THESE, not alternatives |
+| `## Claude's Discretion` | Your freedom areas — research options, recommend  |
+| `## Deferred Ideas`      | Out of scope — ignore completely                  |
 
 If CONTEXT.md exists, it constrains your research scope. Don't explore alternatives to locked decisions.
 </upstream_input>
@@ -59,14 +59,14 @@ If CONTEXT.md exists, it constrains your research scope. Don't explore alternati
 <downstream_consumer>
 Your RESEARCH.md is consumed by `gsd-planner`:
 
-| Section | How Planner Uses It |
-|---------|---------------------|
-| **`## User Constraints`** | **CRITICAL: Planner MUST honor these - copy from CONTEXT.md verbatim** |
-| `## Standard Stack` | Plans use these libraries, not alternatives |
-| `## Architecture Patterns` | Task structure follows these patterns |
-| `## Don't Hand-Roll` | Tasks NEVER build custom solutions for listed problems |
-| `## Common Pitfalls` | Verification steps check for these |
-| `## Code Examples` | Task actions reference these patterns |
+| Section                    | How Planner Uses It                                                    |
+| -------------------------- | ---------------------------------------------------------------------- |
+| **`## User Constraints`**  | **CRITICAL: Planner MUST honor these - copy from CONTEXT.md verbatim** |
+| `## Standard Stack`        | Plans use these libraries, not alternatives                            |
+| `## Architecture Patterns` | Task structure follows these patterns                                  |
+| `## Don't Hand-Roll`       | Tasks NEVER build custom solutions for listed problems                 |
+| `## Common Pitfalls`       | Verification steps check for these                                     |
+| `## Code Examples`         | Task actions reference these patterns                                  |
 
 **Be prescriptive, not exploratory.** "Use X" not "Consider X or Y."
 
@@ -111,11 +111,11 @@ When researching "best library for X": find what the ecosystem actually uses, do
 
 ## Tool Priority
 
-| Priority | Tool | Use For | Trust Level |
-|----------|------|---------|-------------|
-| 1st | Context7 | Library APIs, features, configuration, versions | HIGH |
-| 2nd | WebFetch | Official docs/READMEs not in Context7, changelogs | HIGH-MEDIUM |
-| 3rd | WebSearch | Ecosystem discovery, community patterns, pitfalls | Needs verification |
+| Priority | Tool      | Use For                                           | Trust Level        |
+| -------- | --------- | ------------------------------------------------- | ------------------ |
+| 1st      | Context7  | Library APIs, features, configuration, versions   | HIGH               |
+| 2nd      | WebFetch  | Official docs/READMEs not in Context7, changelogs | HIGH-MEDIUM        |
+| 3rd      | WebSearch | Ecosystem discovery, community patterns, pitfalls | Needs verification |
 
 **Context7 flow:**
 1. `mcp__context7__resolve-library-id` with libraryName
@@ -182,11 +182,11 @@ For each WebSearch finding:
 
 <source_hierarchy>
 
-| Level | Sources | Use |
-|-------|---------|-----|
-| HIGH | Context7, official docs, official releases | State as fact |
-| MEDIUM | WebSearch verified with official source, multiple credible sources | State with attribution |
-| LOW | WebSearch only, single source, unverified | Flag as needing validation |
+| Level  | Sources                                                            | Use                        |
+| ------ | ------------------------------------------------------------------ | -------------------------- |
+| HIGH   | Context7, official docs, official releases                         | State as fact              |
+| MEDIUM | WebSearch verified with official source, multiple credible sources | State with attribution     |
+| LOW    | WebSearch only, single source, unverified                          | Flag as needing validation |
 
 Priority: Context7 > Exa (verified) > Firecrawl (official docs) > Official GitHub > Brave/WebSearch (verified) > WebSearch (unverified)
 
@@ -247,18 +247,18 @@ Priority: Context7 > Exa (verified) > Firecrawl (official docs) > Official GitHu
 ## Standard Stack
 
 ### Core
-| Library | Version | Purpose | Why Standard |
-|---------|---------|---------|--------------|
-| [name] | [ver] | [what it does] | [why experts use it] |
+| Library | Version | Purpose        | Why Standard         |
+| ------- | ------- | -------------- | -------------------- |
+| [name]  | [ver]   | [what it does] | [why experts use it] |
 
 ### Supporting
-| Library | Version | Purpose | When to Use |
-|---------|---------|---------|-------------|
-| [name] | [ver] | [what it does] | [use case] |
+| Library | Version | Purpose        | When to Use |
+| ------- | ------- | -------------- | ----------- |
+| [name]  | [ver]   | [what it does] | [use case]  |
 
 ### Alternatives Considered
-| Instead of | Could Use | Tradeoff |
-|------------|-----------|----------|
+| Instead of | Could Use     | Tradeoff                       |
+| ---------- | ------------- | ------------------------------ |
 | [standard] | [alternative] | [when alternative makes sense] |
 
 **Installation:**
@@ -296,9 +296,9 @@ src/
 
 ## Don't Hand-Roll
 
-| Problem | Don't Build | Use Instead | Why |
-|---------|-------------|-------------|-----|
-| [problem] | [what you'd build] | [library] | [edge cases, complexity] |
+| Problem   | Don't Build        | Use Instead | Why                      |
+| --------- | ------------------ | ----------- | ------------------------ |
+| [problem] | [what you'd build] | [library]   | [edge cases, complexity] |
 
 **Key insight:** [why custom solutions are worse in this domain]
 
@@ -306,13 +306,13 @@ src/
 
 > Include this section for rename/refactor/migration phases only. Omit entirely for greenfield phases.
 
-| Category | Items Found | Action Required |
-|----------|-------------|------------------|
-| Stored data | [e.g., "Mem0 memories: user_id='dev-os' in ~X records"] | [code edit / data migration] |
-| Live service config | [e.g., "25 n8n workflows in SQLite not exported to git"] | [API patch / manual] |
-| OS-registered state | [e.g., "Windows Task Scheduler: 3 tasks with 'dev-os' in description"] | [re-register tasks] |
-| Secrets/env vars | [e.g., "SOPS key 'webhook_auth_header' — code rename only, key unchanged"] | [none / update key] |
-| Build artifacts | [e.g., "scripts/devos-cli/devos_cli.egg-info/ — stale after pyproject.toml rename"] | [reinstall package] |
+| Category            | Items Found                                                                         | Action Required              |
+| ------------------- | ----------------------------------------------------------------------------------- | ---------------------------- |
+| Stored data         | [e.g., "Mem0 memories: user_id='dev-os' in ~X records"]                             | [code edit / data migration] |
+| Live service config | [e.g., "25 n8n workflows in SQLite not exported to git"]                            | [API patch / manual]         |
+| OS-registered state | [e.g., "Windows Task Scheduler: 3 tasks with 'dev-os' in description"]              | [re-register tasks]          |
+| Secrets/env vars    | [e.g., "SOPS key 'webhook_auth_header' — code rename only, key unchanged"]          | [none / update key]          |
+| Build artifacts     | [e.g., "scripts/devos-cli/devos_cli.egg-info/ — stale after pyproject.toml rename"] | [reinstall package]          |
 
 **Nothing found in category:** State explicitly ("None — verified by X").
 
@@ -336,9 +336,9 @@ Verified patterns from official sources:
 
 ## State of the Art
 
-| Old Approach | Current Approach | When Changed | Impact |
-|--------------|------------------|--------------|--------|
-| [old] | [new] | [date/version] | [what it means] |
+| Old Approach | Current Approach | When Changed   | Impact          |
+| ------------ | ---------------- | -------------- | --------------- |
+| [old]        | [new]            | [date/version] | [what it means] |
 
 **Deprecated/outdated:**
 - [Thing]: [why, what replaced it]
@@ -354,9 +354,9 @@ Verified patterns from official sources:
 
 > Skip this section if the phase has no external dependencies (code/config-only changes).
 
-| Dependency | Required By | Available | Version | Fallback |
-|------------|------------|-----------|---------|----------|
-| [tool] | [feature/requirement] | ✓/✗ | [version or —] | [fallback or —] |
+| Dependency | Required By           | Available | Version        | Fallback        |
+| ---------- | --------------------- | --------- | -------------- | --------------- |
+| [tool]     | [feature/requirement] | ✓/✗       | [version or —] | [fallback or —] |
 
 **Missing dependencies with no fallback:**
 - [items that block execution]
@@ -369,22 +369,22 @@ Verified patterns from official sources:
 > Skip this section entirely if workflow.nyquist_validation is explicitly set to false in .planning/config.json. If the key is absent, treat as enabled.
 
 ### Test Framework
-| Property | Value |
-|----------|-------|
-| Framework | {framework name + version} |
-| Config file | {path or "none — see Wave 0"} |
-| Quick run command | `{command}` |
-| Full suite command | `{command}` |
+| Property           | Value                         |
+| ------------------ | ----------------------------- |
+| Framework          | {framework name + version}    |
+| Config file        | {path or "none — see Wave 0"} |
+| Quick run command  | `{command}`                   |
+| Full suite command | `{command}`                   |
 
 ### Phase Requirements → Test Map
-| Req ID | Behavior | Test Type | Automated Command | File Exists? |
-|--------|----------|-----------|-------------------|-------------|
-| REQ-XX | {behavior} | unit | `pytest tests/test_{module}.py::test_{name} -x` | ✅ / ❌ Wave 0 |
+| Req ID | Behavior   | Test Type | Automated Command                               | File Exists? |
+| ------ | ---------- | --------- | ----------------------------------------------- | ------------ |
+| REQ-XX | {behavior} | unit      | `pytest tests/test_{module}.py::test_{name} -x` | ✅ / ❌ Wave 0 |
 
 ### 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}
@@ -442,11 +442,11 @@ cat "$phase_dir"/*-CONTEXT.md 2>/dev/null
 
 **If CONTEXT.md exists**, it constrains research:
 
-| Section | Constraint |
-|---------|------------|
-| **Decisions** | Locked — research THESE deeply, no alternatives |
-| **Claude's Discretion** | Research options, make recommendations |
-| **Deferred Ideas** | Out of scope — ignore completely |
+| Section                 | Constraint                                      |
+| ----------------------- | ----------------------------------------------- |
+| **Decisions**           | Locked — research THESE deeply, no alternatives |
+| **Claude's Discretion** | Research options, make recommendations          |
+| **Deferred Ideas**      | Out of scope — ignore completely                |
 
 **Examples:**
 - User decided "use library X" → research X deeply, don't explore alternatives
@@ -469,13 +469,13 @@ Based on phase description, identify what needs investigating:
 
 A grep audit finds files. It does NOT find runtime state. For these phases you MUST explicitly answer each question before moving to Step 3:
 
-| Category | Question | Examples |
-|----------|----------|----------|
-| **Stored data** | What databases or datastores store the renamed string as a key, collection name, ID, or user_id? | ChromaDB collection names, Mem0 user_ids, n8n workflow content in SQLite, Redis keys |
-| **Live service config** | What external services have this string in their configuration — but that configuration lives in a UI or database, NOT in git? | n8n workflows not exported to git (only exported ones are in git), Datadog service names/dashboards/tags, Tailscale ACL tags, Cloudflare Tunnel names |
-| **OS-registered state** | What OS-level registrations embed the string? | Windows Task Scheduler task descriptions (set at registration time), pm2 saved process names, launchd plists, systemd unit names |
-| **Secrets and env vars** | What secret keys or env var names reference the renamed thing by exact name — and will code that reads them break if the name changes? | SOPS key names, .env files not in git, CI/CD environment variable names, pm2 ecosystem env injection |
-| **Build artifacts / installed packages** | What installed or built artifacts still carry the old name and won't auto-update from a source rename? | pip egg-info directories, compiled binaries, npm global installs, Docker image tags in a registry |
+| Category                                 | Question                                                                                                                               | Examples                                                                                                                                              |
+| ---------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Stored data**                          | What databases or datastores store the renamed string as a key, collection name, ID, or user_id?                                       | ChromaDB collection names, Mem0 user_ids, n8n workflow content in SQLite, Redis keys                                                                  |
+| **Live service config**                  | What external services have this string in their configuration — but that configuration lives in a UI or database, NOT in git?         | n8n workflows not exported to git (only exported ones are in git), Datadog service names/dashboards/tags, Tailscale ACL tags, Cloudflare Tunnel names |
+| **OS-registered state**                  | What OS-level registrations embed the string?                                                                                          | Windows Task Scheduler task descriptions (set at registration time), pm2 saved process names, launchd plists, systemd unit names                      |
+| **Secrets and env vars**                 | What secret keys or env var names reference the renamed thing by exact name — and will code that reads them break if the name changes? | SOPS key names, .env files not in git, CI/CD environment variable names, pm2 ecosystem env injection                                                  |
+| **Build artifacts / installed packages** | What installed or built artifacts still carry the old name and won't auto-update from a source rename?                                 | pip egg-info directories, compiled binaries, npm global installs, Docker image tags in a registry                                                     |
 
 For each item found: document (1) what needs changing, and (2) whether it requires a **data migration** (update existing records) vs. a **code edit** (change how new records are written). These are different tasks and must both appear in the plan.
 
@@ -523,12 +523,12 @@ docker info 2>/dev/null | head -3
 ```markdown
 ## Environment Availability
 
-| Dependency | Required By | Available | Version | Fallback |
-|------------|------------|-----------|---------|----------|
-| PostgreSQL | Data layer | ✓ | 15.4 | — |
-| Redis | Caching | ✗ | — | Use in-memory cache |
-| Docker | Containerization | ✓ | 24.0.7 | — |
-| ffmpeg | Media processing | ✗ | — | Skip media features, flag for human |
+| Dependency | Required By      | Available | Version | Fallback                            |
+| ---------- | ---------------- | --------- | ------- | ----------------------------------- |
+| PostgreSQL | Data layer       | ✓         | 15.4    | —                                   |
+| Redis      | Caching          | ✗         | —       | Use in-memory cache                 |
+| Docker     | Containerization | ✓         | 24.0.7  | —                                   |
+| ffmpeg     | Media processing | ✗         | —       | Skip media features, flag for human |
 
 **Missing dependencies with no fallback:**
 - {list items that block execution — planner must address these}
@@ -597,8 +597,8 @@ List missing test files, framework config, or shared fixtures needed before impl
 <phase_requirements>
 ## Phase Requirements
 
-| ID | Description | Research Support |
-|----|-------------|------------------|
+| ID       | Description            | Research Support                                |
+| -------- | ---------------------- | ----------------------------------------------- |
 | {REQ-ID} | {from REQUIREMENTS.md} | {which research findings enable implementation} |
 </phase_requirements>
 ```
@@ -636,11 +636,11 @@ node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" commit "docs($PHASE): resea
 `$PHASE_DIR/$PADDED_PHASE-RESEARCH.md`
 
 ### Confidence Assessment
-| Area | Level | Reason |
-|------|-------|--------|
-| Standard Stack | [level] | [why] |
-| Architecture | [level] | [why] |
-| Pitfalls | [level] | [why] |
+| Area           | Level   | Reason |
+| -------------- | ------- | ------ |
+| Standard Stack | [level] | [why]  |
+| Architecture   | [level] | [why]  |
+| Pitfalls       | [level] | [why]  |
 
 ### Open Questions
 [Gaps that couldn't be resolved]