@bhargavvc/sdd-cc 1.35.0 → 1.42.4

package/commands/sdd/list-workspaces.md

@@ -1,19 +0,0 @@
----
-name: sdd:list-workspaces
-description: List active SDD workspaces and their status
-allowed-tools:
-  - Bash
-  - Read
----
-<objective>
-Scan `~/sdd-workspaces/` for workspace directories containing `WORKSPACE.md` manifests. Display a summary table with name, path, repo count, strategy, and SDD project status.
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/list-workspaces.md
-@~/.claude/sdd/references/ui-brand.md
-</execution_context>
-
-<process>
-Execute the list-workspaces workflow from @~/.claude/sdd/workflows/list-workspaces.md end-to-end.
-</process>

package/commands/sdd/new-workspace.md

@@ -1,44 +0,0 @@
----
-name: sdd:new-workspace
-description: Create an isolated workspace with repo copies and independent .planning/
-argument-hint: "--name <name> [--repos repo1,repo2] [--path /target] [--strategy worktree|clone] [--branch name] [--auto]"
-allowed-tools:
-  - Read
-  - Bash
-  - Write
-  - AskUserQuestion
----
-<context>
-**Flags:**
-- `--name` (required) — Workspace name
-- `--repos` — Comma-separated repo paths or names. If omitted, interactive selection from child git repos in cwd
-- `--path` — Target directory. Defaults to `~/sdd-workspaces/<name>`
-- `--strategy` — `worktree` (default, lightweight) or `clone` (fully independent)
-- `--branch` — Branch to checkout. Defaults to `workspace/<name>`
-- `--auto` — Skip interactive questions, use defaults
-</context>
-
-<objective>
-Create a physical workspace directory containing copies of specified git repos (as worktrees or clones) with an independent `.planning/` directory for isolated SDD sessions.
-
-**Use cases:**
-- Multi-repo orchestration: work on a subset of repos in parallel with isolated SDD state
-- Feature branch isolation: create a worktree of the current repo with its own `.planning/`
-
-**Creates:**
-- `<path>/WORKSPACE.md` — workspace manifest
-- `<path>/.planning/` — independent planning directory
-- `<path>/<repo>/` — git worktree or clone for each specified repo
-
-**After this command:** `cd` into the workspace and run `/sdd-new-project` to initialize SDD.
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/new-workspace.md
-@~/.claude/sdd/references/ui-brand.md
-</execution_context>
-
-<process>
-Execute the new-workspace workflow from @~/.claude/sdd/workflows/new-workspace.md end-to-end.
-Preserve all workflow gates (validation, approvals, commits, routing).
-</process>

package/commands/sdd/next.md

@@ -1,26 +0,0 @@
----
-name: sdd:next
-description: Automatically advance to the next logical step in the SDD workflow
-allowed-tools:
-  - Read
-  - Bash
-  - Grep
-  - Glob
-  - SlashCommand
----
-<objective>
-Detect the current project state and automatically invoke the next logical SDD workflow step.
-No arguments needed — reads STATE.md, ROADMAP.md, and phase directories to determine what comes next.
-
-Designed for rapid multi-project workflows where remembering which phase/step you're on is overhead.
-
-Supports `--force` flag to bypass safety gates (checkpoint, error state, verification failures).
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/next.md
-</execution_context>
-
-<process>
-Execute the next workflow from @~/.claude/sdd/workflows/next.md end-to-end.
-</process>

package/commands/sdd/note.md

@@ -1,34 +0,0 @@
----
-name: sdd:note
-description: Zero-friction idea capture. Append, list, or promote notes to todos.
-argument-hint: "<text> | list | promote <N> [--global]"
-allowed-tools:
-  - Read
-  - Write
-  - Glob
-  - Grep
----
-<objective>
-Zero-friction idea capture — one Write call, one confirmation line.
-
-Three subcommands:
-- **append** (default): Save a timestamped note file. No questions, no formatting.
-- **list**: Show all notes from project and global scopes.
-- **promote**: Convert a note into a structured todo.
-
-Runs inline — no Task, no AskUserQuestion, no Bash.
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/note.md
-@~/.claude/sdd/references/ui-brand.md
-</execution_context>
-
-<context>
-$ARGUMENTS
-</context>
-
-<process>
-Execute the note workflow from @~/.claude/sdd/workflows/note.md end-to-end.
-Capture the note, list notes, or promote to todo — depending on arguments.
-</process>

package/commands/sdd/plan-milestone-gaps.md

@@ -1,34 +0,0 @@
----
-name: sdd:plan-milestone-gaps
-description: Create phases to close all gaps identified by milestone audit
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
----
-<objective>
-Create all phases necessary to close gaps identified by `/sdd-audit-milestone`.
-
-Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase.
-
-One command creates all fix phases — no manual `/sdd-add-phase` per gap.
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/plan-milestone-gaps.md
-</execution_context>
-
-<context>
-**Audit results:**
-Glob: .planning/v*-MILESTONE-AUDIT.md (use most recent)
-
-Original intent and current planning state are loaded on demand inside the workflow.
-</context>
-
-<process>
-Execute the plan-milestone-gaps workflow from @~/.claude/sdd/workflows/plan-milestone-gaps.md end-to-end.
-Preserve all workflow gates (audit loading, prioritization, phase grouping, user confirmation, roadmap updates).
-</process>

package/commands/sdd/plant-seed.md

@@ -1,28 +0,0 @@
----
-name: sdd:plant-seed
-description: Capture a forward-looking idea with trigger conditions — surfaces automatically at the right milestone
-argument-hint: "[idea summary]"
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - AskUserQuestion
----
-
-<objective>
-Capture an idea that's too big for now but should surface automatically when the right
-milestone arrives. Seeds solve context rot: instead of a one-liner in Deferred that nobody
-reads, a seed preserves the full WHY, WHEN to surface, and breadcrumbs to details.
-
-Creates: .planning/seeds/SEED-NNN-slug.md
-Consumed by: /sdd-new-milestone (scans seeds and presents matches)
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/plant-seed.md
-</execution_context>
-
-<process>
-Execute the plant-seed workflow from @~/.claude/sdd/workflows/plant-seed.md end-to-end.
-</process>

package/commands/sdd/remove-phase.md

@@ -1,31 +0,0 @@
----
-name: sdd:remove-phase
-description: Remove a future phase from roadmap and renumber subsequent phases
-argument-hint: <phase-number>
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
----
-<objective>
-Remove an unstarted future phase from the roadmap and renumber all subsequent phases to maintain a clean, linear sequence.
-
-Purpose: Clean removal of work you've decided not to do, without polluting context with cancelled/deferred markers.
-Output: Phase deleted, all subsequent phases renumbered, git commit as historical record.
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/remove-phase.md
-</execution_context>
-
-<context>
-Phase: $ARGUMENTS
-
-Roadmap and state are resolved in-workflow via `init phase-op` and targeted reads.
-</context>
-
-<process>
-Execute the remove-phase workflow from @~/.claude/sdd/workflows/remove-phase.md end-to-end.
-Preserve all validation gates (future phase check, work check), renumbering logic, and commit.
-</process>

package/commands/sdd/remove-workspace.md

@@ -1,26 +0,0 @@
----
-name: sdd:remove-workspace
-description: Remove a SDD workspace and clean up worktrees
-argument-hint: "<workspace-name>"
-allowed-tools:
-  - Bash
-  - Read
-  - AskUserQuestion
----
-<context>
-**Arguments:**
-- `<workspace-name>` (required) — Name of the workspace to remove
-</context>
-
-<objective>
-Remove a workspace directory after confirmation. For worktree strategy, runs `git worktree remove` for each member repo first. Refuses if any repo has uncommitted changes.
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/remove-workspace.md
-@~/.claude/sdd/references/ui-brand.md
-</execution_context>
-
-<process>
-Execute the remove-workspace workflow from @~/.claude/sdd/workflows/remove-workspace.md end-to-end.
-</process>

package/commands/sdd/research-phase.md

@@ -1,195 +0,0 @@
----
-name: sdd:research-phase
-description: Research how to implement a phase (standalone - usually use /sdd-plan-phase instead)
-argument-hint: "[phase]"
-allowed-tools:
-  - Read
-  - Bash
-  - Task
----
-
-<objective>
-Research how to implement a phase. Spawns sdd-phase-researcher agent with phase context.
-
-**Note:** This is a standalone research command. For most workflows, use `/sdd-plan-phase` which integrates research automatically.
-
-**Use this command when:**
-- You want to research without planning yet
-- You want to re-research after planning is complete
-- You need to investigate before deciding if a phase is feasible
-
-**Orchestrator role:** Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.
-
-**Why subagent:** Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
-</objective>
-
-<available_agent_types>
-Valid SDD subagent types (use exact names — do not fall back to 'general-purpose'):
-- sdd-phase-researcher — Researches technical approaches for a phase
-</available_agent_types>
-
-<context>
-Phase number: $ARGUMENTS (required)
-
-Normalize phase input in step 1 before any directory lookups.
-</context>
-
-<process>
-
-## 0. Initialize Context
-
-```bash
-INIT=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" init phase-op "$ARGUMENTS")
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-```
-
-Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `phase_found`, `commit_docs`, `has_research`, `state_path`, `requirements_path`, `context_path`, `research_path`.
-
-Resolve researcher model:
-```bash
-RESEARCHER_MODEL=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" resolve-model sdd-phase-researcher --raw)
-```
-
-## 1. Validate Phase
-
-```bash
-PHASE_INFO=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" roadmap get-phase "${phase_number}")
-```
-
-**If `found` is false:** Error and exit. **If `found` is true:** Extract `phase_number`, `phase_name`, `goal` from JSON.
-
-## 2. Check Existing Research
-
-```bash
-ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
-```
-
-**If exists:** Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.
-
-**If doesn't exist:** Continue.
-
-## 3. Gather Phase Context
-
-Use paths from INIT (do not inline file contents in orchestrator context):
-- `requirements_path`
-- `context_path`
-- `state_path`
-
-Present summary with phase description and what files the researcher will load.
-
-## 4. Spawn sdd-phase-researcher Agent
-
-Research modes: ecosystem (default), feasibility, implementation, comparison.
-
-```markdown
-<research_type>
-Phase Research — investigating HOW to implement a specific phase well.
-</research_type>
-
-<key_insight>
-The question is NOT "which library should I use?"
-
-The question is: "What do I not know that I don't know?"
-
-For this phase, discover:
-- What's the established architecture pattern?
-- What libraries form the standard stack?
-- What problems do people commonly hit?
-- What's SOTA vs what Claude's training thinks is SOTA?
-- What should NOT be hand-rolled?
-</key_insight>
-
-<objective>
-Research implementation approach for Phase {phase_number}: {phase_name}
-Mode: ecosystem
-</objective>
-
-<files_to_read>
-- {requirements_path} (Requirements)
-- {context_path} (Phase context from discuss-phase, if exists)
-- {state_path} (Prior project decisions and blockers)
-</files_to_read>
-
-<additional_context>
-**Phase description:** {phase_description}
-</additional_context>
-
-<downstream_consumer>
-Your RESEARCH.md will be loaded by `/sdd-plan-phase` which uses specific sections:
-- `## Standard Stack` → Plans use these libraries
-- `## Architecture Patterns` → Task structure follows these
-- `## 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."
-</downstream_consumer>
-
-<quality_gate>
-Before declaring complete, verify:
-- [ ] All domains investigated (not just some)
-- [ ] Negative claims verified with official docs
-- [ ] Multiple sources for critical claims
-- [ ] Confidence levels assigned honestly
-- [ ] Section names match what plan-phase expects
-</quality_gate>
-
-<output>
-Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
-</output>
-```
-
-```
-Task(
-  prompt=filled_prompt,
-  subagent_type="sdd-phase-researcher",
-  model="{researcher_model}",
-  description="Research Phase {phase}"
-)
-```
-
-## 5. Handle Agent Return
-
-**`## RESEARCH COMPLETE`:** Display summary, offer: Plan phase, Dig deeper, Review full, Done.
-
-**`## CHECKPOINT REACHED`:** Present to user, get response, spawn continuation.
-
-**`## RESEARCH INCONCLUSIVE`:** Show what was attempted, offer: Add context, Try different mode, Manual.
-
-## 6. Spawn Continuation Agent
-
-```markdown
-<objective>
-Continue research for Phase {phase_number}: {phase_name}
-</objective>
-
-<prior_state>
-<files_to_read>
-- .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md (Existing research)
-</files_to_read>
-</prior_state>
-
-<checkpoint_response>
-**Type:** {checkpoint_type}
-**Response:** {user_response}
-</checkpoint_response>
-```
-
-```
-Task(
-  prompt=continuation_prompt,
-  subagent_type="sdd-phase-researcher",
-  model="{researcher_model}",
-  description="Continue research Phase {phase}"
-)
-```
-
-</process>
-
-<success_criteria>
-- [ ] Phase validated against roadmap
-- [ ] Existing research checked
-- [ ] sdd-phase-researcher spawned with context
-- [ ] Checkpoints handled correctly
-- [ ] User knows next steps
-</success_criteria>

package/commands/sdd/scan.md

@@ -1,26 +0,0 @@
----
-name: sdd:scan
-description: Rapid codebase assessment — lightweight alternative to /sdd-map-codebase
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Grep
-  - Glob
-  - Agent
-  - AskUserQuestion
----
-<objective>
-Run a focused codebase scan for a single area, producing targeted documents in `.planning/codebase/`.
-Accepts an optional `--focus` flag: `tech`, `arch`, `quality`, `concerns`, or `tech+arch` (default).
-
-Lightweight alternative to `/sdd-map-codebase` — spawns one mapper agent instead of four parallel ones.
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/scan.md
-</execution_context>
-
-<process>
-Execute the scan workflow from @~/.claude/sdd/workflows/scan.md end-to-end.
-</process>

package/commands/sdd/session-report.md

@@ -1,19 +0,0 @@
----
-name: sdd:session-report
-description: Generate a session report with token usage estimates, work summary, and outcomes
-allowed-tools:
-  - Read
-  - Bash
-  - Write
----
-<objective>
-Generate a structured SESSION_REPORT.md document capturing session outcomes, work performed, and estimated resource usage. Provides a shareable artifact for post-session review.
-</objective>
-
-<execution_context>
-@~/.claude/sdd/workflows/session-report.md
-</execution_context>
-
-<process>
-Execute the session-report workflow from @~/.claude/sdd/workflows/session-report.md end-to-end.
-</process>

package/commands/sdd/set-profile.md

@@ -1,12 +0,0 @@
----
-name: sdd:set-profile
-description: Switch model profile for SDD agents (quality/balanced/budget/inherit)
-argument-hint: <profile (quality|balanced|budget|inherit)>
-model: haiku
-allowed-tools:
-  - Bash
----
-
-Show the following output to the user verbatim, with no extra commentary:
-
-!`node "$HOME/.claude/sdd/bin/sdd-tools.cjs" config-set-model-profile $ARGUMENTS --raw`

package/scripts/sync-upstream.sh

@@ -1,56 +0,0 @@
-#!/usr/bin/env bash
-##############################################################################
-# sync-upstream.sh
-#
-# Syncs the sdd-cc fork with upstream gsd-build/sdd,
-# then runs the rebrand script.
-#
-# USAGE:  bash scripts/sync-upstream.sh
-##############################################################################
-
-set -euo pipefail
-
-REPO_ROOT="$(cd "$(dirname "$0")/.." && pwd)"
-cd "$REPO_ROOT"
-
-echo "=== SDD-CC Upstream Sync ==="
-echo ""
-
-# Step 1: Fetch upstream
-echo "[1/5] Fetching upstream..."
-git fetch upstream
-echo "  Done."
-
-# Step 2: Update upstream-sync branch
-echo ""
-echo "[2/5] Updating upstream-sync branch..."
-git checkout upstream-sync
-git merge upstream/main --no-edit
-echo "  Done."
-
-# Step 3: Merge into main
-echo ""
-echo "[3/5] Merging upstream-sync into main..."
-git checkout main
-git merge -X theirs upstream-sync --no-edit
-echo "  Done."
-
-# Step 4: Run rebrand
-echo ""
-echo "[4/5] Running rebrand..."
-bash scripts/rebrand-gsd-to-sdd.sh
-echo "  Done."
-
-# Step 5: Summary
-echo ""
-echo "[5/5] Summary"
-echo ""
-echo "  Upstream version: $(git log upstream/main --oneline -1)"
-echo "  Local version:    $(cat package.json | grep '"version"' | head -1)"
-echo ""
-echo "  Next steps:"
-echo "  1. Review:   git diff --stat"
-echo "  2. Test:     node bin/install.js --cursor --local"
-echo "  3. Commit:   git add -A && git commit -m 'sync: upstream vX.Y.Z + rebrand'"
-echo "  4. Push:     git push origin main upstream-sync"
-echo "  5. Publish:  npm publish --access public"

package/sdd/workflows/research-phase.md

@@ -1,82 +0,0 @@
-<purpose>
-Research how to implement a phase. Spawns sdd-phase-researcher with phase context.
-
-Standalone research command. For most workflows, use `/sdd-plan-phase` which integrates research automatically.
-</purpose>
-
-<available_agent_types>
-Valid SDD subagent types (use exact names — do not fall back to 'general-purpose'):
-- sdd-phase-researcher — Researches technical approaches for a phase
-</available_agent_types>
-
-<process>
-
-## Step 0: Resolve Model Profile
-
-@~/.claude/sdd/references/model-profile-resolution.md
-
-Resolve model for:
-- `sdd-phase-researcher`
-
-## Step 1: Normalize and Validate Phase
-
-@~/.claude/sdd/references/phase-argument-parsing.md
-
-```bash
-PHASE_INFO=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" roadmap get-phase "${PHASE}")
-```
-
-If `found` is false: Error and exit.
-
-## Step 2: Check Existing Research
-
-```bash
-ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null || true
-```
-
-If exists: Offer update/view/skip options.
-
-## Step 3: Gather Phase Context
-
-```bash
-INIT=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" init phase-op "${PHASE}")
-if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
-# Extract: phase_dir, padded_phase, phase_number, state_path, requirements_path, context_path
-AGENT_SKILLS_RESEARCHER=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" agent-skills sdd-researcher 2>/dev/null)
-```
-
-## Step 4: Spawn Researcher
-
-```
-Task(
-  prompt="<objective>
-Research implementation approach for Phase {phase}: {name}
-</objective>
-
-<files_to_read>
-- {context_path} (USER DECISIONS from /sdd-discuss-phase)
-- {requirements_path} (Project requirements)
-- {state_path} (Project decisions and history)
-</files_to_read>
-
-${AGENT_SKILLS_RESEARCHER}
-
-<additional_context>
-Phase description: {description}
-</additional_context>
-
-<output>
-Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
-</output>",
-  subagent_type="sdd-phase-researcher",
-  model="{researcher_model}"
-)
-```
-
-## Step 5: Handle Return
-
-- `## RESEARCH COMPLETE` — Display summary, offer: Plan/Dig deeper/Review/Done
-- `## CHECKPOINT REACHED` — Present to user, spawn continuation
-- `## RESEARCH INCONCLUSIVE` — Show attempts, offer: Add context/Try different mode/Manual
-
-</process>