pi-gsd 2.0.21 → 2.0.23

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

@@ -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 `<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.
@@ -41,17 +41,17 @@ 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 |
-|---------|----------------|
-| `## Decisions` | Locked — UI-SPEC must reflect these. Flag if contradicted. |
-| `## Deferred Ideas` | Out of scope — UI-SPEC must NOT include these. |
+| Section             | How You Use It                                             |
+| ------------------- | ---------------------------------------------------------- |
+| `## Decisions`      | Locked — UI-SPEC must reflect these. Flag if contradicted. |
+| `## Deferred Ideas` | Out of scope — UI-SPEC must NOT include these.             |
 
 **RESEARCH.md** (if exists) — Technical findings
 
-| Section | How You Use It |
-|---------|----------------|
+| Section             | How You Use It                           |
+| ------------------- | ---------------------------------------- |
 | `## Standard Stack` | Verify UI-SPEC component library matches |
 </upstream_input>
 
@@ -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
@@ -230,13 +230,13 @@ If APPROVED: update UI-SPEC.md frontmatter `status: approved` and `reviewed_at:
 **Status:** APPROVED
 
 ### Dimension Results
-| Dimension | Verdict | Notes |
-|-----------|---------|-------|
-| 1 Copywriting | {PASS/FLAG} | {brief note} |
-| 2 Visuals | {PASS/FLAG} | {brief note} |
-| 3 Color | {PASS/FLAG} | {brief note} |
-| 4 Typography | {PASS/FLAG} | {brief note} |
-| 5 Spacing | {PASS/FLAG} | {brief note} |
+| Dimension         | Verdict     | Notes        |
+| ----------------- | ----------- | ------------ |
+| 1 Copywriting     | {PASS/FLAG} | {brief note} |
+| 2 Visuals         | {PASS/FLAG} | {brief note} |
+| 3 Color           | {PASS/FLAG} | {brief note} |
+| 4 Typography      | {PASS/FLAG} | {brief note} |
+| 5 Spacing         | {PASS/FLAG} | {brief note} |
 | 6 Registry Safety | {PASS/FLAG} | {brief note} |
 
 ### Recommendations
@@ -257,10 +257,10 @@ UI-SPEC approved. Planner can use as design context.
 **Blocking Issues:** {count}
 
 ### Dimension Results
-| Dimension | Verdict | Notes |
-|-----------|---------|-------|
+| Dimension     | Verdict           | Notes        |
+| ------------- | ----------------- | ------------ |
 | 1 Copywriting | {PASS/FLAG/BLOCK} | {brief note} |
-| ... | ... | ... |
+| ...           | ...               | ...          |
 
 ### Blocking Issues
 {For each BLOCK:}
@@ -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>

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

@@ -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 `<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.
@@ -43,27 +43,27 @@ 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 |
-|---------|----------------|
-| `## Decisions` | Locked choices — use these as design contract defaults |
-| `## Claude's Discretion` | Your freedom areas — research and recommend |
-| `## Deferred Ideas` | Out of scope — ignore completely |
+| Section                  | How You Use It                                         |
+| ------------------------ | ------------------------------------------------------ |
+| `## Decisions`           | Locked choices — use these as design contract defaults |
+| `## 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 |
-|---------|----------------|
-| `## Standard Stack` | Component library, styling approach, icon library |
-| `## Architecture Patterns` | Layout patterns, state management approach |
+| Section                    | How You Use It                                    |
+| -------------------------- | ------------------------------------------------- |
+| `## Standard Stack`        | Component library, styling approach, icon library |
+| `## Architecture Patterns` | Layout patterns, state management approach        |
 
 **REQUIREMENTS.md** — Project requirements
 
-| Section | How You Use It |
-|---------|----------------|
+| Section                  | How You Use It                                       |
+| ------------------------ | ---------------------------------------------------- |
 | Requirement descriptions | Extract any visual/UX requirements already specified |
-| Success criteria | Infer what states and interactions are needed |
+| Success criteria         | Infer what states and interactions are needed        |
 
 If upstream artifacts answer a design contract question, do NOT re-ask it. Pre-populate the contract and confirm.
 </upstream_input>
@@ -71,12 +71,12 @@ If upstream artifacts answer a design contract question, do NOT re-ask it. Pre-p
 <downstream_consumer>
 Your UI-SPEC.md is consumed by:
 
-| Consumer | How They Use It |
-|----------|----------------|
-| `gsd-ui-checker` | Validates against 6 design quality dimensions |
-| `gsd-planner` | Uses design tokens, component inventory, and copywriting in plan tasks |
-| `gsd-executor` | References as visual source of truth during implementation |
-| `gsd-ui-auditor` | Compares implemented UI against the contract retroactively |
+| Consumer         | How They Use It                                                        |
+| ---------------- | ---------------------------------------------------------------------- |
+| `gsd-ui-checker` | Validates against 6 design quality dimensions                          |
+| `gsd-planner`    | Uses design tokens, component inventory, and copywriting in plan tasks |
+| `gsd-executor`   | References as visual source of truth during implementation             |
+| `gsd-ui-auditor` | Compares implemented UI against the contract retroactively             |
 
 **Be prescriptive, not exploratory.** "Use 16px body at 1.5 line-height" not "Consider 14-16px."
 </downstream_consumer>
@@ -85,13 +85,13 @@ Your UI-SPEC.md is consumed by:
 
 ## Tool Priority
 
-| Priority | Tool | Use For | Trust Level |
-|----------|------|---------|-------------|
-| 1st | Codebase Grep/Glob | Existing tokens, components, styles, config files | HIGH |
-| 2nd | Context7 | Component library API docs, shadcn preset format | HIGH |
-| 3rd | Exa (MCP) | Design pattern references, accessibility standards, semantic research | MEDIUM (verify) |
-| 4th | Firecrawl (MCP) | Deep scrape component library docs, design system references | HIGH (content depends on source) |
-| 5th | WebSearch | Fallback keyword search for ecosystem discovery | Needs verification |
+| Priority | Tool               | Use For                                                               | Trust Level                      |
+| -------- | ------------------ | --------------------------------------------------------------------- | -------------------------------- |
+| 1st      | Codebase Grep/Glob | Existing tokens, components, styles, config files                     | HIGH                             |
+| 2nd      | Context7           | Component library API docs, shadcn preset format                      | HIGH                             |
+| 3rd      | Exa (MCP)          | Design pattern references, accessibility standards, semantic research | MEDIUM (verify)                  |
+| 4th      | Firecrawl (MCP)    | Deep scrape component library docs, design system references          | HIGH (content depends on source) |
+| 5th      | WebSearch          | Fallback keyword search for ecosystem discovery                       | Needs verification               |
 
 **Exa/Firecrawl:** Check `exa_search` and `firecrawl` from orchestrator context. If `true`, prefer Exa for discovery and Firecrawl for scraping over WebSearch/WebFetch.
 
@@ -297,12 +297,12 @@ node "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" commit "docs($PHASE): UI de
 `$PHASE_DIR/$PADDED_PHASE-UI-SPEC.md`
 
 ### Pre-Populated From
-| Source | Decisions Used |
-|--------|---------------|
-| CONTEXT.md | {count} |
-| RESEARCH.md | {count} |
-| components.json | {yes/no} |
-| User input | {count} |
+| Source          | Decisions Used |
+| --------------- | -------------- |
+| CONTEXT.md      | {count}        |
+| RESEARCH.md     | {count}        |
+| components.json | {yes/no}       |
+| User input      | {count}        |
 
 ### Ready for Verification
 UI-SPEC complete. Checker can now validate.

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

@@ -170,11 +170,11 @@ For each artifact in result:
 
 **Artifact status mapping:**
 
-| exists | issues empty | Status      |
-| ------ | ------------ | ----------- |
-| true   | true         | ✓ VERIFIED  |
-| true   | false        | ✗ STUB      |
-| false  | -            | ✗ MISSING   |
+| exists | issues empty | Status     |
+| ------ | ------------ | ---------- |
+| true   | true         | ✓ VERIFIED |
+| true   | false        | ✗ STUB     |
+| false  | -            | ✗ MISSING  |
 
 **For wiring verification (Level 3)**, check imports/usage manually for artifacts that pass Levels 1-2:
 
@@ -193,12 +193,12 @@ grep -r "$artifact_name" "${search_path:-src/}" --include="*.ts" --include="*.ts
 
 ### Final Artifact Status
 
-| Exists | Substantive | Wired | Status      |
-| ------ | ----------- | ----- | ----------- |
-| ✓      | ✓           | ✓     | ✓ VERIFIED  |
+| Exists | Substantive | Wired | Status     |
+| ------ | ----------- | ----- | ---------- |
+| ✓      | ✓           | ✓     | ✓ VERIFIED |
 | ✓      | ✓           | ✗     | ⚠️ ORPHANED |
-| ✓      | ✗           | -     | ✗ STUB      |
-| ✗      | -           | -     | ✗ MISSING   |
+| ✓      | ✗           | -     | ✗ STUB     |
+| ✗      | -           | -     | ✗ MISSING  |
 
 ## Step 4b: Data-Flow Trace (Level 4)
 
@@ -240,22 +240,22 @@ grep -r -A 3 "<${COMPONENT_NAME}" "${search_path:-src/}" --include="*.tsx" 2>/de
 
 **Data-flow status:**
 
-| Data Source | Produces Real Data | Status |
-| ---------- | ------------------ | ------ |
-| DB query found | Yes | ✓ FLOWING |
-| Fetch exists, static fallback only | No | ⚠️ STATIC |
-| No data source found | N/A | ✗ DISCONNECTED |
-| Props hardcoded empty at call site | No | ✗ HOLLOW_PROP |
+| Data Source                        | Produces Real Data | Status         |
+| ---------------------------------- | ------------------ | -------------- |
+| DB query found                     | Yes                | ✓ FLOWING      |
+| Fetch exists, static fallback only | No                 | ⚠️ STATIC       |
+| No data source found               | N/A                | ✗ DISCONNECTED |
+| Props hardcoded empty at call site | No                 | ✗ HOLLOW_PROP  |
 
 **Final Artifact Status (updated with Level 4):**
 
-| Exists | Substantive | Wired | Data Flows | Status |
-| ------ | ----------- | ----- | ---------- | ------ |
-| ✓ | ✓ | ✓ | ✓ | ✓ VERIFIED |
-| ✓ | ✓ | ✓ | ✗ | ⚠️ HOLLOW — wired but data disconnected |
-| ✓ | ✓ | ✗ | - | ⚠️ ORPHANED |
-| ✓ | ✗ | - | - | ✗ STUB |
-| ✗ | - | - | - | ✗ MISSING |
+| Exists | Substantive | Wired | Data Flows | Status                                 |
+| ------ | ----------- | ----- | ---------- | -------------------------------------- |
+| ✓      | ✓           | ✓     | ✓          | ✓ VERIFIED                             |
+| ✓      | ✓           | ✓     | ✗          | ⚠️ HOLLOW — wired but data disconnected |
+| ✓      | ✓           | ✗     | -          | ⚠️ ORPHANED                             |
+| ✓      | ✗           | -     | -          | ✗ STUB                                 |
+| ✗      | -           | -     | -          | ✗ MISSING                              |
 
 ## Step 5: Verify Key Links (Wiring)
 
@@ -409,9 +409,9 @@ npm test -- --grep "$PHASE_TEST_PATTERN" 2>&1 | grep -q "passing"
 
 **Spot-check status:**
 
-| Behavior | Command | Result | Status |
-| -------- | ------- | ------ | ------ |
-| {truth} | {command} | {output} | ✓ PASS / ✗ FAIL / ? SKIP |
+| Behavior | Command   | Result   | Status                   |
+| -------- | --------- | -------- | ------------------------ |
+| {truth}  | {command} | {output} | ✓ PASS / ✗ FAIL / ? SKIP |
 
 3. **Classification:**
    - ✓ PASS: Command succeeded and output matches expected
@@ -452,7 +452,7 @@ npm test -- --grep "$PHASE_TEST_PATTERN" 2>&1 | grep -q "passing"
 
 ## Step 10: Structure Gap Output (If Gaps Found)
 
-Structure gaps in YAML frontmatter for `/gsd:plan-phase --gaps`:
+Structure gaps in YAML frontmatter for `/gsd-plan-phase --gaps`:
 
 ```yaml
 gaps:
@@ -554,7 +554,7 @@ human_verification: # Only if status: human_needed
 ### Requirements Coverage
 
 | Requirement | Source Plan | Description | Status | Evidence |
-| ----------- | ---------- | ----------- | ------ | -------- |
+| ----------- | ----------- | ----------- | ------ | -------- |
 
 ### Anti-Patterns Found
 
@@ -597,7 +597,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
@@ -618,7 +618,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).
 

package/.gsd/harnesses/pi/get-shit-done/references/continuation-format.md

@@ -13,7 +13,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 `{command to copy-paste}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -29,7 +29,7 @@ Standard format for presenting next steps after completing a command or workflow
 1. **Always show what it is** - name + description, never just a command path
 2. **Pull context from source** - ROADMAP.md for phases, PLAN.md `<objective>` for plans
 3. **Command in inline code** - backticks, easy to copy-paste, renders as clickable link
-4. **`/clear` explanation** - always include, keeps it concise but explains why
+4. **`/new` explanation** - always include, keeps it concise but explains why
 5. **"Also available" not "Other options"** - sounds more app-like
 6. **Visual separators** - `---` above and below to make it stand out
 
@@ -46,7 +46,7 @@ Standard format for presenting next steps after completing a command or workflow
 
 `/gsd-execute-phase 2`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -71,7 +71,7 @@ Add note that this is the last plan and what comes after:
 
 `/gsd-execute-phase 2`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -93,7 +93,7 @@ Add note that this is the last plan and what comes after:
 
 `/gsd-plan-phase 2`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -122,7 +122,7 @@ Show completion status before next action:
 
 `/gsd-plan-phase 3`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 
@@ -151,7 +151,7 @@ When there's no clear primary action:
 
 **To research unknowns:** `/gsd-research-phase 3`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 ```
@@ -171,7 +171,7 @@ All 4 phases shipped
 
 `/gsd-new-milestone`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ---
 ```
@@ -213,18 +213,18 @@ Extract: `**02-03: Refresh Token Rotation** - Add /api/auth/refresh with sliding
 ```
 ## To Continue
 
-Run `/clear`, then paste:
+Run `/new`, then paste:
 /gsd-execute-phase 2
 ```
 
 User has no idea what 02-03 is about.
 
-### Don't: Missing /clear explanation
+### Don't: Missing /new explanation
 
 ```
 `/gsd-plan-phase 3`
 
-Run /clear first.
+Run /new first.
 ```
 
 Doesn't explain why. User might skip it.

package/.gsd/harnesses/pi/get-shit-done/references/ui-brand.md

@@ -74,7 +74,7 @@ Always at end of major completions.
 
 `{copy-paste command}`
 
-<sub>`/clear` first → fresh context window</sub>
+<sub>`/new` first → fresh context window</sub>
 
 ───────────────────────────────────────────────────────────────
 

package/.gsd/harnesses/pi/get-shit-done/templates/DEBUG.md

@@ -32,7 +32,7 @@ reproduction: [how to trigger]
 started: [when it broke / always broken]
 
 ## Eliminated
-<!-- APPEND only - prevents re-investigating after /clear -->
+<!-- APPEND only - prevents re-investigating after /new -->
 
 - hypothesis: [theory that was wrong]
   evidence: [what disproved it]
@@ -68,7 +68,7 @@ files_changed: []
 **Current Focus:**
 - OVERWRITE entirely on each update
 - Always reflects what the agent is doing RIGHT NOW
-- If the agent reads this after /clear, it knows exactly where to resume
+- If the agent reads this after /new, it knows exactly where to resume
 - Fields: hypothesis, test, expecting, next_action
 
 **Symptoms:**
@@ -81,7 +81,7 @@ files_changed: []
 - APPEND only - never remove entries
 - Prevents re-investigating dead ends after context reset
 - Each entry: hypothesis, evidence that disproved it, timestamp
-- Critical for efficiency across /clear boundaries
+- Critical for efficiency across /new boundaries
 
 **Evidence:**
 - APPEND only - never remove entries
@@ -140,7 +140,7 @@ files_changed: []
 
 <resume_behavior>
 
-When the agent reads this file after /clear:
+When the agent reads this file after /new:
 
 1. Parse frontmatter → know status
 2. Read Current Focus → know exactly what was happening

package/.gsd/harnesses/pi/get-shit-done/templates/UAT.md

@@ -174,7 +174,7 @@ blocked: [N]
 - `/gsd-verify-work {phase}` picks up from first pending/blocked test
 - When all items resolved, status advances to "complete"
 
-**Resume after /clear:**
+**Resume after /new:**
 1. Read frontmatter → know phase and status
 2. Read Current Test → know where we are
 3. Find first [pending] result → continue from there

package/.gsd/harnesses/pi/get-shit-done/workflows/add-backlog.md

@@ -0,0 +1,132 @@
+<gsd-version v="1.12.4" />
+
+<gsd-arguments>
+  <settings>
+    <keep-extra-args />
+  </settings>
+  <arg name="idea" type="string" optional />
+</gsd-arguments>
+
+<gsd-execute>
+  <display msg="Loading backlog context..." />
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="state" />
+      <arg string="json" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <suppress-errors />
+      <out type="string" name="state" />
+    </outs>
+  </shell>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="roadmap" />
+      <arg string="analyze" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <suppress-errors />
+      <out type="string" name="roadmap" />
+    </outs>
+  </shell>
+  <shell command="pi-gsd-tools">
+    <args>
+      <arg string="current-timestamp" />
+      <arg string="--raw" />
+    </args>
+    <outs>
+      <out type="string" name="timestamp" />
+    </outs>
+  </shell>
+</gsd-execute>
+
+## Backlog Context (pre-injected by WXP)
+
+**Idea:** <gsd-paste name="idea" />
+
+**Timestamp:** <gsd-paste name="timestamp" />
+
+**State:**
+<gsd-paste name="state" />
+
+**Roadmap Analysis:**
+<gsd-paste name="roadmap" />
+
+---
+
+<purpose>
+Park an idea as a backlog entry (999.x numbered phase) in ROADMAP.md. Zero friction — one command captures an idea without interrupting current work. The idea sits in the backlog until promoted by `/gsd-review-backlog`.
+</purpose>
+
+<process>
+
+<step name="validate_context">
+<!-- State, roadmap, and idea pre-injected above via WXP -->
+
+Check that `.planning/ROADMAP.md` exists (from `state` JSON field `roadmap_exists`).
+
+**If roadmap missing:**
+```
+Error: No ROADMAP.md found. Run /gsd-new-project or /gsd-new-milestone first.
+```
+Exit.
+
+**If idea is empty (no $ARGUMENTS):**
+Ask the user: "What's the idea? (one sentence description)"
+Use the response as `idea`.
+</step>
+
+<step name="find_next_slot">
+From the roadmap analysis JSON, extract the `phases` array. Find all phases where `phase_number` starts with `999` (e.g., `999.1`, `999.2`).
+
+Compute next backlog number:
+- If no 999.x entries exist → use `999.1`
+- Otherwise → use `999.(max_decimal + 1)`, e.g., if `999.3` exists → `999.4`
+
+Set `BACKLOG_NUM` = next available 999.x slot.
+</step>
+
+<step name="add_entry">
+Append to `.planning/ROADMAP.md` under a `## Backlog` section (create the section if missing):
+
+```markdown
+- [ ] **Phase {BACKLOG_NUM}**: {idea}
+```
+
+Use the roadmap `roadmap add-phase` command if available, or append directly:
+
+```bash
+pi-gsd-tools roadmap add-phase "{BACKLOG_NUM}" "{idea}" --raw
+```
+
+If the CLI command fails or is unavailable, append manually to ROADMAP.md.
+</step>
+
+<step name="commit">
+```bash
+pi-gsd-tools commit "docs: add backlog entry {BACKLOG_NUM} - {idea_slug}" --files .planning/ROADMAP.md
+```
+</step>
+
+<step name="confirm">
+```
+✓ Backlog entry added
+
+  Phase {BACKLOG_NUM}: {idea}
+
+---
+
+Review and promote backlog: /gsd-review-backlog
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] ROADMAP.md has new 999.x entry
+- [ ] 999.x number is sequential (no gaps or duplicates)
+- [ ] Entry committed to git
+- [ ] User sees confirmation with the assigned phase number
+</success_criteria>