@bhargavvc/sdd-cc 1.30.0 → 1.35.0

package/sdd/workflows/verify-work.md

@@ -1,5 +1,5 @@
 <purpose>
-Validate built features through conversational testing with persistent state. Creates UAT.md that tracks test progress, survives /clear, and feeds gaps into /sdd:plan-phase --gaps.
+Validate built features through conversational testing with persistent state. Creates UAT.md that tracks test progress, survives /clear, and feeds gaps into /sdd-plan-phase --gaps.
 
 User tests, Claude records. One test at a time. Plain text responses.
 </purpose>
@@ -78,7 +78,7 @@ If no, continue to `create_uat_file`.
 ```
 No active UAT sessions.
 
-Provide a phase number to start testing (e.g., /sdd:verify-work 4)
+Provide a phase number to start testing (e.g., /sdd-verify-work 4)
 ```
 
 **If no active sessions AND $ARGUMENTS provided:**
@@ -86,6 +86,42 @@ Provide a phase number to start testing (e.g., /sdd:verify-work 4)
 Continue to `create_uat_file`.
 </step>
 
+<step name="automated_ui_verification">
+**Automated UI Verification (when Playwright-MCP is available)**
+
+Before running manual UAT, check whether this phase has a UI component and whether
+`mcp__playwright__*` or `mcp__puppeteer__*` tools are available in the current session.
+
+```
+UI_PHASE_FLAG=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" config-get workflow.ui_phase --raw 2>/dev/null || echo "true")
+UI_SPEC_FILE=$(ls "${PHASE_DIR}"/*-UI-SPEC.md 2>/dev/null | head -1)
+```
+
+**If Playwright-MCP tools are available in this session (`mcp__playwright__*` tools
+respond to tool calls) AND (`UI_PHASE_FLAG` is `true` OR `UI_SPEC_FILE` is non-empty):**
+
+For each UI checkpoint listed in the phase's UI-SPEC.md (or inferred from SUMMARY.md):
+
+1. Use `mcp__playwright__navigate` (or equivalent) to open the component's URL.
+2. Use `mcp__playwright__screenshot` to capture a screenshot.
+3. Compare the screenshot visually against the spec's stated requirements
+   (dimensions, color, layout, spacing).
+4. Automatically mark checkpoints as **passed** or **needs review** based on the
+   visual comparison — no manual question required for items that clearly match.
+5. Flag items that require human judgment (subjective aesthetics, content accuracy)
+   and present only those as manual UAT questions.
+
+If automated verification is not available, fall back to the standard manual
+checkpoint questions defined in this workflow unchanged. This step is entirely
+conditional: if Playwright-MCP is not configured, behavior is unchanged from today.
+
+**Display summary line before proceeding:**
+```
+UI checkpoints: {N} auto-verified, {M} queued for manual review
+```
+
+</step>
+
 <step name="find_summaries">
 **Find what to test:**
 
@@ -212,6 +248,8 @@ Display the returned checkpoint EXACTLY as-is:
 - Do NOT add commentary before or after the block.
 - If you notice protocol/meta markers such as `to=all:`, role-routing text, XML system tags, hidden instruction markers, ad copy, or any unrelated suffix, discard the draft and output `{CHECKPOINT}` only.
 
+
+**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.
 Wait for user response (plain text, no AskUserQuestion).
 </step>
 
@@ -375,12 +413,48 @@ Present summary:
 **If issues > 0:** Proceed to `diagnose_issues`
 
 **If issues == 0:**
+
+```bash
+SECURITY_CFG=$(node "$HOME/.claude/sdd/bin/sdd-tools.cjs" config-get workflow.security_enforcement --raw 2>/dev/null || echo "true")
+SECURITY_FILE=$(ls "${PHASE_DIR}"/*-SECURITY.md 2>/dev/null | head -1)
+```
+
+If `SECURITY_CFG` is `true` AND `SECURITY_FILE` is empty:
 ```
+⚠ Security enforcement enabled — /sdd-secure-phase {phase} has not run.
+Run before advancing to the next phase.
+
 All tests passed. Ready to continue.
 
-- `/sdd:plan-phase {next}` — Plan next phase
-- `/sdd:execute-phase {next}` — Execute next phase
-- `/sdd:ui-review {phase}` — visual quality audit (if frontend files were modified)
+- `/sdd-secure-phase {phase}` — security review (required before advancing)
+- `/sdd-plan-phase {next}` — Plan next phase
+- `/sdd-execute-phase {next}` — Execute next phase
+- `/sdd-ui-review {phase}` — visual quality audit (if frontend files were modified)
+```
+
+If `SECURITY_CFG` is `true` AND `SECURITY_FILE` exists: check frontmatter `threats_open`. If > 0:
+```
+⚠ Security gate: {threats_open} threats open
+  /sdd-secure-phase {phase} — resolve before advancing
+```
+
+If `SECURITY_CFG` is `false` OR (`SECURITY_FILE` exists AND `threats_open` is `0`):
+
+**Auto-transition: mark phase complete in ROADMAP.md and STATE.md**
+
+Execute the transition workflow inline (do NOT use Task — the orchestrator context already holds the UAT results and phase data needed for accurate transition):
+
+Read and follow `~/.claude/sdd/workflows/transition.md`.
+
+After transition completes, present next-step options to the user:
+
+```
+All tests passed. Phase {phase} marked complete.
+
+- `/sdd-plan-phase {next}` — Plan next phase
+- `/sdd-execute-phase {next}` — Execute next phase
+- `/sdd-secure-phase {phase}` — security review
+- `/sdd-ui-review {phase}` — visual quality audit (if frontend files were modified)
 ```
 </step>
 
@@ -438,7 +512,7 @@ ${AGENT_SKILLS_PLANNER}
 </planning_context>
 
 <downstream_consumer>
-Output consumed by /sdd:execute-phase
+Output consumed by /sdd-execute-phase
 Plans must be executable prompts.
 </downstream_consumer>
 """,
@@ -551,7 +625,7 @@ Display: `Max iterations reached. {N} issues remain.`
 Offer options:
 1. Force proceed (execute despite issues)
 2. Provide guidance (user gives direction, retry)
-3. Abandon (exit, user runs /sdd:plan-phase manually)
+3. Abandon (exit, user runs /sdd-plan-phase manually)
 
 Wait for user response.
 </step>
@@ -579,7 +653,7 @@ Plans verified and ready for execution.
 
 **Execute fixes** — run fix plans
 
-`/clear` then `/sdd:execute-phase {phase} --gaps-only`
+`/clear` then `/sdd-execute-phase {phase} --gaps-only`
 
 ───────────────────────────────────────────────────────────────
 ```
@@ -633,5 +707,5 @@ Default to **major** if unclear. User can correct if needed.
 - [ ] If issues: sdd-planner creates fix plans (gap_closure mode)
 - [ ] If issues: sdd-plan-checker verifies fix plans
 - [ ] If issues: revision loop until plans pass (max 3 iterations)
-- [ ] Ready for `/sdd:execute-phase --gaps-only` when complete
+- [ ] Ready for `/sdd-execute-phase --gaps-only` when complete
 </success_criteria>

package/sdd/commands/sdd/workstreams.md

@@ -1,63 +0,0 @@
----
-description: Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
----
-
-# /sdd:workstreams
-
-Manage parallel workstreams for concurrent milestone work.
-
-## Usage
-
-`/sdd:workstreams [subcommand] [args]`
-
-### Subcommands
-
-| Command | Description |
-|---------|-------------|
-| `list` | List all workstreams with status |
-| `create <name>` | Create a new workstream |
-| `status <name>` | Detailed status for one workstream |
-| `switch <name>` | Set active workstream |
-| `progress` | Progress summary across all workstreams |
-| `complete <name>` | Archive a completed workstream |
-| `resume <name>` | Resume work in a workstream |
-
-## Step 1: Parse Subcommand
-
-Parse the user's input to determine which workstream operation to perform.
-If no subcommand given, default to `list`.
-
-## Step 2: Execute Operation
-
-### list
-Run: `node "$SDD_TOOLS" workstream list --raw --cwd "$CWD"`
-Display the workstreams in a table format showing name, status, current phase, and progress.
-
-### create
-Run: `node "$SDD_TOOLS" workstream create <name> --raw --cwd "$CWD"`
-After creation, display the new workstream path and suggest next steps:
-- `/sdd:new-milestone --ws <name>` to set up the milestone
-
-### status
-Run: `node "$SDD_TOOLS" workstream status <name> --raw --cwd "$CWD"`
-Display detailed phase breakdown and state information.
-
-### switch
-Run: `node "$SDD_TOOLS" workstream set <name> --raw --cwd "$CWD"`
-Also set `SDD_WORKSTREAM` env var for the current session.
-
-### progress
-Run: `node "$SDD_TOOLS" workstream progress --raw --cwd "$CWD"`
-Display a progress overview across all workstreams.
-
-### complete
-Run: `node "$SDD_TOOLS" workstream complete <name> --raw --cwd "$CWD"`
-Archive the workstream to milestones/.
-
-### resume
-Set the workstream as active and suggest `/sdd:resume-work --ws <name>`.
-
-## Step 3: Display Results
-
-Format the JSON output from sdd-tools into a human-readable display.
-Include the `${SDD_WS}` flag in any routing suggestions.