@bhargavvc/sdd-cc 1.30.1 → 1.35.0

package/sdd/workflows/profile-user.md

@@ -30,6 +30,8 @@ PROFILE_PATH="$HOME/.claude/sdd/USER-PROFILE.md"
 
 **If profile exists AND --refresh NOT set AND --questionnaire NOT set:**
 
+
+**Text mode (`workflow.text_mode: true` in config or `--text` flag):** Set `TEXT_MODE=true` if `--text` is present in `$ARGUMENTS` OR `text_mode` from init JSON is `true`. When TEXT_MODE is active, replace every `AskUserQuestion` call with a plain-text numbered list and ask the user to type their choice number. This is required for non-Claude runtimes (OpenAI Codex, Gemini CLI, etc.) where `AskUserQuestion` is not available.
 Use AskUserQuestion:
 - header: "Existing Profile"
 - question: "You already have a profile. What would you like to do?"
@@ -46,7 +48,7 @@ If "Cancel": Display "No changes made." and exit.
 
 Backup existing profile:
 ```bash
-cp "$HOME/.claude/sdd/USER-PROFILE.md" "$HOME/.claude/sdd/USER-PROFILE.backup.md"
+cp "$HOME/.claude/sdd/USER-PROFILE.md" "$HOME/.claude/USER-PROFILE.backup.md"
 ```
 
 Display: "Re-analyzing your sessions to update your profile."
@@ -118,7 +120,7 @@ Use AskUserQuestion:
 - options:
   - "Let's go" -- Proceed to step 3 (session analysis)
   - "Use questionnaire instead" -- Jump to step 4b (questionnaire path)
-  - "Not now" -- Display "No worries. Run /sdd:profile-user when ready." and exit
+  - "Not now" -- Display "No worries. Run /sdd-profile-user when ready." and exit
 
 ---
 
@@ -333,7 +335,7 @@ Use AskUserQuestion with multiSelect:
 - header: "Artifacts"
 - question: "Which artifacts should I generate?"
 - options (ALL pre-selected by default):
-  - "/sdd:dev-preferences command file" -- "Load your preferences in any session"
+  - "/sdd-dev-preferences command file" -- "Load your preferences in any session"
   - "CLAUDE.md profile section" -- "Add profile to this project's CLAUDE.md"
   - "Global CLAUDE.md" -- "Add profile to $HOME/.claude/CLAUDE.md for all projects"
 
@@ -345,13 +347,13 @@ Use AskUserQuestion with multiSelect:
 
 Generate selected artifacts sequentially (file I/O is fast, no benefit from parallel agents):
 
-**For /sdd:dev-preferences (if selected):**
+**For /sdd-dev-preferences (if selected):**
 
 ```bash
 node $HOME/.claude/sdd/bin/sdd-tools.cjs generate-dev-preferences --analysis "$ANALYSIS_PATH" --json 2>/dev/null
 ```
 
-Display: "✓ Generated /sdd:dev-preferences at $HOME/.claude/commands/sdd/dev-preferences.md"
+Display: "✓ Generated /sdd-dev-preferences at $HOME/.claude/commands/sdd/dev-preferences.md"
 
 **For CLAUDE.md profile section (if selected):**
 
@@ -381,7 +383,7 @@ Read both old backup and new analysis to compare dimension ratings/confidence.
 
 Read the backed-up profile:
 ```bash
-BACKUP_PATH="$HOME/.claude/sdd/USER-PROFILE.backup.md"
+BACKUP_PATH="$HOME/.claude/USER-PROFILE.backup.md"
 ```
 
 Compare each dimension's rating and confidence between old and new. Display diff table showing only changed dimensions:
@@ -410,7 +412,7 @@ Your profile:    $HOME/.claude/sdd/USER-PROFILE.md
 Then list paths for each generated artifact:
 ```
 Artifacts:
-  ✓ /sdd:dev-preferences   $HOME/.claude/commands/sdd/dev-preferences.md
+  ✓ /sdd-dev-preferences   $HOME/.claude/commands/sdd/dev-preferences.md
   ✓ CLAUDE.md section       ./CLAUDE.md
   ✓ Global CLAUDE.md        $HOME/.claude/CLAUDE.md
 ```

package/sdd/workflows/progress.md

@@ -27,18 +27,18 @@ If `project_exists` is false (no `.planning/` directory):
 ```
 No planning structure found.
 
-Run /sdd:new-project to start a new project.
+Run /sdd-new-project to start a new project.
 ```
 
 Exit.
 
-If missing STATE.md: suggest `/sdd:new-project`.
+If missing STATE.md: suggest `/sdd-new-project`.
 
 **If ROADMAP.md missing but PROJECT.md exists:**
 
 This means a milestone was completed and archived. Go to **Route F** (between milestones).
 
-If missing both ROADMAP.md and PROJECT.md: suggest `/sdd:new-project`.
+If missing both ROADMAP.md and PROJECT.md: suggest `/sdd-new-project`.
 </step>
 
 <step name="load">
@@ -123,10 +123,10 @@ CONTEXT: [✓ if has_context | - if not]
 - [e.g. jq -r '.blockers[].text' from state-snapshot]
 
 ## Pending Todos
-- [count] pending — /sdd:check-todos to review
+- [count] pending — /sdd-check-todos to review
 
 ## Active Debug Sessions
-- [count] active — /sdd:debug to continue
+- [count] active — /sdd-debug to continue
 (Only show this section if count > 0)
 
 ## What's Next
@@ -185,8 +185,8 @@ Track: `outstanding_debt` — `summary.total_items` from the audit.
 | {phase} | {filename} | {pending_count} pending, {skipped_count} skipped, {blocked_count} blocked |
 | {phase} | {filename} | human_needed — {count} items |
 
-Review: `/sdd:audit-uat ${SDD_WS}` — full cross-phase audit
-Resume testing: `/sdd:verify-work {phase} ${SDD_WS}` — retest specific phase
+Review: `/sdd-audit-uat ${SDD_WS}` — full cross-phase audit
+Resume testing: `/sdd-verify-work {phase} ${SDD_WS}` — retest specific phase
 ```
 
 This is a WARNING, not a blocker — routing proceeds normally. The debt is visible so the user can make an informed choice.
@@ -215,9 +215,9 @@ Read its `<objective>` section.
 
 **{phase}-{plan}: [Plan Name]** — [objective summary from PLAN.md]
 
-`/sdd:execute-phase {phase} ${SDD_WS}`
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-execute-phase {phase} ${SDD_WS}`
 
 ---
 ```
@@ -245,9 +245,9 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 <sub>✓ Context gathered, ready to plan</sub>
 
-`/sdd:plan-phase {phase-number} ${SDD_WS}`
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-plan-phase {phase-number} ${SDD_WS}`
 
 ---
 ```
@@ -261,16 +261,16 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 
-`/sdd:discuss-phase {phase}` — gather context and clarify approach
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-discuss-phase {phase}` — gather context and clarify approach
 
 ---
 
 **Also available:**
-- `/sdd:ui-phase {phase}` — generate UI design contract (recommended for frontend phases)
-- `/sdd:plan-phase {phase}` — skip discussion, plan directly
-- `/sdd:list-phase-assumptions {phase}` — see Claude's assumptions
+- `/sdd-ui-phase {phase}` — generate UI design contract (recommended for frontend phases)
+- `/sdd-plan-phase {phase}` — skip discussion, plan directly
+- `/sdd-list-phase-assumptions {phase}` — see Claude's assumptions
 
 ---
 ```
@@ -284,15 +284,15 @@ PHASE_HAS_UI=$(echo "$PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true" ||
 
 **Phase {N}: {Name}** — {Goal from ROADMAP.md}
 
-`/sdd:discuss-phase {phase} ${SDD_WS}` — gather context and clarify approach
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-discuss-phase {phase} ${SDD_WS}` — gather context and clarify approach
 
 ---
 
 **Also available:**
-- `/sdd:plan-phase {phase} ${SDD_WS}` — skip discussion, plan directly
-- `/sdd:list-phase-assumptions {phase} ${SDD_WS}` — see Claude's assumptions
+- `/sdd-plan-phase {phase} ${SDD_WS}` — skip discussion, plan directly
+- `/sdd-list-phase-assumptions {phase} ${SDD_WS}` — see Claude's assumptions
 
 ---
 ```
@@ -310,15 +310,15 @@ UAT.md exists with gaps (diagnosed issues). User needs to plan fixes.
 
 **{phase_num}-UAT.md** has {N} gaps requiring fixes.
 
-`/sdd:plan-phase {phase} --gaps ${SDD_WS}`
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-plan-phase {phase} --gaps ${SDD_WS}`
 
 ---
 
 **Also available:**
-- `/sdd:execute-phase {phase} ${SDD_WS}` — execute phase plans
-- `/sdd:verify-work {phase} ${SDD_WS}` — run more UAT testing
+- `/sdd-execute-phase {phase} ${SDD_WS}` — execute phase plans
+- `/sdd-verify-work {phase} ${SDD_WS}` — run more UAT testing
 
 ---
 ```
@@ -336,15 +336,15 @@ UAT.md exists with `status: partial` — testing session ended before all items
 
 **{phase_num}-UAT.md** has {N} unresolved tests (pending, blocked, or skipped).
 
-`/sdd:verify-work {phase} ${SDD_WS}` — resume testing from where you left off
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-verify-work {phase} ${SDD_WS}` — resume testing from where you left off
 
 ---
 
 **Also available:**
-- `/sdd:audit-uat ${SDD_WS}` — full cross-phase UAT audit
-- `/sdd:execute-phase {phase} ${SDD_WS}` — execute phase plans
+- `/sdd-audit-uat ${SDD_WS}` — full cross-phase UAT audit
+- `/sdd-execute-phase {phase} ${SDD_WS}` — execute phase plans
 
 ---
 ```
@@ -392,16 +392,16 @@ NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true
 
 **Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
 
-`/sdd:discuss-phase {Z+1}` — gather context and clarify approach
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-discuss-phase {Z+1}` — gather context and clarify approach
 
 ---
 
 **Also available:**
-- `/sdd:ui-phase {Z+1}` — generate UI design contract (recommended for frontend phases)
-- `/sdd:plan-phase {Z+1}` — skip discussion, plan directly
-- `/sdd:verify-work {Z}` — user acceptance test before continuing
+- `/sdd-ui-phase {Z+1}` — generate UI design contract (recommended for frontend phases)
+- `/sdd-plan-phase {Z+1}` — skip discussion, plan directly
+- `/sdd-verify-work {Z}` — user acceptance test before continuing
 
 ---
 ```
@@ -417,15 +417,15 @@ NEXT_HAS_UI=$(echo "$NEXT_PHASE_SECTION" | grep -qi "UI hint.*yes" && echo "true
 
 **Phase {Z+1}: {Name}** — {Goal from ROADMAP.md}
 
-`/sdd:discuss-phase {Z+1} ${SDD_WS}` — gather context and clarify approach
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-discuss-phase {Z+1} ${SDD_WS}` — gather context and clarify approach
 
 ---
 
 **Also available:**
-- `/sdd:plan-phase {Z+1} ${SDD_WS}` — skip discussion, plan directly
-- `/sdd:verify-work {Z} ${SDD_WS}` — user acceptance test before continuing
+- `/sdd-plan-phase {Z+1} ${SDD_WS}` — skip discussion, plan directly
+- `/sdd-verify-work {Z} ${SDD_WS}` — user acceptance test before continuing
 
 ---
 ```
@@ -445,14 +445,14 @@ All {N} phases finished!
 
 **Complete Milestone** — archive and prepare for next
 
-`/sdd:complete-milestone ${SDD_WS}`
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-complete-milestone ${SDD_WS}`
 
 ---
 
 **Also available:**
-- `/sdd:verify-work ${SDD_WS}` — user acceptance test before completing milestone
+- `/sdd-verify-work ${SDD_WS}` — user acceptance test before completing milestone
 
 ---
 ```
@@ -476,9 +476,9 @@ Ready to plan the next milestone.
 
 **Start Next Milestone** — questioning → research → requirements → roadmap
 
-`/sdd:new-milestone ${SDD_WS}`
+`/clear` then:
 
-<sub>`/clear` first → fresh context window</sub>
+`/sdd-new-milestone ${SDD_WS}`
 
 ---
 ```
@@ -488,10 +488,10 @@ Ready to plan the next milestone.
 <step name="edge_cases">
 **Handle edge cases:**
 
-- Phase complete but next phase not planned → offer `/sdd:plan-phase [next] ${SDD_WS}`
+- Phase complete but next phase not planned → offer `/sdd-plan-phase [next] ${SDD_WS}`
 - All work complete → offer milestone completion
 - Blockers present → highlight before offering to continue
-- Handoff file exists → mention it, offer `/sdd:resume-work ${SDD_WS}`
+- Handoff file exists → mention it, offer `/sdd-resume-work ${SDD_WS}`
   </step>
 
 </process>
@@ -501,7 +501,7 @@ Ready to plan the next milestone.
 - [ ] Rich context provided (recent work, decisions, issues)
 - [ ] Current position clear with visual progress
 - [ ] What's next clearly explained
-- [ ] Smart routing: /sdd:execute-phase if plans exist, /sdd:plan-phase if not
+- [ ] Smart routing: /sdd-execute-phase if plans exist, /sdd-plan-phase if not
 - [ ] User confirms before any action
 - [ ] Seamless handoff to appropriate sdd command
       </success_criteria>