gsd-remix 1.0.2 → 1.1.0

package/get-shit-done/workflows/execute-phase.md

@@ -43,10 +43,7 @@ Always use the exact name from this list — do not fall back to 'general-purpos
 - gsd-debugger — Diagnoses and fixes issues
 - gsd-codebase-mapper — Maps project structure and dependencies
 - gsd-integration-checker — Checks cross-phase integration
-- gsd-nyquist-auditor — Validates verification coverage
-- gsd-ui-researcher — Researches UI/UX approaches
-- gsd-ui-checker — Reviews UI implementation quality
-- gsd-ui-auditor — Audits UI against design requirements
+- gsd-security-auditor — Diff-scoped security review (fallback when no company security skill)
 </available_agent_types>
 
 <process>
@@ -57,8 +54,6 @@ Parse `$ARGUMENTS` before loading any context:
 - First positional token → `PHASE_ARG`
 - Optional `--wave N` → `WAVE_FILTER`
 - Optional `--gaps-only` keeps its current meaning
-- Optional `--cross-ai` → `CROSS_AI_FORCE=true` (force all plans through cross-AI execution)
-- Optional `--no-cross-ai` → `CROSS_AI_DISABLED=true` (disable cross-AI for this run, overrides config and frontmatter)
 
 If `--wave` is absent, preserve the current behavior of executing all incomplete waves in the phase.
 </step>
@@ -72,9 +67,6 @@ if ! command -v gsd-remix-sdk &>/dev/null; then
   echo ""
   echo "Repair the bundled SDK:"
   echo "  /gsd-health --runtime --repair"
-  echo ""
-  echo "Or refresh all runtime assets:"
-  echo "  /gsd-update"
   exit 1
 fi
 
@@ -286,77 +278,6 @@ Report:
 ```
 </step>
 
-<step name="cross_ai_delegation">
-**Optional step 2.5 — Delegate plans to an external AI runtime.**
-
-This step runs after plan discovery and before normal wave execution. It identifies plans
-that should be delegated to an external AI command and executes them via stdin-based prompt
-delivery. Plans handled here are removed from the execute_waves plan list so the normal
-executor skips them.
-
-**Activation logic:**
-
-1. If `CROSS_AI_DISABLED` is true (`--no-cross-ai` flag): skip this step entirely.
-2. If `CROSS_AI_FORCE` is true (`--cross-ai` flag): mark ALL incomplete plans for cross-AI execution.
-3. Otherwise: check each plan's frontmatter for `cross_ai: true` AND verify config
-   `workflow.cross_ai_execution` is `true`. Plans matching both conditions are marked for cross-AI.
-
-```bash
-CROSS_AI_ENABLED=$(gsd-remix-sdk query config-get workflow.cross_ai_execution 2>/dev/null || echo "false")
-CROSS_AI_CMD=$(gsd-remix-sdk query config-get workflow.cross_ai_command 2>/dev/null || echo "")
-CROSS_AI_TIMEOUT=$(gsd-remix-sdk query config-get workflow.cross_ai_timeout 2>/dev/null || echo "300")
-```
-
-**If no plans are marked for cross-AI:** Skip to execute_waves.
-
-**If plans are marked but `cross_ai_command` is empty:** Error — tell user to set
-`workflow.cross_ai_command` via `gsd-remix-sdk query config-set workflow.cross_ai_command "<command>"`.
-
-**For each cross-AI plan (sequentially):**
-
-1. **Construct the task prompt** from the plan file:
-   - Extract `<objective>` and `<tasks>` sections from the PLAN.md
-   - Append PROJECT.md context (project name, description, tech stack)
-   - Format as a self-contained execution prompt
-
-2. **Check for dirty working tree before execution:**
-   ```bash
-   if ! git diff --quiet HEAD 2>/dev/null; then
-     echo "WARNING: dirty working tree detected — the external AI command may produce uncommitted changes that conflict with existing modifications"
-   fi
-   ```
-
-3. **Run the external command** from the project root, writing the prompt to stdin.
-   Never shell-interpolate the prompt — always pipe via stdin to prevent injection:
-   ```bash
-   echo "$TASK_PROMPT" | timeout "${CROSS_AI_TIMEOUT}s" ${CROSS_AI_CMD} > "$CANDIDATE_SUMMARY" 2>"$ERROR_LOG"
-   EXIT_CODE=$?
-   ```
-
-4. **Evaluate the result:**
-
-   **Success (exit 0 + valid summary):**
-   - Read `$CANDIDATE_SUMMARY` and validate it contains meaningful content
-     (not empty, has at least a heading and description — a valid SUMMARY.md structure)
-   - Write it as the plan's SUMMARY.md file
-   - Update STATE.md plan status to complete
-   - Update ROADMAP.md progress
-   - Mark plan as handled — skip it in execute_waves
-
-   **Failure (non-zero exit or invalid summary):**
-   - Display the error output and exit code
-   - Warn: "The external command may have left uncommitted changes or partial edits
-     in the working tree. Review `git status` and `git diff` before proceeding."
-   - Offer three choices:
-     - **retry** — run the same plan through cross-AI again
-     - **skip** — fall back to normal executor for this plan (re-add to execute_waves list)
-     - **abort** — stop execution entirely, preserve state for resume
-
-5. **After all cross-AI plans processed:** Remove successfully handled plans from the
-   incomplete plan list so execute_waves skips them. Any skipped-to-fallback plans remain
-   in the list for normal executor processing.
-</step>
-
 <step name="execute_waves">
 Execute each selected wave in sequence. Within a wave: parallel if `PARALLELIZATION=true`, sequential if `false`.
 
@@ -967,26 +888,6 @@ After all waves:
 [Aggregate from SUMMARYs, or "None"]
 ```
 
-**Security gate check:**
-```bash
-SECURITY_CFG=$(gsd-remix-sdk query 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 `false`: skip.
-
-If `SECURITY_CFG` is `true` AND `SECURITY_FILE` is empty (no SECURITY.md yet):
-Include in the next-steps routing output:
-```
-⚠ Security enforcement enabled — run before advancing:
-  /gsd-secure-phase {PHASE} ${GSD_WS}
-```
-
-If `SECURITY_CFG` is `true` AND SECURITY.md exists: check frontmatter `threats_open`. If > 0:
-```
-⚠ Security gate: {threats_open} threats open
-  /gsd-secure-phase {PHASE} — resolve before advancing
-```
 </step>
 
 <step name="tdd_review_checkpoint">
@@ -1094,7 +995,56 @@ Code review found issues. Consider running:
 
 **Error handling:** If the Skill invocation fails or throws, catch the error, display "Code review encountered an error (non-blocking): {error}" and proceed to next step. Review failures must never block execution.
 
-Regardless of review result, ALWAYS proceed to close_parent_artifacts → regression_gate → verify_phase_goal.
+Regardless of review result, ALWAYS proceed to security_review_gate → close_parent_artifacts → regression_gate → verify_phase_goal.
+</step>
+
+<step name="security_review_gate" required="true">
+**Advisory security review anchored on the phase's real diff.** Never blocks execution flow.
+
+**1. Config gate:**
+```bash
+SECURITY_REVIEW=$(gsd-remix-sdk query config-get workflow.security_review 2>/dev/null || echo "auto")
+```
+
+If `SECURITY_REVIEW` is `"off"`: display `Security review skipped: workflow.security_review=off` and proceed to next step.
+
+**2. Resolve changed-file scope (reuse, don't recompute):** resolution order is `--files` argument > aggregated `files_modified` from this phase's SUMMARY.md files > `git diff --name-only` against the phase's starting commit.
+```bash
+CHANGED_FILES=$(grep -h "^- " "${PHASE_DIR}"/*-SUMMARY.md 2>/dev/null | grep -oE '[^ ]+\.[a-zA-Z]+' | sort -u)
+[ -z "$CHANGED_FILES" ] && CHANGED_FILES=$(git diff --name-only "${PHASE_START_COMMIT:-HEAD~10}" 2>/dev/null)
+```
+
+**3. Trigger decision:**
+
+- If `SECURITY_REVIEW` is `"always"` → trigger. Reviewer model: **opus**.
+- If `SECURITY_REVIEW` is `"auto"`:
+  - **Hard rules (no AI judgment — low-frequency files only):** trigger if any changed file matches `.env*`, `Dockerfile*`, or CI config (`.github/workflows/`, `.gitlab-ci.yml`, `Jenkinsfile`, `cloudbuild.*`, `.circleci/`). Reviewer model: **opus**.
+  - **Otherwise, AI judgment:** read the changed-file list and each plan's SUMMARY (including any `## Security-Relevant Surface` section) and decide whether the change plausibly touches: auth/authz/session handling; secrets or crypto; user input, deserialization, or file upload; new network endpoints; path/SQL/command string concatenation; permissions/CORS/Cookie config; XSS or unsafe HTML rendering; SSRF (outbound requests from BFF/server); PII or credentials in logs; redirects.
+    Lean toward triggering when the diff **adds a new dependency** (package.json/lockfile changes are NOT a hard rule — they are a hint). Additional hints (hint only, never auto-trigger): tenant/account/org boundary changes; webhook signature verification or callbacks; rate limiting/abuse protection; audit logging or admin-privilege paths; billing/entitlement gating.
+    Reviewer model when triggered via semantic signal: **sonnet**.
+  - **If not triggered:** you MUST display one line — `Security review skipped: {short reason, e.g. "docs-only diff, no security-relevant surface"}` — then proceed to next step. Silent skips are not allowed.
+
+**4. Invoke review (company skill first, generic fallback second):**
+
+Try the company skill via try-invoke-and-catch (do NOT probe the filesystem for skills — plugin-provided skills are not discoverable that way):
+```
+Skill(skill="security-code-review", args="{changed file list}")
+```
+
+If the Skill invocation fails or the skill does not exist, fall back to the bundled generic reviewer:
+```
+Task(
+  subagent_type="gsd-security-auditor",
+  model="{opus for hard-rule/always triggers, sonnet for auto semantic triggers}",
+  prompt="<changed_files>{list}</changed_files>
+<diff>run: git diff {phase start ref} -- {changed files}</diff>
+<trigger_reason>{hard rule | semantic signal | always}</trigger_reason>
+<summary_surface>{## Security-Relevant Surface content from SUMMARYs, if any}</summary_surface>",
+  description="Security review: phase {N} diff"
+)
+```
+
+**5. Relay findings.** Display the reviewer's findings table to the user. Critical/high findings deserve a suggestion to fix before shipping — but this gate is advisory: regardless of findings or errors, ALWAYS proceed to close_parent_artifacts. If the review itself errors, display `Security review encountered an error (non-blocking): {error}` and proceed.
 </step>
 
 <step name="close_parent_artifacts">
@@ -1385,7 +1335,7 @@ All automated checks passed. {N} items need human testing:
 
 {From VERIFICATION.md human_verification section}
 
-Items saved to `{phase_num}-HUMAN-UAT.md` — they will appear in `/gsd-progress` and `/gsd-audit-uat`.
+Items saved to `{phase_num}-HUMAN-UAT.md` — they will appear in `/gsd-progress`.
 
 "approved" → continue | Report issues → gap closure
 ```
@@ -1480,7 +1430,7 @@ Extract from result: `next_phase`, `next_phase_name`, `is_last_phase`, `warnings
 
 {list each warning}
 
-These items are tracked and will appear in `/gsd-progress` and `/gsd-audit-uat`.
+These items are tracked and will appear in `/gsd-progress`.
 ```
 
 ```bash

package/get-shit-done/workflows/execute-plan.md

@@ -61,11 +61,11 @@ PHASE=$(echo "$PLAN_PATH" | grep -oE '[0-9]+(\.[0-9]+)?-[0-9]+')
 # config settings can be fetched via gsd-remix-sdk query config-get if needed
 ```
 
-<if mode="yolo">
+<if mode="yolo" OR="gates.execute_next_plan is false or absent">
 Auto-approve: `⚡ Execute {phase}-{plan}-PLAN.md [Plan X of Y for Phase Z]` → parse_segments.
 </if>
 
-<if mode="interactive" OR="custom with gates.execute_next_plan true">
+<if mode="interactive" AND="gates.execute_next_plan is explicitly true">
 Present plan identification, wait for confirmation.
 </if>
 </step>
@@ -91,7 +91,7 @@ Parse JSON for: `task_count`, `inline_threshold`, `checkpoint_mode`, `threshold_
 Use the route returned by `plan.execution-route` by default. This decision is deterministic and code-based — do NOT substitute your own LLM judgment unless the query failed.
 
 Routing rules encoded in the query:
-- `INLINE_THRESHOLD` remains the hard floor. If `task_count <= INLINE_THRESHOLD`, use inline execution immediately.
+- `INLINE_THRESHOLD` remains the hard floor. If `INLINE_THRESHOLD > 0` and `task_count <= INLINE_THRESHOLD`, use inline execution immediately. A threshold of `0` disables inline routing.
 - For plans above the threshold, a conservative low-complexity override is allowed only for simple `3-5` task plans with:
   - no checkpoint tasks
   - small file surface
@@ -121,7 +121,7 @@ If `EXECUTION_ROUTE` failed or returned no usable recommendation:
   grep -n 'type="checkpoint' "$PLAN_FILE"
   ```
   - count `<task>` tags
-  - inline when `TASK_COUNT <= INLINE_THRESHOLD`
+  - inline when `INLINE_THRESHOLD > 0` and `TASK_COUNT <= INLINE_THRESHOLD`
   - otherwise apply checkpoint-based routing
 
 **Pattern A:** init_agent_tracking → capture `EXPECTED_BASE=$(git rev-parse HEAD)` → spawn Task(subagent_type="gsd-executor", model=executor_model) with prompt: execute plan at [path], autonomous, all tasks + SUMMARY + commit, follow deviation/auth rules, report: plan name, tasks, SUMMARY path, commit hash → track agent_id → wait → update tracking → report. **Include `isolation="worktree"` only if `workflow.use_worktrees` is not `false`** (read via `config-get workflow.use_worktrees`). **When using `isolation="worktree"`, include a `<worktree_branch_check>` block in the prompt** instructing the executor to run `git merge-base HEAD {EXPECTED_BASE}` and, if the result differs from `{EXPECTED_BASE}`, hard-reset the branch with `git reset --hard {EXPECTED_BASE}` before starting work (safe — runs before any agent work), then verify with `[ "$(git rev-parse HEAD)" != "{EXPECTED_BASE}" ] && exit 1`. This corrects a known issue where `EnterWorktree` creates branches from `main` instead of the feature branch HEAD (affects all platforms).

package/get-shit-done/workflows/health.md

@@ -153,13 +153,13 @@ Warnings: N
 ## Warnings
 
 - [legacy_bridge_missing] No gsd-tools.cjs bridge could be found for CJS fallback commands.
-  Fix: Run /gsd-update to restore the bundled bridge. Use /gsd-health --runtime --repair only for SDK CLI repair.
+  Fix: Reinstall GSD to restore the bundled bridge. Use /gsd-health --runtime --repair only for SDK CLI repair.
 ```
 
 **Footer:**
 ```
 ---
-Runtime mode is read-only unless --repair is set. Use /gsd-health --runtime --repair to rebuild the bundled SDK, or /gsd-update to refresh all runtime assets.
+Runtime mode is read-only unless --repair is set. Use /gsd-health --runtime --repair to rebuild the bundled SDK, or reinstall GSD to refresh all runtime assets.
 ```
 
 Then STOP. Do not proceed to repair prompts.
@@ -266,8 +266,6 @@ Report final status.
 | W005 | warning | Phase directory naming mismatch | No |
 | W006 | warning | Phase in ROADMAP but no directory | No |
 | W007 | warning | Phase on disk but not in ROADMAP | No |
-| W008 | warning | config.json: workflow.nyquist_validation absent (defaults to enabled but agents may skip) | Yes |
-| W009 | warning | Phase has Validation Architecture in RESEARCH.md but no VALIDATION.md | No |
 | W018 | warning | MILESTONES.md missing entry for archived milestone snapshot | Yes (`--backfill`) |
 | W019 | warning | Unrecognized .planning/ root file — not a canonical GSD artifact | No |
 | I001 | info | Plan without SUMMARY (may be in progress) | No |
@@ -281,7 +279,6 @@ Report final status.
 | createConfig | Create config.json with defaults | None |
 | resetConfig | Delete + recreate config.json | Loses custom settings |
 | regenerateState | Create STATE.md from ROADMAP structure when it is missing | Loses session history |
-| addNyquistKey | Add workflow.nyquist_validation: true to config.json | None — matches existing default |
 | backfillMilestones | Synthesize missing MILESTONES.md entries from `.planning/milestones/vX.Y-ROADMAP.md` snapshots | None — additive only; triggered by `--backfill` flag |
 
 **Not repairable (too risky):**

package/get-shit-done/workflows/help.md

@@ -82,15 +82,6 @@ Comprehensive ecosystem research for niche/complex domains.
 
 Usage: `/gsd-research-phase 3`
 
-**`/gsd-list-phase-assumptions <number>`**
-See what Claude is planning to do before it starts.
-
-- Shows Claude's intended approach for a phase
-- Lets you course-correct if Claude misunderstood your vision
-- No files created - conversational output only
-
-Usage: `/gsd-list-phase-assumptions 3`
-
 **`/gsd-plan-phase <number>`**
 Create detailed execution plan for a specific phase.
 
@@ -276,57 +267,6 @@ Systematic debugging with persistent state across context resets.
 Usage: `/gsd-debug "login button doesn't work"`
 Usage: `/gsd-debug` (resume active session)
 
-### Spiking & Sketching
-
-**`/gsd-spike [idea] [--quick]`**
-Rapidly spike an idea with throwaway experiments to validate feasibility.
-
-- Decomposes idea into 2-5 focused experiments (risk-ordered)
-- Each spike answers one specific Given/When/Then question
-- Builds minimum code, runs it, captures verdict (VALIDATED/INVALIDATED/PARTIAL)
-- Saves to `.planning/spikes/` with MANIFEST.md tracking
-- Does not require `/gsd-new-project` — works in any repo
-- `--quick` skips decomposition, builds immediately
-
-Usage: `/gsd-spike "can we stream LLM output over WebSockets?"`
-Usage: `/gsd-spike --quick "test if pdfjs extracts tables"`
-
-**`/gsd-sketch [idea] [--quick]`**
-Rapidly sketch UI/design ideas using throwaway HTML mockups with multi-variant exploration.
-
-- Conversational mood/direction intake before building
-- Each sketch produces 2-3 variants as tabbed HTML pages
-- User compares variants, cherry-picks elements, iterates
-- Shared CSS theme system compounds across sketches
-- Saves to `.planning/sketches/` with MANIFEST.md tracking
-- Does not require `/gsd-new-project` — works in any repo
-- `--quick` skips mood intake, jumps to building
-
-Usage: `/gsd-sketch "dashboard layout for the admin panel"`
-Usage: `/gsd-sketch --quick "form card grouping"`
-
-**`/gsd-spike-wrap-up`**
-Package spike findings into a persistent project skill.
-
-- Curates each spike one-at-a-time (include/exclude/partial/UAT)
-- Groups findings by feature area
-- Generates `./.claude/skills/spike-findings-[project]/` with references and sources
-- Writes summary to `.planning/spikes/WRAP-UP-SUMMARY.md`
-- Adds auto-load routing line to project CLAUDE.md
-
-Usage: `/gsd-spike-wrap-up`
-
-**`/gsd-sketch-wrap-up`**
-Package sketch design findings into a persistent project skill.
-
-- Curates each sketch one-at-a-time (include/exclude/partial/revisit)
-- Groups findings by design area
-- Generates `./.claude/skills/sketch-findings-[project]/` with design decisions, CSS patterns, HTML structures
-- Writes summary to `.planning/sketches/WRAP-UP-SUMMARY.md`
-- Adds auto-load routing line to project CLAUDE.md
-
-Usage: `/gsd-sketch-wrap-up`
-
 ### Quick Notes
 
 **`/gsd-note <text>`**
@@ -382,33 +322,6 @@ Usage: `/gsd-verify-work 3`
 
 ### Ship Work
 
-**`/gsd-ship [phase]`**
-Create a PR from completed phase work with an auto-generated body.
-
-- Pushes branch to remote
-- Creates PR with summary from SUMMARY.md, VERIFICATION.md, REQUIREMENTS.md
-- Optionally requests code review
-- Updates STATE.md with shipping status
-
-Prerequisites: Phase verified, `gh` CLI installed and authenticated.
-
-Usage: `/gsd-ship 4` or `/gsd-ship 4 --draft`
-
----
-
-**`/gsd-review --phase N [--gemini] [--claude] [--codex] [--coderabbit] [--opencode] [--qwen] [--cursor] [--all]`**
-Cross-AI peer review — invoke external AI CLIs to independently review phase plans.
-
-- Detects available CLIs (gemini, claude, codex, coderabbit)
-- Each CLI reviews plans independently with the same structured prompt
-- CodeRabbit reviews the current git diff (not a prompt) — may take up to 5 minutes
-- Produces REVIEWS.md with per-reviewer feedback and consensus summary
-- Feed reviews back into planning: `/gsd-plan-phase N --reviews`
-
-Usage: `/gsd-review --phase 3 --all`
-
----
-
 **`/gsd-pr-branch [target]`**
 Create a clean branch for pull requests by filtering out .planning/ commits.
 
@@ -420,48 +333,6 @@ Usage: `/gsd-pr-branch` or `/gsd-pr-branch main`
 
 ---
 
-**`/gsd-plant-seed [idea]`**
-Capture a forward-looking idea with trigger conditions for automatic surfacing.
-
-- Seeds preserve WHY, WHEN to surface, and breadcrumbs to related code
-- Auto-surfaces during `/gsd-new-milestone` when trigger conditions match
-- Better than deferred items — triggers are checked, not forgotten
-
-Usage: `/gsd-plant-seed "add real-time notifications when we build the events system"`
-
----
-
-**`/gsd-audit-uat`**
-Cross-phase audit of all outstanding UAT and verification items.
-- Scans every phase for pending, skipped, blocked, and human_needed items
-- Cross-references against codebase to detect stale documentation
-- Produces prioritized human test plan grouped by testability
-- Use before starting a new milestone to clear verification debt
-
-Usage: `/gsd-audit-uat`
-
-### Milestone Auditing
-
-**`/gsd-audit-milestone [version]`**
-Audit milestone completion against original intent.
-
-- Reads all phase VERIFICATION.md files
-- Checks requirements coverage
-- Spawns integration checker for cross-phase wiring
-- Creates MILESTONE-AUDIT.md with gaps and tech debt
-
-Usage: `/gsd-audit-milestone`
-
-**`/gsd-plan-milestone-gaps`**
-Create phases to close gaps identified by audit.
-
-- Reads MILESTONE-AUDIT.md and groups gaps into phases
-- Prioritizes by requirement priority (must/should/nice)
-- Adds gap closure phases to ROADMAP.md
-- Ready for `/gsd-plan-phase` on new phases
-
-Usage: `/gsd-plan-milestone-gaps`
-
 ### Configuration
 
 **`/gsd-settings`**
@@ -473,16 +344,6 @@ Configure workflow toggles and model profile interactively.
 
 Usage: `/gsd-settings`
 
-**`/gsd-set-profile <profile>`**
-Quick switch model profile for GSD agents.
-
-- `quality` — Opus everywhere except verification
-- `balanced` — Opus for planning, Sonnet for execution (default)
-- `budget` — Sonnet for writing, Haiku for research/verification
-- `inherit` — Use current session model for all agents (OpenCode `/model`)
-
-Usage: `/gsd-set-profile budget`
-
 ### Utility Commands
 
 **`/gsd-cleanup`**
@@ -498,25 +359,6 @@ Usage: `/gsd-cleanup`
 **`/gsd-help`**
 Show this command reference.
 
-**`/gsd-update`**
-Update GSD to latest version with changelog preview.
-
-- Shows installed vs latest version comparison
-- Displays changelog entries for versions you've missed
-- Highlights breaking changes
-- Confirms before running install
-- Better than raw `npx get-shit-done-cc`
-
-Usage: `/gsd-update`
-
-**`/gsd-join-discord`**
-Join the GSD Discord community.
-
-- Get help, share what you're building, stay updated
-- Connect with other GSD users
-
-Usage: `/gsd-join-discord`
-
 ## Files & Structure
 
 ```
@@ -529,13 +371,6 @@ Usage: `/gsd-join-discord`
 ├── todos/                # Captured ideas and tasks
 │   ├── pending/          # Todos waiting to be worked on
 │   └── done/             # Completed todos
-├── spikes/               # Spike experiments (/gsd-spike)
-│   ├── MANIFEST.md       # Spike inventory and verdicts
-│   └── NNN-name/         # Individual spike directories
-├── sketches/             # Design sketches (/gsd-sketch)
-│   ├── MANIFEST.md       # Sketch inventory and winners
-│   ├── themes/           # Shared CSS theme files
-│   └── NNN-name/         # Individual sketch directories (HTML + README)
 ├── debug/                # Active debug sessions
 │   └── resolved/         # Archived resolved issues
 ├── milestones/

package/get-shit-done/workflows/new-milestone.md

@@ -46,55 +46,6 @@ If the flag is absent, keep the current behavior of continuing phase numbering f
 - Wait for their response, then use AskUserQuestion to probe specifics
 - If user selects "Other" at any point to provide freeform input, ask follow-up as plain text — not another AskUserQuestion
 
-## 2.5. Scan Planted Seeds
-
-Check `.planning/seeds/` for seed files that match the milestone goals gathered in step 2.
-
-```bash
-ls .planning/seeds/SEED-*.md 2>/dev/null
-```
-
-**If no seed files exist:** Skip this step silently — do not print any message or prompt.
-
-**If seed files exist:** Read each `SEED-*.md` file and extract from its frontmatter and body:
-- **Idea** — the seed title (heading after frontmatter, e.g. `# SEED-001: <idea>`)
-- **Trigger conditions** — the `trigger_when` frontmatter field and the "When to Surface" section's bullet list
-- **Planted during** — the `planted_during` frontmatter field (for context)
-
-Compare each seed's trigger conditions against the milestone goals from step 2. A seed matches when its trigger conditions are relevant to any of the milestone's target features or goals.
-
-**If no seeds match:** Skip silently — do not prompt the user.
-
-**If matching seeds found:**
-
-**`--auto` mode:** Auto-select ALL matching seeds. Log: `[auto] Selected N matching seed(s): [list seed names]`
-
-**Text mode (`TEXT_MODE=true`):** Present matching seeds as a plain-text numbered list:
-```
-Seeds that match your milestone goals:
-1. SEED-001: <idea> (trigger: <trigger_when>)
-2. SEED-003: <idea> (trigger: <trigger_when>)
-
-Enter numbers to include (comma-separated), or "none" to skip:
-```
-
-**Normal mode:** Present via AskUserQuestion:
-```
-AskUserQuestion(
-  header: "Seeds",
-  question: "These planted seeds match your milestone goals. Include any in this milestone's scope?",
-  multiSelect: true,
-  options: [
-    { label: "SEED-001: <idea>", description: "Trigger: <trigger_when> | Planted during: <planted_during>" },
-    ...
-  ]
-)
-```
-
-**After selection:**
-- Selected seeds become additional context for requirement definition in step 9. Store them in an accumulator (e.g. `$SELECTED_SEEDS`) so step 9 can reference the ideas and their "Why This Matters" sections when defining requirements.
-- Unselected seeds remain untouched in `.planning/seeds/` — never delete or modify seed files during this workflow.
-
 ## 3. Determine Milestone Version
 
 - Parse last version from MILESTONES.md
@@ -363,8 +314,6 @@ Display key findings from SUMMARY.md:
 
 Read PROJECT.md: core value, current milestone goals, validated requirements (what exists).
 
-**If `$SELECTED_SEEDS` is non-empty (from step 2.5):** Include selected seed ideas and their "Why This Matters" sections as additional input when defining requirements. Seeds provide user-validated feature ideas that should be incorporated into the requirement categories alongside research findings or conversation-gathered features.
-
 **If research exists:** Read FEATURES.md, extract feature categories.
 
 Present features by category:

package/get-shit-done/workflows/new-project.md

@@ -227,7 +227,7 @@ Create `.planning/config.json` with all settings (CLI fills in remaining default
 
 ```bash
 mkdir -p .planning
-gsd-remix-sdk query config-new-project '{"mode":"yolo","granularity":"[selected]","parallelization":true|false,"commit_docs":true|false,"model_profile":"quality|balanced|budget|inherit","workflow":{"research":true|false,"plan_check":true|false,"verifier":true|false,"nyquist_validation":true|false,"auto_advance":true}}'
+gsd-remix-sdk query config-new-project '{"mode":"yolo","granularity":"[selected]","parallelization":true|false,"commit_docs":true|false,"model_profile":"balanced|inherit","workflow":{"research":true|false,"plan_check":true|false,"verifier":true|false,"auto_advance":true}}'
 ```
 
 **If commit_docs = No:** Add `.planning/` to `.gitignore`.
@@ -247,36 +247,6 @@ gsd-remix-sdk query config-set workflow._auto_chain_active true
 
 Proceed to Step 4 (skip Steps 3 and 5).
 
-## 2b. Prior Spike/Sketch Detection
-
-Check for existing spike and sketch work that should inform project setup:
-
-```bash
-# Check for spike findings skill (project-local)
-SPIKE_SKILL=$(ls ./.claude/skills/spike-findings-*/SKILL.md 2>/dev/null | head -1)
-
-# Check for sketch findings skill (project-local)
-SKETCH_SKILL=$(ls ./.claude/skills/sketch-findings-*/SKILL.md 2>/dev/null | head -1)
-
-# Check for raw spikes/sketches in .planning/
-HAS_SPIKES=$(ls .planning/spikes/MANIFEST.md 2>/dev/null)
-HAS_SKETCHES=$(ls .planning/sketches/MANIFEST.md 2>/dev/null)
-```
-
-If any of these exist, surface them before questioning:
-
-```
-⚡ Prior exploration detected:
-{if SPIKE_SKILL}  ✓ Spike findings skill: {path} — validated patterns from experiments
-{if SKETCH_SKILL}  ✓ Sketch findings skill: {path} — validated design decisions
-{if HAS_SPIKES && !SPIKE_SKILL}  ◆ Raw spikes in .planning/spikes/ — consider `/gsd-spike-wrap-up` to package findings
-{if HAS_SKETCHES && !SKETCH_SKILL}  ◆ Raw sketches in .planning/sketches/ — consider `/gsd-sketch-wrap-up` to package findings
-
-These findings will be incorporated into project context and available to planning agents.
-```
-
-If spike/sketch findings skills exist, read their SKILL.md files to inform the questioning phase — they contain validated patterns, constraints, and design decisions that should shape the project definition.
-
 ## 3. Deep Questioning
 
 **If auto mode:** Skip (already handled in Step 2a). Extract project context from provided document instead and proceed to Step 4.
@@ -649,7 +619,7 @@ Create `.planning/config.json` with all settings (CLI fills in remaining default
 
 ```bash
 mkdir -p .planning
-gsd-remix-sdk query config-new-project '{"mode":"[yolo|interactive]","granularity":"[selected]","parallelization":true|false,"commit_docs":true|false,"model_profile":"quality|balanced|budget|inherit","workflow":{"research":true|false,"plan_check":true|false,"verifier":true|false,"nyquist_validation":[false if granularity=coarse, true otherwise]}}'
+gsd-remix-sdk query config-new-project '{"mode":"[yolo|interactive]","granularity":"[selected]","parallelization":true|false,"commit_docs":true|false,"model_profile":"balanced|inherit","workflow":{"research":true|false,"plan_check":true|false,"verifier":true|false}}'
 ```
 
 **Note:** Run `/gsd-settings` anytime to update model profile, workflow agents, branching strategy, and other preferences.
@@ -1296,37 +1266,6 @@ Exit skill and invoke SlashCommand("/gsd-discuss-phase 1 --auto")
 
 **If interactive mode:**
 
-Check if Phase 1 has UI indicators (look for `**UI hint**: yes` in Phase 1 detail section of ROADMAP.md):
-
-```bash
-PHASE1_SECTION=$(gsd-remix-sdk query roadmap.get-phase 1 2>/dev/null)
-PHASE1_HAS_UI=$(echo "$PHASE1_SECTION" | grep -qi "UI hint.*yes" && echo "true" || echo "false")
-```
-
-**If Phase 1 has UI (`PHASE1_HAS_UI` is `true`):**
-
-```
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up — [${PROJECT_CODE}] ${PROJECT_TITLE}
-
-**Phase 1: [Phase Name]** — [Goal from ROADMAP.md]
-
-/clear then:
-
-/gsd-discuss-phase 1 — gather context and clarify approach
-
----
-
-**Also available:**
-- /gsd-ui-phase 1 — generate UI design contract (recommended for frontend phases)
-- /gsd-plan-phase 1 — skip discussion, plan directly
-
-───────────────────────────────────────────────────────────────
-```
-
-**If Phase 1 has no UI:**
-
 ```
 ───────────────────────────────────────────────────────────────