mindsystem-cc 3.10.0 → 3.11.0

package/mindsystem/workflows/create-milestone.md

@@ -1,243 +0,0 @@
-<purpose>
-Start a new milestone cycle by updating PROJECT.md with new goals.
-
-This is the brownfield equivalent of new-project. The project exists and has history.
-This workflow gathers "what's next" and updates PROJECT.md, then routes to the
-requirements → roadmap cycle.
-</purpose>
-
-<required_reading>
-**Read these files NOW:**
-
-1. ~/.claude/mindsystem/references/questioning.md
-2. ~/.claude/mindsystem/templates/project.md
-3. `.planning/PROJECT.md`
-4. `.planning/MILESTONES.md` (if exists)
-5. `.planning/STATE.md`
-</required_reading>
-
-<process>
-
-<step name="load_context">
-Load project context:
-
-```bash
-cat .planning/PROJECT.md
-cat .planning/MILESTONES.md 2>/dev/null || echo "No milestones file yet"
-cat .planning/STATE.md
-cat .planning/config.json 2>/dev/null
-```
-
-Extract:
-- What shipped previously (from MILESTONES.md)
-- Current Validated requirements (from PROJECT.md)
-- Pending todos and blockers (from STATE.md)
-
-**Calculate next milestone version:**
-- Parse last version from MILESTONES.md
-- If v1.0 → suggest v1.1 (minor) or v2.0 (major)
-- If v1.3 → suggest v1.4 or v2.0
-
-**Calculate previous milestone for context:**
-- If v1.1 starting → previous is v1.0
-- Store previous version number for use in gather_goals step
-- Context files (DECISIONS.md, AUDIT.md) will be loaded on-demand based on user's choice
-
-**Why only the last milestone?** Older decisions that remain important should already be in PROJECT.md or visible in the codebase. Older untested assumptions that weren't addressed are intentionally skipped. Loading all previous milestones would bloat context for diminishing returns.
-</step>
-
-<step name="gather_goals">
-Present what shipped:
-```
-Last milestone: v[X.Y] [Name]
-Key accomplishments:
-- [From MILESTONES.md]
-
-Validated so far:
-- [From PROJECT.md Validated section]
-
-Pending todos:
-- [From STATE.md if any]
-```
-
-**Decision gate:**
-
-Use AskUserQuestion:
-```
-header: "New Milestone"
-question: "How do you want to start v[X.Y]?"
-options:
-  - "I know what to build" — proceed to goal gathering
-  - "Help me figure it out" — enter discovery mode with previous context
-  - "Show previous decisions first" — view DECISIONS.md and AUDIT.md, then decide
-```
-
-**If "I know what to build":**
-- Ask directly: "What do you want to build in the next milestone?"
-- Wait for response
-- Proceed to confirm_goals
-
-**If "Show previous decisions first":**
-- Using the previous version from load_context (e.g., "1.0"):
-  - Check for and read `.planning/milestones/v1.0-DECISIONS.md` if exists
-  - Check for and read `.planning/milestones/v1.0-MILESTONE-AUDIT.md` if exists
-- Present relevant context from these files
-- Then present decision gate again (without this option)
-
-**If "Help me figure it out" (Discovery Mode):**
-- Using the previous version from load_context:
-  - Check for and read `.planning/milestones/v{VERSION}-DECISIONS.md` if exists
-  - Check for and read `.planning/milestones/v{VERSION}-MILESTONE-AUDIT.md` if exists
-
-Surface untested assumptions (from AUDIT.md):
-```
-📋 Untested from v[previous]:
-- Error state displays (couldn't mock API errors)
-- Empty state handling (couldn't clear test data)
-- [etc. from assumptions section]
-
-These were skipped during UAT. Address them in this milestone?
-```
-
-Run AskUserQuestion-based feature discovery:
-```
-header: "What to build"
-question: "What do you want to add, improve, or fix?"
-options:
-  - "Address untested assumptions" — add test infrastructure or fix gaps
-  - "New features" — build something new
-  - "Improvements" — enhance existing features
-  - "Bug fixes" — fix known issues
-  - "Let me describe" — freeform input
-```
-
-Continue with follow-up questions:
-- Probe specific features mentioned
-- Ask about priorities
-- Surface constraints or dependencies
-- Clarify scope boundaries
-
-Follow questioning.md patterns for AskUserQuestion-based discovery.
-
-Continue until you have clear milestone goals.
-</step>
-
-<step name="confirm_goals">
-Present gathered goals:
-
-```
-Milestone: v[X.Y] [Name]
-
-Goal: [One sentence focus]
-
-Target features:
-- [Feature 1]
-- [Feature 2]
-- [Feature 3]
-
-Ready to update PROJECT.md? (yes / adjust)
-```
-
-If "adjust": return to gather_goals.
-</step>
-
-<step name="update_project">
-Update `.planning/PROJECT.md`:
-
-**Add Current Milestone section** (after Core Value, before Requirements):
-
-```markdown
-## Current Milestone: v[X.Y] [Name]
-
-**Goal:** [One sentence describing milestone focus]
-
-**Target features:**
-- [Feature 1]
-- [Feature 2]
-- [Feature 3]
-```
-
-**Update Active requirements:**
-- Add new milestone goals to Active section
-- Keep existing Active items that weren't addressed
-- Don't remove anything from Validated
-
-**Update footer:**
-```markdown
----
-*Last updated: [date] after v[X.Y] milestone start*
-```
-</step>
-
-<step name="update_state">
-Update `.planning/STATE.md`:
-
-```markdown
-## Current Position
-
-Phase: Not started (run /ms:create-roadmap)
-Plan: —
-Status: Defining requirements
-Last activity: [today] — Milestone v[X.Y] started
-
-Progress: ░░░░░░░░░░ 0%
-```
-
-Keep Accumulated Context (decisions, blockers) from previous milestone.
-</step>
-
-
-<step name="git_commit">
-```bash
-git add .planning/PROJECT.md .planning/STATE.md
-git commit -m "$(cat <<'EOF'
-docs: start milestone v[X.Y] [Name]
-
-Goal: [One sentence]
-Target features: [count] features
-EOF
-)"
-```
-</step>
-
-<step name="offer_next">
-```
-Milestone v[X.Y] [Name] initialized.
-
-PROJECT.md updated with:
-- Current Milestone section
-- Target features in Active requirements
-
----
-
-## ▶ Next Up
-
-**Define Requirements** — scope v[X.Y] features into REQUIREMENTS.md
-
-`/ms:define-requirements`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Or research first:**
-- `/ms:research-project` — investigate ecosystem before scoping
-
-**Full flow:**
-1. `/ms:define-requirements` — create REQUIREMENTS.md
-2. `/ms:create-roadmap` — create ROADMAP.md with phases
-3. `/ms:plan-phase [N]` — start execution
-
----
-```
-</step>
-
-</process>
-
-<success_criteria>
-- PROJECT.md updated with Current Milestone section
-- Active requirements reflect new milestone goals
-- STATE.md reset for new milestone (keeps accumulated context)
-- Git commit made
-- User routed to define-requirements (or research-project)
-</success_criteria>

package/mindsystem/workflows/discuss-milestone.md

@@ -1,310 +0,0 @@
-<purpose>
-Help the user figure out what they want to build in the next milestone through collaborative thinking.
-
-You're a thinking partner helping them crystallize their vision for what's next. Features first — everything else (scope, phases) derives from what they want to build.
-</purpose>
-
-<process>
-
-<step name="check_state" priority="first">
-Load project state:
-
-```bash
-cat .planning/STATE.md
-cat .planning/ROADMAP.md
-```
-
-**If no active milestone (expected state after completing previous):**
-Continue to milestone_context.
-
-**If active milestone exists:**
-
-```
-Current milestone in progress: v[X.Y] [Name]
-Phases [N]-[M], [P]% complete
-
-Did you want to:
-1. Complete current milestone first (/ms:complete-milestone)
-2. Add phases to current milestone (/ms:add-phase)
-3. Continue anyway - discuss next milestone scope
-
-```
-
-Wait for user response. If "Continue anyway", proceed to milestone_context.
-</step>
-
-<step name="milestone_context">
-Present context from previous milestone:
-
-```
-Last completed: v[X.Y] [Name] (shipped [DATE])
-Key accomplishments:
-- [From MILESTONES.md or STATE.md]
-
-Total phases delivered: [N]
-Next phase number: [N+1]
-```
-
-Continue to intake_gate.
-</step>
-
-<step name="intake_gate">
-**CRITICAL: ALL questions use AskUserQuestion. Never ask inline text questions.**
-
-The primary question is: **What do you want to build/add/fix?**
-
-Everything else (scope, priority, constraints) is secondary and derived from features.
-
-Check for inputs:
-- Pending todos from STATE.md (potential features)
-- Untested assumptions from MILESTONE-AUDIT.md (potential infrastructure work)
-- Known gaps or pain points from usage
-- User's ideas for what's next
-
-```bash
-# Check for assumptions from previous milestone audit
-ASSUMPTIONS=$(cat .planning/v*-MILESTONE-AUDIT.md 2>/dev/null | grep -c "assumptions:" || echo 0)
-```
-
-**1. Open with context-aware options:**
-
-Use AskUserQuestion:
-- header: "Next"
-- question: "What do you want to add, improve, or fix in this milestone?"
-- options:
-  - [Pending todos from STATE.md if any]
-  - [If ASSUMPTIONS > 0: "Address untested assumptions ({N} items)"]
-  - "New features"
-  - "Improvements to existing"
-  - "Bug fixes"
-  - "Let me describe"
-
-**If user selects "Address untested assumptions":**
-
-Present the assumptions list from MILESTONE-AUDIT.md:
-
-```
-## Untested Assumptions from v{X.Y}
-
-These tests were skipped because required states couldn't be mocked:
-
-| Phase | Test | Expected Behavior | Reason |
-|-------|------|-------------------|--------|
-| 04-comments | Error state display | Shows error message when API fails | Can't mock API errors |
-| 04-comments | Empty state | Shows placeholder when no comments | Can't clear test data |
-| 05-auth | Session timeout | Redirects to login after 30min | Can't manipulate time |
-
-To verify these, you'd need:
-- Error response mocking (API interceptor or mock server)
-- State reset capabilities (clear data for empty states)
-- Time manipulation (for timeout testing)
-```
-
-Then use AskUserQuestion:
-- header: "Assumptions"
-- question: "Which assumptions do you want to address?"
-- options:
-  - "All of them — plan test infrastructure"
-  - "Just error states"
-  - "Just empty states"
-  - "None for now — they're low risk"
-
-Continue to feature gathering based on selection.
-
-**2. Follow the thread (don't switch topics):**
-
-Based on their response, dig deeper into THAT topic before moving on:
-
-| They said | Follow-up |
-|-----------|-----------|
-| Named a feature | "What should [feature] do? What's the core behavior?" |
-| "New features" | "What capability is missing? What would users do with it?" |
-| "Improvements" | "Which existing feature needs improvement? What's the friction?" |
-| "Bug fixes" | "What's broken? How does it manifest?" |
-
-**3. Probe for edges:**
-
-Once you understand the feature, probe:
-- "What's the simplest version of this that would be useful?"
-- "What would make this feel complete vs MVP?"
-- "Any constraints I should know about?"
-
-**4. Explore features:**
-
-Based on their response, use AskUserQuestion:
-
-If they named specific features:
-- header: "Feature Details"
-- question: "Tell me more about [feature] - what should it do?"
-- options: [Contextual options based on feature type + "Let me describe it"]
-
-If they described a general direction:
-- header: "Breaking It Down"
-- question: "That could involve [A], [B], [C] - which matter most?"
-- options: [Specific sub-features + "All of them" + "Something else"]
-
-If they're not sure:
-- header: "Starting Points"
-- question: "What's been frustrating or missing?"
-- options: [Pending todos from STATE.md + pain point categories + "Let me think about it"]
-
-**5. Prioritize:**
-
-Use AskUserQuestion:
-- header: "Priority"
-- question: "Which of these matters most?"
-- options: [Features they mentioned + "All equally important" + "Let me prioritize"]
-
-After gathering features, synthesize:
-
-```
-Based on what you described:
-
-**Features:**
-- [Feature 1]: [brief description]
-- [Feature 2]: [brief description]
-- [Feature 3]: [brief description]
-
-**Estimated scope:** [N] phases
-**Theme suggestion:** v[X.Y] [Name]
-```
-
-**6. Decision gate:**
-
-Use AskUserQuestion:
-- header: "Ready?"
-- question: "Ready to create the milestone, or explore more?"
-- options (ALL THREE REQUIRED):
-  - "Create milestone" - Proceed to /ms:new-milestone
-  - "Ask more questions" - Help me think through this more
-  - "Let me add context" - I have more to share
-
-If "Ask more questions" → return to step 2 with new probes.
-If "Let me add context" → receive input → return to step 2.
-Loop until "Create milestone" selected.
-</step>
-
-<step name="write_context">
-Write milestone context to file for handoff.
-
-**File:** `.planning/MILESTONE-CONTEXT.md`
-
-Use template from ~/.claude/mindsystem/templates/milestone-context.md
-
-**Calculate next phase number:**
-
-```bash
-# Find highest existing phase number
-LAST_PHASE=$(ls -d .planning/phases/[0-9]*-* 2>/dev/null | sort -V | tail -1 | grep -oE '[0-9]+' | head -1)
-
-if [ -n "$LAST_PHASE" ]; then
-  NEXT_PHASE=$((10#$LAST_PHASE + 1))
-else
-  NEXT_PHASE=1
-fi
-echo "Next phase number: $NEXT_PHASE"
-```
-
-Populate with:
-- Features identified during discussion
-- Suggested milestone name and theme
-- Estimated phase count
-- How features map to phases
-- Any constraints or scope boundaries mentioned
-- **Starting phase number** (calculated above)
-
-```bash
-# Write the context file
-cat > .planning/MILESTONE-CONTEXT.md << 'EOF'
-# Milestone Context
-
-**Generated:** [today's date]
-**Status:** Ready for /ms:new-milestone
-
-<features>
-## Features to Build
-
-- **[Feature 1]**: [description]
-- **[Feature 2]**: [description]
-- **[Feature 3]**: [description]
-
-</features>
-
-<scope>
-## Scope
-
-**Suggested name:** v[X.Y] [Theme Name]
-**Estimated phases:** [N]
-**Focus:** [One sentence theme/focus]
-
-</scope>
-
-<starting_phase>
-## Starting Phase
-
-Next phase number: $NEXT_PHASE (calculated from existing phases)
-
-</starting_phase>
-
-<constraints>
-## Constraints
-
-- [Any constraints mentioned]
-
-</constraints>
-
-<notes>
-## Additional Context
-
-[Anything else from discussion]
-
-</notes>
-
----
-
-*This file is temporary. It will be deleted after /ms:new-milestone creates the milestone.*
-EOF
-```
-</step>
-
-<step name="handoff">
-Present summary and hand off to create-milestone:
-
-```
-Milestone scope defined:
-
-**Features:**
-- [Feature 1]: [description]
-- [Feature 2]: [description]
-- [Feature 3]: [description]
-
-**Suggested milestone:** v[X.Y] [Theme Name]
-
-Context saved to `.planning/MILESTONE-CONTEXT.md`
-
----
-
-## ▶ Next Up
-
-**Create Milestone v[X.Y]** — [Theme Name]
-
-`/ms:new-milestone`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-```
-</step>
-
-</process>
-
-<success_criteria>
-
-- Project state loaded (STATE.md, MILESTONES.md)
-- Previous milestone context presented
-- **Features identified** - What to build/add/fix (the substance)
-- Features explored with clarifying questions
-- Scope synthesized from features (not asked abstractly)
-- **MILESTONE-CONTEXT.md created** with features and scope
-- Context handed off to /ms:new-milestone
-</success_criteria>