gsd-remix 1.0.2 → 1.1.0

package/get-shit-done/templates/config.json

@@ -6,19 +6,11 @@
     "plan_check": true,
     "verifier": true,
     "auto_advance": false,
-    "nyquist_validation": true,
-    "security_enforcement": true,
-    "security_asvs_level": 1,
-    "security_block_on": "high",
+    "nyquist_validation": false,
+    "security_enforcement": false,
+    "security_review": "auto",
     "discuss_mode": "discuss",
-    "research_before_questions": false,
-    "code_review_command": null,
-    "plan_bounce": false,
-    "plan_bounce_script": null,
-    "plan_bounce_passes": 2,
-    "cross_ai_execution": false,
-    "cross_ai_command": "",
-    "cross_ai_timeout": 300
+    "research_before_questions": false
   },
   "planning": {
     "commit_docs": true,
@@ -34,13 +26,7 @@
     "min_plans_for_parallel": 2
   },
   "gates": {
-    "confirm_project": true,
-    "confirm_phases": true,
-    "confirm_roadmap": true,
-    "confirm_breakdown": true,
-    "confirm_plan": true,
-    "execute_next_plan": true,
-    "issues_review": true,
+    "execute_next_plan": false,
     "confirm_transition": true
   },
   "safety": {

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

@@ -275,45 +275,6 @@ PHASE_STATE=$(gsd-remix-sdk query init.phase-op ${PHASE_NUM})
 
 Check `has_context`. If false → go to handle_blocker: "Discuss for phase ${PHASE_NUM} did not produce CONTEXT.md."
 
-**3a.5. UI Design Contract (Frontend Phases)**
-
-Check if this phase has frontend indicators and whether a UI-SPEC already exists:
-
-```bash
-PHASE_SECTION=$(gsd-remix-sdk query roadmap.get-phase ${PHASE_NUM} 2>/dev/null)
-echo "$PHASE_SECTION" | grep -iE "UI|interface|frontend|component|layout|page|screen|view|form|dashboard|widget" > /dev/null 2>&1
-HAS_UI=$?
-UI_SPEC_FILE=$(ls "${PHASE_DIR}"/*-UI-SPEC.md 2>/dev/null | head -1)
-```
-
-Check if UI phase workflow is enabled:
-
-```bash
-UI_PHASE_CFG=$(gsd-remix-sdk query config-get workflow.ui_phase 2>/dev/null || echo "true")
-```
-
-**If `HAS_UI` is 0 (frontend indicators found) AND `UI_SPEC_FILE` is empty (no UI-SPEC exists) AND `UI_PHASE_CFG` is not `false`:**
-
-Display:
-
-```
-Phase ${PHASE_NUM}: Frontend phase detected — generating UI design contract...
-```
-
-```
-Skill(skill="gsd-ui-phase", args="${PHASE_NUM}")
-```
-
-Verify UI-SPEC was created:
-
-```bash
-UI_SPEC_FILE=$(ls "${PHASE_DIR}"/*-UI-SPEC.md 2>/dev/null | head -1)
-```
-
-**If `UI_SPEC_FILE` is still empty after ui-phase:** Display warning `Phase ${PHASE_NUM}: UI-SPEC generation did not produce output — continuing without design contract.` and proceed to 3b.
-
-**If `HAS_UI` is 1 (no frontend indicators) OR `UI_SPEC_FILE` is not empty (UI-SPEC already exists) OR `UI_PHASE_CFG` is `false`:** Skip silently to 3b.
-
 **3b. Plan**
 
 **If `INTERACTIVE` is set:** Dispatch plan as a background agent to keep the main context lean. While plan runs, the workflow can immediately start discussing the next phase (see step 4).
@@ -473,38 +434,6 @@ On **"Continue without fixing"**: Display `Phase ${PHASE_NUM} ⏭ Gaps deferred`
 
 On **"Stop autonomous mode"**: Go to handle_blocker with "User stopped — gaps remain in phase ${PHASE_NUM}".
 
-**3d.5. UI Review (Frontend Phases)**
-
-> Run after any successful execution routing (passed, human_needed accepted, or gaps deferred/accepted) — before proceeding to the iterate step.
-
-Check if this phase had a UI-SPEC (created in step 3a.5 or pre-existing):
-
-```bash
-UI_SPEC_FILE=$(ls "${PHASE_DIR}"/*-UI-SPEC.md 2>/dev/null | head -1)
-```
-
-Check if UI review is enabled:
-
-```bash
-UI_REVIEW_CFG=$(gsd-remix-sdk query config-get workflow.ui_review 2>/dev/null || echo "true")
-```
-
-**If `UI_SPEC_FILE` is not empty AND `UI_REVIEW_CFG` is not `false`:**
-
-Display:
-
-```
-Phase ${PHASE_NUM}: Frontend phase with UI-SPEC — running UI review audit...
-```
-
-```
-Skill(skill="gsd-ui-review", args="${PHASE_NUM}")
-```
-
-Display the review result summary (score from UI-REVIEW.md if produced). Continue to iterate step regardless of score — UI review is advisory, not blocking.
-
-**If `UI_SPEC_FILE` is empty OR `UI_REVIEW_CFG` is `false`:** Skip silently to iterate step.
-
 </step>
 
 <step name="smart_discuss">
@@ -540,7 +469,7 @@ Read and execute: `$HOME/.claude/get-shit-done/references/autonomous-smart-discu
  Resume with: /gsd-autonomous --from ${next_incomplete_phase}
 ```
 
-Proceed directly to lifecycle step (which handles partial completion — skips audit/complete/cleanup since not all phases are done). Exit cleanly.
+Proceed directly to lifecycle step (which handles partial completion — skips complete/cleanup since not all phases are done). Exit cleanly.
 
 **Otherwise:** After each phase completes, re-read ROADMAP.md to catch phases inserted mid-execution (decimal phases like 5.1):
 
@@ -579,7 +508,7 @@ If all phases complete, proceed to lifecycle step.
 
 ## 5. Lifecycle
 
-**If `ONLY_PHASE` is set:** Skip lifecycle. A single phase does not trigger audit/complete/cleanup. Display:
+**If `ONLY_PHASE` is set:** Skip lifecycle. A single phase does not trigger complete/cleanup. Display:
 
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
@@ -590,12 +519,12 @@ If all phases complete, proceed to lifecycle step.
  Mode: Single phase (--only)
 
  Lifecycle skipped — run /gsd-autonomous without --only
- after all phases complete to trigger audit/complete/cleanup.
+ after all phases complete to trigger complete/cleanup.
 ```
 
 Exit cleanly.
 
-**Otherwise:** After all phases complete, run the milestone lifecycle sequence: audit → complete → cleanup.
+**Otherwise:** After all phases complete, run the milestone lifecycle sequence: complete → cleanup.
 
 Display lifecycle transition banner:
 
@@ -604,66 +533,10 @@ Display lifecycle transition banner:
  GSD ► AUTONOMOUS ▸ LIFECYCLE
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
- All phases complete → Starting lifecycle: audit → complete → cleanup
+ All phases complete → Starting lifecycle: complete → cleanup
  Milestone: {milestone_version} — {milestone_name}
 ```
 
-**5a. Audit**
-
-```
-Skill(skill="gsd-audit-milestone")
-```
-
-After audit completes, detect the result:
-
-```bash
-AUDIT_FILE=".planning/v${milestone_version}-MILESTONE-AUDIT.md"
-AUDIT_STATUS=$(grep "^status:" "${AUDIT_FILE}" 2>/dev/null | head -1 | cut -d: -f2 | tr -d ' ')
-```
-
-**If AUDIT_STATUS is empty** (no audit file or no status field):
-
-Go to handle_blocker: "Audit did not produce results — audit file missing or malformed."
-
-**If `passed`:**
-
-Display:
-```
-Audit ✅ passed — proceeding to complete milestone
-```
-
-Proceed to 5b (no user pause — per CTRL-01).
-
-**If `gaps_found`:**
-
-Read the gaps summary from the audit file. Display:
-```
-⚠ Audit: Gaps Found
-```
-
-Ask user via AskUserQuestion:
-- **question:** "Milestone audit found gaps. How to proceed?"
-- **options:** "Continue anyway — accept gaps" / "Stop — fix gaps manually"
-
-On **"Continue anyway"**: Display `Audit ⏭ Gaps accepted — proceeding to complete milestone` and proceed to 5b.
-
-On **"Stop"**: Go to handle_blocker with "User stopped — audit gaps remain. Run /gsd-audit-milestone to review, then /gsd-complete-milestone when ready."
-
-**If `tech_debt`:**
-
-Read the tech debt summary from the audit file. Display:
-```
-⚠ Audit: Tech Debt Identified
-```
-
-Show the summary, then ask user via AskUserQuestion:
-- **question:** "Milestone audit found tech debt. How to proceed?"
-- **options:** "Continue with tech debt" / "Stop — address debt first"
-
-On **"Continue with tech debt"**: Display `Audit ⏭ Tech debt acknowledged — proceeding to complete milestone` and proceed to 5b.
-
-On **"Stop"**: Go to handle_blocker with "User stopped — tech debt to address. Run /gsd-audit-milestone to review details."
-
 **5b. Complete Milestone**
 
 ```
@@ -697,7 +570,7 @@ Display final completion banner:
 
  Milestone: {milestone_version} — {milestone_name}
  Status: Complete ✅
- Lifecycle: audit ✅ → complete ✅ → cleanup ✅
+ Lifecycle: complete ✅ → cleanup ✅
 
  Ship it! 🚀
 ```
@@ -740,7 +613,7 @@ When any phase operation fails or a blocker is detected, present 3 options via A
 </process>
 
 <success_criteria>
-- [ ] All incomplete phases executed in order (smart discuss → ui-phase → plan → execute → ui-review each)
+- [ ] All incomplete phases executed in order (smart discuss → plan → execute each)
 - [ ] Smart discuss proposes grey area answers in tables, user accepts or overrides per area
 - [ ] Progress banners displayed between phases
 - [ ] Execute-phase invoked with --no-transition (autonomous manages transitions)
@@ -755,8 +628,7 @@ When any phase operation fails or a blocker is detected, present 3 options via A
 - [ ] Blockers handled via user choice (retry / skip / stop)
 - [ ] Final completion or stop summary displayed
 - [ ] After all phases complete, lifecycle step is invoked (not manual suggestion)
-- [ ] Lifecycle transition banner displayed before audit
-- [ ] Audit invoked via Skill(skill="gsd-audit-milestone")
+- [ ] Lifecycle transition banner displayed before complete
 - [ ] Audit result routing: passed → auto-continue, gaps_found → user decides, tech_debt → user decides
 - [ ] Audit technical failure (no file/no status) routes to handle_blocker
 - [ ] Complete-milestone invoked via Skill() with ${milestone_version} arg
@@ -764,12 +636,8 @@ When any phase operation fails or a blocker is detected, present 3 options via A
 - [ ] Final completion banner displayed after lifecycle
 - [ ] Progress bar uses phase number / total milestone phases (not position among incomplete), with fallback display when phase numbers exceed total
 - [ ] Smart discuss documents relationship to discuss-phase with CTRL-03 note
-- [ ] Frontend phases get UI-SPEC generated before planning (step 3a.5) if not already present
-- [ ] Frontend phases get UI review audit after successful execution (step 3d.5) if UI-SPEC exists
-- [ ] UI phase and UI review respect workflow.ui_phase and workflow.ui_review config toggles
-- [ ] UI review is advisory (non-blocking) — phase proceeds to iterate regardless of score
 - [ ] `--only N` restricts execution to exactly one phase
-- [ ] `--only N` skips lifecycle step (audit/complete/cleanup)
+- [ ] `--only N` skips lifecycle step (complete/cleanup)
 - [ ] `--only N` exits cleanly after single phase completes
 - [ ] `--only N` on already-complete phase exits with message
 - [ ] `--only N` handle_blocker resume message uses --only flag

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

@@ -122,10 +122,9 @@ Requirements: {N}/{M} v1 requirements checked off
 - [ ] {REQ-ID}: {description} (Phase {Y})
 ```
 
-MUST present 3 options:
+MUST present 2 options:
 1. **Proceed anyway** — mark milestone complete with known gaps
-2. **Run audit first** — `/gsd-audit-milestone` to assess gap severity
-3. **Abort** — return to development
+2. **Abort** — return to development
 
 If user selects "Proceed anyway": note incomplete requirements in MILESTONES.md under `### Known Gaps` with REQ-IDs and descriptions.
 
@@ -838,7 +837,7 @@ Milestone completion is successful when:
 - [ ] Git tag created (v[X.Y])
 - [ ] Milestone commit made (includes archive files and deletion)
 - [ ] Requirements completion checked against REQUIREMENTS.md traceability table
-- [ ] Incomplete requirements surfaced with proceed/audit/abort options
+- [ ] Incomplete requirements surfaced with proceed/abort options
 - [ ] Known gaps recorded in MILESTONES.md if user proceeded with incomplete requirements
 - [ ] RETROSPECTIVE.md updated with milestone section
 - [ ] Cross-milestone trends updated

package/get-shit-done/workflows/discuss-phase-assumptions.md

@@ -233,23 +233,7 @@ Identify reusable assets, established patterns, integration points, and creative
 Spawn a `gsd-assumptions-analyzer` agent to deeply analyze the codebase for this phase. This
 keeps raw file contents out of the main context window, protecting token budget.
 
-**Resolve calibration tier (if USER-PROFILE.md exists):**
-
-```bash
-PROFILE_PATH="$HOME/.claude/get-shit-done/USER-PROFILE.md"
-```
-
-If file exists at PROFILE_PATH:
-- Priority 1: Read config.json > preferences.vendor_philosophy (project-level override)
-- Priority 2: Read USER-PROFILE.md Vendor Choices/Philosophy rating (global)
-- Priority 3: Default to "standard"
-
-Map to calibration tier:
-- conservative OR thorough-evaluator → full_maturity (more alternatives, detailed evidence)
-- opinionated → minimal_decisive (fewer alternatives, decisive recommendations)
-- pragmatic-fast OR any other value → standard
-
-If no USER-PROFILE.md: calibration_tier = "standard"
+**Calibration tier:** fixed at `standard`.
 
 **Spawn Explore subagent:**
 
@@ -605,7 +589,6 @@ Created: .planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
 
 **Also available:**
 - `/gsd-plan-phase ${PHASE} --skip-research` — plan without research
-- `/gsd-ui-phase ${PHASE}` — generate UI design contract (if frontend work)
 - Review/edit CONTEXT.md before continuing
 
 ---

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

@@ -152,9 +152,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
 
@@ -242,7 +239,7 @@ Write these answers inline before continuing. If a blocking anti-pattern cannot
 </step>
 
 <step name="check_spec">
-Check if a SPEC.md (from `/gsd-spec-phase`) exists for this phase. SPEC.md locks requirements before implementation decisions — if present, this discussion focuses on HOW to implement, not WHAT to build.
+Check if a SPEC.md exists for this phase (produced by earlier spec tooling or written by hand). SPEC.md locks requirements before implementation decisions — if present, this discussion focuses on HOW to implement, not WHAT to build.
 
 ```bash
 ls ${phase_dir}/*-SPEC.md 2>/dev/null | grep -v AI-SPEC | head -1 || true
@@ -261,7 +258,7 @@ ls ${phase_dir}/*-SPEC.md 2>/dev/null | grep -v AI-SPEC | head -1 || true
 
 **If no SPEC.md is found:** Continue to `check_existing` with `spec_loaded = false` (default behavior unchanged).
 
-**Note:** SPEC.md files named `AI-SPEC.md` (from `/gsd-ai-integration-phase`) are excluded — those serve a different purpose.
+**Note:** SPEC.md files named `AI-SPEC.md` (legacy AI design contracts) are excluded — those serve a different purpose.
 </step>
 
 <step name="check_existing">
@@ -396,40 +393,9 @@ Structure the extracted information:
 When escalating, read only the specific `path` returned by `context-history` for the relevant phase. Do not fall back to bulk-reading every prior CONTEXT.md file.
 If `counts.omitted_phases > 0` and the current gray area still feels underdetermined after reviewing the brief, rerun `context-history` with a higher `--limit` before reading many full source files.
 
-**Step 4: Load spike/sketch findings (if they exist)**
-```bash
-# Check for spike/sketch findings skills (project-local)
-SPIKE_FINDINGS=$(ls ./.claude/skills/spike-findings-*/SKILL.md 2>/dev/null | head -1)
-SKETCH_FINDINGS=$(ls ./.claude/skills/sketch-findings-*/SKILL.md 2>/dev/null | head -1)
-
-# Also check for raw spikes/sketches not yet wrapped up
-RAW_SPIKES=$(ls .planning/spikes/MANIFEST.md 2>/dev/null)
-RAW_SKETCHES=$(ls .planning/sketches/MANIFEST.md 2>/dev/null)
-```
-
-If spike/sketch findings skills exist, read their SKILL.md and reference files. Extract:
-- **Validated patterns** — what was proven to work (use these, don't re-explore)
-- **Landmines** — what was proven NOT to work (avoid these)
-- **Constraints** — hard limits discovered (rate limits, API gaps, library limitations)
-- **Design decisions** — winning visual directions, CSS patterns, layout choices
-
-Add to `<prior_decisions>`:
-```
-## From Spike Experiments
-- [Validated pattern or constraint from spike findings]
-
-## From Design Sketches
-- [Design decision or visual direction from sketch findings]
-```
-
-If raw spikes/sketches exist but no findings skill, note in output:
-```
-⚠ Unpackaged spikes/sketches detected — run `/gsd-spike-wrap-up` or `/gsd-sketch-wrap-up` to make findings available to planning agents.
-```
-
 **Usage in subsequent steps:**
-- `analyze_phase`: Skip gray areas already decided in prior phases or validated by spikes/sketches
-- `present_gray_areas`: Annotate options with prior decisions ("You chose X in Phase 5") and spike/sketch findings ("Spike 002 validated this approach")
+- `analyze_phase`: Skip gray areas already decided in prior phases
+- `present_gray_areas`: Annotate options with prior decisions ("You chose X in Phase 5")
 - `discuss_areas`: Pre-fill answers or flag conflicts ("This contradicts Phase 3 — same here or different?")
 
 **If `context-history` fails or returns no usable data:** Fall back to the legacy approach for reliability:
@@ -557,58 +523,18 @@ Analyze the phase to identify gray areas worth discussing. **Use both `prior_dec
 
 **Advisor Mode Detection:**
 
-Check if advisor mode should activate:
-
-1. Check for USER-PROFILE.md:
-   ```bash
-   PROFILE_PATH="$HOME/.claude/get-shit-done/USER-PROFILE.md"
-   ```
-   ADVISOR_MODE = file exists at PROFILE_PATH → true, otherwise → false
+Advisor mode is ON by default. It is disabled only when the `--no-advisor` flag is present in $ARGUMENTS.
 
-2. If ADVISOR_MODE is true, resolve vendor_philosophy calibration tier:
-   - Priority 1: Read config.json > preferences.vendor_philosophy (project-level override)
-   - Priority 2: Read USER-PROFILE.md Vendor Choices/Philosophy rating (global)
-   - Priority 3: Default to "standard" if neither has a value or value is UNSCORED
+1. Set ADVISOR_MODE = true unless `--no-advisor` was passed.
 
-   Map to calibration tier:
-   - conservative OR thorough-evaluator → full_maturity
-   - opinionated → minimal_decisive
-   - pragmatic-fast OR any other value OR empty → standard
+2. Calibration tier is fixed at `standard`.
 
 3. Resolve model for advisor agents:
    ```bash
    ADVISOR_MODEL=$(gsd-remix-sdk query resolve-model gsd-advisor-researcher --raw)
    ```
 
-If ADVISOR_MODE is false, skip all advisor-specific steps — workflow proceeds with existing conversational flow unchanged.
-
-**User Profile Language Detection:**
-
-Check USER-PROFILE.md for communication preferences that indicate a non-technical product owner:
-
-```bash
-PROFILE_CONTENT=$(cat "$HOME/.claude/get-shit-done/USER-PROFILE.md" 2>/dev/null || true)
-```
-
-Set NON_TECHNICAL_OWNER = true if ANY of the following are present in USER-PROFILE.md:
-- `learning_style: guided`
-- The word `jargon` appears in a `frustration_triggers` section
-- `explanation_depth: practical-detailed` (without a technical modifier)
-- `explanation_depth: high-level`
-
-NON_TECHNICAL_OWNER = false if USER-PROFILE.md does not exist or none of the above signals are present.
-
-When NON_TECHNICAL_OWNER is true, reframe gray area labels and descriptions in product-outcome language before presenting them to the user. Preserve the same underlying decision — only change the framing:
-- Technical implementation term → outcome the user will experience
-  - "Token architecture" → "Color system: which approach prevents the dark theme from flashing white on open"
-  - "CSS variable strategy" → "Theme colors: how your brand colors stay consistent in both light and dark mode"
-  - "Component API surface area" → "How the building blocks connect: how tightly coupled should these parts be"
-  - "Caching strategy: SWR vs React Query" → "Loading speed: should screens show saved data right away or wait for fresh data"
-- All decisions stay the same. Only the question language adapts.
-
-This reframing applies to:
-1. Gray area labels and descriptions in `present_gray_areas`
-2. Advisor research rationale rewrites in `advisor_research` synthesis
+If ADVISOR_MODE is false (`--no-advisor`), skip all advisor-specific steps — workflow proceeds with the plain conversational flow unchanged.
 
 **Output your analysis internally, then present to user.**
 
@@ -717,7 +643,7 @@ After user selects gray areas in present_gray_areas, spawn parallel research age
      <gray_area>{area_name}: {area_description from gray area identification}</gray_area>
      <phase_context>{phase_goal and description from ROADMAP.md}</phase_context>
      <project_context>{project name and brief description from PROJECT.md}</project_context>
-     <calibration_tier>{resolved calibration tier: full_maturity | standard | minimal_decisive}</calibration_tier>
+     <calibration_tier>standard</calibration_tier>
 
      Research this gray area and return a structured comparison table with rationale.
      ${AGENT_SKILLS_ADVISOR}",
@@ -732,15 +658,10 @@ After user selects gray areas in present_gray_areas, spawn parallel research age
    For each agent's return:
    a. Parse the markdown comparison table and rationale paragraph
    b. Verify all 5 columns present (Option | Pros | Cons | Complexity | Recommendation) — fill any missing columns rather than showing broken table
-   c. Verify option count matches calibration tier:
-      - full_maturity: 3-5 options acceptable
-      - standard: 2-4 options acceptable
-      - minimal_decisive: 1-2 options acceptable
+   c. Verify option count matches the standard calibration (2-4 options acceptable).
       If agent returned too many, trim least viable. If too few, accept as-is.
    d. Rewrite rationale paragraph to weave in project context and ongoing discussion context that the agent did not have access to
    e. If agent returned only 1 option, convert from table format to direct recommendation: "Standard approach for {area}: {option}. {rationale}"
-   f. **If NON_TECHNICAL_OWNER is true:** After completing steps a–e, apply a plain language rewrite to the rationale paragraph. Replace implementation-level terms with outcome descriptions the user can reason about without technical context. The table option names may also be rewritten in plain language if they are implementation terms — the Recommendation column value and the table structure remain intact. Do not remove detail; translate it. Example: "SWR uses stale-while-revalidate to serve cached responses immediately" → "This approach shows you something right away, then quietly updates in the background — users see data instantly."
-
 4. Store synthesized tables for use in discuss_areas.
 
 **If ADVISOR_MODE is false:** Skip this step entirely — proceed directly from present_gray_areas to discuss_areas.
@@ -766,20 +687,6 @@ Table-first discussion flow — present research-backed comparison tables, then
    - If user picks from table options → record as locked decision for that area
    - If user picks "Other" → receive their input, reflect it back for confirmation, record
 
-   **Thinking partner (conditional):**
-   If `features.thinking_partner` is enabled in config, check the user's answer for tradeoff signals
-   (see `references/thinking-partner.md` for signal list). If tradeoff detected:
-
-   ```
-   I notice competing priorities here — {option_A} optimizes for {goal_A} while {option_B} optimizes for {goal_B}.
-
-   Want me to think through the tradeoffs before we lock this in?
-   [Yes, analyze] / [No, decision made]
-   ```
-
-   If yes: provide 3-5 bullet analysis (what each optimizes/sacrifices, alignment with PROJECT.md goals, recommendation). Then return to normal flow.
-   If no or thinking_partner disabled: continue to next area.
-
 4. **After recording pick, Claude decides whether follow-up questions are needed:**
    - If the pick has ambiguity that would affect downstream planning → ask 1-2 targeted follow-up questions using AskUserQuestion
    - If the pick is clear and self-contained → move to next area
@@ -1184,7 +1091,6 @@ Created: .planning/phases/${PADDED_PHASE}-${SLUG}/${PADDED_PHASE}-CONTEXT.md
 **Also available:**
 - `/gsd-discuss-phase ${PHASE} --chain ${GSD_WS}` — re-run with auto plan+execute after
 - `/gsd-plan-phase ${PHASE} --skip-research ${GSD_WS}` — plan without research
-- `/gsd-ui-phase ${PHASE} ${GSD_WS}` — generate UI design contract before planning (if phase has frontend work)
 - Review/edit CONTEXT.md before continuing
 
 ---

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

@@ -42,10 +42,6 @@ Evaluate `$ARGUMENTS` against these routing rules. Apply the **first matching**
 | Starting a new project, "set up", "initialize" | `/gsd-new-project` | Needs full project initialization |
 | Mapping or analyzing an existing codebase | `/gsd-map-codebase` | Codebase discovery |
 | A bug, error, crash, failure, or something broken | `/gsd-debug` | Needs systematic investigation |
-| Spiking, "test if", "will this work", "experiment", "prove this out", validate feasibility | `/gsd-spike` | Throwaway experiment to validate feasibility |
-| Sketching, "mockup", "what would this look like", "prototype the UI", "design this", explore visual direction | `/gsd-sketch` | Throwaway HTML mockups to explore design |
-| Wrapping up spikes, "package the spikes", "consolidate spike findings" | `/gsd-spike-wrap-up` | Package spike findings into reusable skill |
-| Wrapping up sketches, "package the designs", "consolidate sketch findings" | `/gsd-sketch-wrap-up` | Package sketch findings into reusable skill |
 | Exploring, researching, comparing, or "how does X work" | `/gsd-research-phase` | Domain research before planning |
 | Discussing vision, "how should X look", brainstorming | `/gsd-discuss-phase` | Needs context gathering |
 | A complex task: refactoring, migration, multi-file architecture, system redesign | `/gsd-add-phase` | Needs a full phase with plan/build cycle |
@@ -60,7 +56,7 @@ Evaluate `$ARGUMENTS` against these routing rules. Apply the **first matching**
 | Completing a milestone, shipping, releasing | `/gsd-complete-milestone` | Milestone lifecycle |
 | A specific, actionable, small task (add feature, fix typo, update config) | `/gsd-quick` | Self-contained, single executor |
 
-**Requires `.planning/` directory:** All routes except `/gsd-new-project`, `/gsd-map-codebase`, `/gsd-spike`, `/gsd-sketch`, `/gsd-help`, and `/gsd-join-discord`. If the project doesn't exist and the route requires it, suggest `/gsd-new-project` first.
+**Requires `.planning/` directory:** All routes except `/gsd-new-project`, `/gsd-map-codebase`, and `/gsd-help`. If the project doesn't exist and the route requires it, suggest `/gsd-new-project` first.
 
 **Ambiguity handling:** If the text could reasonably match multiple routes, ask the user via AskUserQuestion with the top 2-3 options. For example: