mindsystem-cc 3.20.0 → 3.22.0

package/mindsystem/templates/roadmap-milestone.md

@@ -7,14 +7,14 @@ Template for reorganizing `ROADMAP.md` after first milestone ships. Collapse com
 
 ## Milestones
 
-- ✅ **v1.0 MVP** - Phases 1-4 (shipped YYYY-MM-DD)
-- 🚧 **v1.1 [Name]** - Phases 5-6 (in progress)
-- 📋 **v2.0 [Name]** - Phases 7-10 (planned)
+- ✅ **MVP** - Phases 1-4 (shipped YYYY-MM-DD)
+- 🚧 **[Name]** - Phases 5-6 (in progress)
+- 📋 **[Name]** - Phases 7-10 (planned)
 
 ## Phases
 
 <details>
-<summary>✅ v1.0 MVP (Phases 1-4) - SHIPPED YYYY-MM-DD</summary>
+<summary>✅ MVP (Phases 1-4) - SHIPPED YYYY-MM-DD</summary>
 
 ### Phase 1: [Name]
 **Goal**: [What this phase delivers]
@@ -25,13 +25,13 @@ Plans:
 - [x] 01-02: [Brief description]
 - [x] 01-03: [Brief description]
 
-[... remaining v1.0 phases ...]
+[... remaining phases ...]
 
 </details>
 
-### 🚧 v1.1 [Name] (In Progress)
+### 🚧 [Name] (In Progress)
 
-**Milestone Goal:** [What v1.1 delivers]
+**Milestone Goal:** [What this milestone delivers]
 
 #### Phase 5: [Name]
 **Goal**: [What this phase delivers]
@@ -42,21 +42,21 @@ Plans:
 - [ ] 05-01: [Brief description]
 - [ ] 05-02: [Brief description]
 
-[... remaining v1.1 phases ...]
+[... remaining phases ...]
 
-### 📋 v2.0 [Name] (Planned)
+### 📋 [Name] (Planned)
 
-**Milestone Goal:** [What v2.0 delivers]
+**Milestone Goal:** [What this milestone delivers]
 
-[... v2.0 phases ...]
+[... phases ...]
 
 ## Progress
 
 | Phase | Milestone | Plans Complete | Status | Completed |
 |-------|-----------|----------------|--------|-----------|
-| 1. Foundation | v1.0 | 3/3 | Complete | YYYY-MM-DD |
-| 2. Features | v1.0 | 2/2 | Complete | YYYY-MM-DD |
-| 5. Security | v1.1 | 0/2 | Not started | - |
+| 1. Foundation | MVP | 3/3 | Complete | YYYY-MM-DD |
+| 2. Features | MVP | 2/2 | Complete | YYYY-MM-DD |
+| 5. Security | Security & Polish | 0/2 | Not started | - |
 ```
 
 **Notes:**

package/mindsystem/templates/roadmap.md

@@ -2,7 +2,7 @@
 
 Template for `.planning/ROADMAP.md`.
 
-## Initial Roadmap (v1.0 Greenfield)
+## Initial Roadmap (Greenfield)
 
 ```markdown
 # Roadmap: [Project Name]
@@ -34,7 +34,7 @@ Decimal phases appear between their surrounding integers in numeric order.
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
   3. [Observable behavior from user perspective]
-**Discuss**: Unlikely (clear requirements)
+**Discuss**: Unlikely (mechanical setup, zero design decisions)
 **Design**: Unlikely (backend only)
 **Research**: Unlikely (established patterns)
 **Plans**: [Number of plans, e.g., "3 plans" or "TBD"]
@@ -51,7 +51,7 @@ Plans:
 **Success Criteria** (what must be TRUE):
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
-**Discuss**: Likely (ambiguous user flow)
+**Discuss**: Likely (assumes email/password only, unclear if social login needed, session duration unspecified)
 **Discuss topics**: [What to clarify]
 **Design**: Likely (significant new UI)
 **Design focus**: [What to design]
@@ -81,7 +81,8 @@ Plans:
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
   3. [Observable behavior from user perspective]
-**Discuss**: Unlikely (established patterns)
+**Discuss**: Likely (assumes standard REST patterns, error handling strategy unspecified, rate limiting approach unclear)
+**Discuss topics**: [Integration scope, error UX, retry behavior]
 **Design**: Unlikely (API only)
 **Research**: Likely (external API)
 **Research topics**: [What needs investigating]
@@ -98,7 +99,8 @@ Plans:
 **Success Criteria** (what must be TRUE):
   1. [Observable behavior from user perspective]
   2. [Observable behavior from user perspective]
-**Discuss**: Unlikely (clear requirements)
+**Discuss**: Likely (assumes priority ordering of requirements, unclear if batch processing needed, edge case handling unspecified)
+**Discuss topics**: [Priority rules, batch vs individual, error recovery]
 **Design**: Unlikely (backend only)
 **Research**: Unlikely (internal patterns)
 **Plans**: [Number of plans]
@@ -120,7 +122,7 @@ Phases execute in numeric order: 2 → 2.1 → 2.2 → 3 → 3.1 → 4
 ```
 
 <guidelines>
-**Initial planning (v1.0):**
+**Initial planning:**
 - Phase count derived from actual work (not a target number)
 - Each phase delivers something coherent
 - Phases can have 1+ plans (split by orchestrator judgment — multiple subsystems, context budget, vertical slices)
@@ -133,11 +135,11 @@ Phases execute in numeric order: 2 → 2.1 → 2.2 → 3 → 3.1 → 4
 - 2-5 observable behaviors per phase (from user's perspective)
 - Cross-checked against requirements during roadmap creation
 - Flow downstream to `## Must-Haves` in plan-phase
-- Verified by verify-phase after execution
+- Verified by ms-verifier agent after execution
 - Format: "User can [action]" or "[Thing] works/exists"
 
 **Pre-work indicators** (all use Likely/Unlikely with parenthetical reason):
-- `Discuss` - Vision unknowns: ambiguous requirements, UX decisions, novel features
+- `Discuss` - Default Likely. Surfaces Claude's assumptions before planning. Unlikely only for fully mechanical zero-decision work (version bump, rename-only refactor, config-only change, pure deletion/cleanup). When Likely, rationale enumerates 2-4 phase-specific assumptions or open questions.
 - `Design` - Visual unknowns: significant new UI, novel interactions, multi-screen flows
 - `Research` - Technical unknowns: external APIs, new libraries, architectural decisions
 - Include topic/focus fields only when Likely

package/mindsystem/templates/state.md

@@ -115,8 +115,8 @@ STATE.md is the project's short-term memory spanning all phases and sessions.
 - adhoc: After adhoc work completed
   - Add entry to "Recent Adhoc Work" section
   - Keep last 5 entries (older entries remain in .planning/adhoc/)
-- Any state-changing command: Update Last Command field
-  - Format: `ms:{command} {args} | YYYY-MM-DD HH:MM`
+- Any state-changing command: `ms-tools set-last-command "ms:{command} {args}"`
+  - Appends real local timestamp via `datetime.now()`
   - Enables status line to show context without running /ms:progress
 
 </lifecycle>

package/mindsystem/templates/verification-report.md

@@ -10,15 +10,16 @@ Template for `.planning/phases/XX-name/{phase}-VERIFICATION.md` — phase goal v
 ---
 phase: XX-name
 verified: YYYY-MM-DDTHH:MM:SSZ
-status: passed | gaps_found | human_needed
+status: passed | gaps_found
 score: N/M must-haves verified
+uncertain: N  # UNCERTAIN truths + NEEDS HUMAN requirements
 ---
 
 # Phase {X}: {Name} Verification Report
 
 **Phase Goal:** {goal from ROADMAP.md}
 **Verified:** {timestamp}
-**Status:** {passed | gaps_found | human_needed}
+**Status:** {passed | gaps_found}
 
 ## Goal Achievement
 
@@ -72,23 +73,6 @@ score: N/M must-haves verified
 
 **Anti-patterns:** {N} found ({blockers} blockers, {warnings} warnings)
 
-## Human Verification Required
-
-{If no human verification needed:}
-None — all verifiable items checked programmatically.
-
-{If human verification needed:}
-
-### 1. {Test Name}
-**Test:** {What to do}
-**Expected:** {What should happen}
-**Why human:** {Why can't verify programmatically}
-
-### 2. {Test Name}
-**Test:** {What to do}
-**Expected:** {What should happen}
-**Why human:** {Why can't verify programmatically}
-
 ## Gaps Summary
 
 {If no gaps:}
@@ -149,7 +133,6 @@ None — all verifiable items checked programmatically.
 **Verification approach:** Goal-backward (derived from phase goal)
 **Must-haves source:** {PLAN.md ## Must-Haves section | derived from ROADMAP.md goal}
 **Automated checks:** {N} passed, {M} failed
-**Human checks required:** {N}
 **Total verification time:** {duration}
 
 ---
@@ -164,7 +147,6 @@ None — all verifiable items checked programmatically.
 **Status values:**
 - `passed` — All must-haves verified, no blockers
 - `gaps_found` — One or more critical gaps found
-- `human_needed` — Automated checks pass but human verification required
 
 **Evidence types:**
 - For EXISTS: "File at path, exports X"
@@ -257,10 +239,6 @@ score: 2/5 must-haves verified
 
 **Anti-patterns:** 3 found (2 blockers, 1 warning)
 
-## Human Verification Required
-
-None needed until automated gaps are fixed.
-
 ## Gaps Summary
 
 ### Critical Gaps (Block Progress)
@@ -313,7 +291,6 @@ None needed until automated gaps are fixed.
 **Verification approach:** Goal-backward (derived from phase goal)
 **Must-haves source:** 03-01-PLAN.md ## Must-Haves section
 **Automated checks:** 2 passed, 8 failed
-**Human checks required:** 0 (blocked by automated failures)
 **Total verification time:** 2 min
 
 ---

package/mindsystem/workflows/adhoc.md

@@ -381,7 +381,7 @@ Generate patch file from the adhoc commit:
 ```bash
 patch_file=".planning/adhoc/${timestamp}-${slug}.patch"
 
-~/.claude/mindsystem/scripts/generate-adhoc-patch.sh "$commit_hash" "$patch_file"
+ms-tools generate-adhoc-patch "$commit_hash" "$patch_file"
 ```
 
 If patch generated (file exists and non-empty):

package/mindsystem/workflows/complete-milestone.md

@@ -1,6 +1,6 @@
 <purpose>
 
-Mark a shipped version (v1.0, v1.1, v2.0) as complete. This creates a historical record in MILESTONES.md, performs full PROJECT.md evolution review, archives ROADMAP.md and REQUIREMENTS.md, and tags the release in git.
+Mark a shipped milestone as complete. This creates a historical record in MILESTONES.md, performs full PROJECT.md evolution review, and archives ROADMAP.md and REQUIREMENTS.md.
 
 </purpose>
 
@@ -20,9 +20,9 @@ Mark a shipped version (v1.0, v1.1, v2.0) as complete. This creates a historical
 
 When a milestone completes, this workflow:
 
-1. Creates `.planning/milestones/v[X.Y]/` directory for all archive files
-2. Extracts full milestone details to `.planning/milestones/v[X.Y]/ROADMAP.md`
-3. Archives requirements to `.planning/milestones/v[X.Y]/REQUIREMENTS.md`
+1. Creates `.planning/milestones/{slug}/` directory for all archive files
+2. Extracts full milestone details to `.planning/milestones/{slug}/ROADMAP.md`
+3. Archives requirements to `.planning/milestones/{slug}/REQUIREMENTS.md`
 4. Archives milestone files via script (audit, context, research — whichever exist)
 5. Consolidates phase summaries, deletes artifacts, moves phase dirs via script
 6. Deletes REQUIREMENTS.md (fresh one created for next milestone)
@@ -68,7 +68,7 @@ cat .planning/config.json 2>/dev/null
 Run the stats script to get readiness status and git statistics:
 
 ```bash
-~/.claude/mindsystem/scripts/gather-milestone-stats.sh $PHASE_START $PHASE_END
+ms-tools gather-milestone-stats $PHASE_START $PHASE_END
 ```
 
 The script outputs:
@@ -133,7 +133,7 @@ If exists, prepend new entry (reverse chronological order).
 Use template from `templates/milestone.md`:
 
 ```markdown
-## v[Version] [Name] (Shipped: YYYY-MM-DD)
+## [Name] (Shipped: YYYY-MM-DD)
 
 **Delivered:** [One sentence from user]
 
@@ -185,7 +185,7 @@ cat .planning/phases/*-*/*-SUMMARY.md
 
    **Validated section:**
    - All requirements shipped in this milestone → Add to Validated
-   - Format: `- ✓ [Requirement] — v[X.Y]`
+   - Format: `- ✓ [Requirement] — [Name]`
 
    **Out of Scope audit:**
    - Review each item — is the reasoning still valid?
@@ -218,10 +218,10 @@ Make all edits inline. Update "Last updated" footer:
 
 ```markdown
 ---
-*Last updated: [date] after v[X.Y] milestone*
+*Last updated: [date] after [Name] milestone*
 ```
 
-**Example full evolution (v1.0 → v1.1 prep):**
+**Example full evolution (MVP → Security & Polish prep):**
 
 Before:
 
@@ -249,7 +249,7 @@ Currently using Miro or physical whiteboards.
 - Video chat — use external tools
 ```
 
-After v1.0:
+After MVP:
 
 ```markdown
 ## What This Is
@@ -267,9 +267,9 @@ Currently using Miro but frustrated by complexity and latency.
 
 ## Validated
 
-- ✓ Canvas drawing tools — v1.0
-- ✓ Real-time sync < 500ms — v1.0 (achieved 200ms avg)
-- ✓ User authentication — v1.0
+- ✓ Canvas drawing tools — MVP
+- ✓ Real-time sync < 500ms — MVP (achieved 200ms avg)
+- ✓ User authentication — MVP
 
 ## Out of Scope
 
@@ -279,7 +279,7 @@ Currently using Miro but frustrated by complexity and latency.
 
 ## Technical Context
 
-Shipped v1.0 with 2,400 LOC TypeScript.
+Shipped MVP with 2,400 LOC TypeScript.
 Tech stack: Next.js, Supabase, Canvas API.
 Initial user testing showed demand for shape tools.
 ```
@@ -305,9 +305,9 @@ Extract completed milestone details and create archive file.
 
 1. Create milestone directory and archive file:
    ```bash
-   mkdir -p .planning/milestones/v[X.Y]
+   mkdir -p .planning/milestones/{slug}
    ```
-   Archive file path: `.planning/milestones/v[X.Y]/ROADMAP.md`
+   Archive file path: `.planning/milestones/{slug}/ROADMAP.md`
 
 2. Read `~/.claude/mindsystem/templates/milestone-archive.md` template
 
@@ -332,7 +332,7 @@ Extract completed milestone details and create archive file.
    - {{DECISIONS_FROM_PROJECT}} — Key decisions from PROJECT.md
    - {{ISSUES_RESOLVED_DURING_MILESTONE}} — From summaries
 
-6. Write filled template to `.planning/milestones/v[X.Y]/ROADMAP.md`
+6. Write filled template to `.planning/milestones/{slug}/ROADMAP.md`
 
 7. Delete ROADMAP.md (fresh one created for next milestone):
    ```bash
@@ -341,17 +341,17 @@ Extract completed milestone details and create archive file.
 
 8. Verify archive exists:
    ```bash
-   ls .planning/milestones/v[X.Y]/ROADMAP.md
+   ls .planning/milestones/{slug}/ROADMAP.md
    ```
 
 9. Confirm roadmap archive complete:
 
    ```
-   ✅ v[X.Y] roadmap archived to milestones/v[X.Y]/ROADMAP.md
+   ✅ Roadmap archived to milestones/{slug}/ROADMAP.md
    ✅ ROADMAP.md deleted (fresh one for next milestone)
    ```
 
-**Note:** Phase directories are moved to `milestones/v[X.Y]/phases/` by the archive_and_cleanup_phases step. After milestone completion, `.planning/phases/` contains only the next milestone's work. Phase numbering continues (v1.0 phases 1-4, v1.1 phases 5-8, etc.).
+**Note:** Phase directories are moved to `milestones/{slug}/phases/` by the archive_and_cleanup_phases step. After milestone completion, `.planning/phases/` contains only the next milestone's work. Phase numbering continues (MVP phases 1-4, next milestone phases 5-8, etc.).
 
 </step>
 
@@ -366,7 +366,7 @@ Archive requirements and prepare for fresh requirements in next milestone.
    cat .planning/REQUIREMENTS.md
    ```
 
-2. Create archive file: `.planning/milestones/v[X.Y]/REQUIREMENTS.md`
+2. Create archive file: `.planning/milestones/{slug}/REQUIREMENTS.md`
 
 3. Transform requirements for archive:
    - Mark all v1 requirements as `[x]` complete
@@ -379,12 +379,12 @@ Archive requirements and prepare for fresh requirements in next milestone.
 
 4. Write archive file with header:
    ```markdown
-   # Requirements Archive: v[X.Y] [Milestone Name]
+   # Requirements Archive: [Milestone Name]
 
    **Archived:** [DATE]
    **Status:** ✅ SHIPPED
 
-   This is the archived requirements specification for v[X.Y].
+   This is the archived requirements specification for [Milestone Name].
    For current requirements, see `.planning/REQUIREMENTS.md` (created for next milestone).
 
    ---
@@ -400,7 +400,7 @@ Archive requirements and prepare for fresh requirements in next milestone.
    **Dropped:** [list any requirements removed and why]
 
    ---
-   *Archived: [DATE] as part of v[X.Y] milestone completion*
+   *Archived: [DATE] as part of [Milestone Name] milestone completion*
    ```
 
 5. Delete original REQUIREMENTS.md:
@@ -410,7 +410,7 @@ Archive requirements and prepare for fresh requirements in next milestone.
 
 6. Confirm:
    ```
-   ✅ Requirements archived to milestones/v[X.Y]/REQUIREMENTS.md
+   ✅ Requirements archived to milestones/{slug}/REQUIREMENTS.md
    ✅ REQUIREMENTS.md deleted (fresh one needed for next milestone)
    ```
 
@@ -423,7 +423,7 @@ Archive requirements and prepare for fresh requirements in next milestone.
 Archive optional milestone files (audit, context, research) to the milestone directory:
 
 ```bash
-~/.claude/mindsystem/scripts/archive-milestone-files.sh v[X.Y]
+ms-tools archive-milestone-files {slug}
 ```
 
 The script moves whichever files exist and reports what was archived. Files that don't exist are skipped silently.
@@ -435,22 +435,22 @@ The script moves whichever files exist and reports what was archived. Files that
 Consolidate phase summaries, delete raw artifacts, and move phase directories to the milestone archive. This runs after all steps that read summaries (extract_accomplishments, evolve_project_full_review) and after archive_milestone creates the milestone directory.
 
 ```bash
-~/.claude/mindsystem/scripts/archive-milestone-phases.sh $PHASE_START $PHASE_END v[X.Y]
+ms-tools archive-milestone-phases $PHASE_START $PHASE_END {slug}
 ```
 
 Verify archive:
 
 ```bash
-ls .planning/milestones/v[X.Y]/PHASE-SUMMARIES.md
-ls .planning/milestones/v[X.Y]/phases/
+ls .planning/milestones/{slug}/PHASE-SUMMARIES.md
+ls .planning/milestones/{slug}/phases/
 ```
 
 Present:
 
 ```
-✅ Phase summaries consolidated to milestones/v[X.Y]/PHASE-SUMMARIES.md
+✅ Phase summaries consolidated to milestones/{slug}/PHASE-SUMMARIES.md
 ✅ Raw artifacts deleted from phase directories
-✅ Phase directories moved to milestones/v[X.Y]/phases/
+✅ Phase directories moved to milestones/{slug}/phases/
 ✅ .planning/phases/ clean for next milestone
 ```
 
@@ -479,7 +479,7 @@ See: .planning/PROJECT.md (updated [today])
 Phase: [Next phase] of [Total] ([Phase name])
 Plan: Not started
 Status: Ready to plan
-Last activity: [today] — v[X.Y] milestone complete
+Last activity: [today] — [Name] milestone complete
 
 Progress: [updated progress bar]
 ```
@@ -492,45 +492,13 @@ Progress: [updated progress bar]
 
 </step>
 
-<step name="git_tag">
-
-Create git tag for milestone:
-
-```bash
-git tag -a v[X.Y] -m "$(cat <<'EOF'
-v[X.Y] [Name]
-
-Delivered: [One sentence]
-
-Key accomplishments:
-- [Item 1]
-- [Item 2]
-- [Item 3]
-
-See .planning/MILESTONES.md for full details.
-EOF
-)"
-```
-
-Confirm: "Tagged: v[X.Y]"
-
-Ask: "Push tag to remote? (y/n)"
-
-If yes:
-
-```bash
-git push origin v[X.Y]
-```
-
-</step>
-
 <step name="git_commit_milestone">
 
 Commit milestone completion including archive files and deletions.
 
 ```bash
 # Stage archive directory (covers ROADMAP, REQUIREMENTS, AUDIT, CONTEXT, research)
-git add .planning/milestones/v[X.Y]/
+git add .planning/milestones/{slug}/
 
 # Stage updated files
 git add .planning/MILESTONES.md
@@ -542,9 +510,9 @@ git add -u .planning/
 
 # Commit with descriptive message
 git commit -m "$(cat <<'EOF'
-chore: complete v[X.Y] milestone
+chore: complete [Name] milestone
 
-Archived to milestones/v[X.Y]/:
+Archived to milestones/{slug}/:
 - ROADMAP.md
 - REQUIREMENTS.md
 - PHASE-SUMMARIES.md (consolidated from phase directories)
@@ -567,32 +535,29 @@ Updated:
 - MILESTONES.md (new entry)
 - PROJECT.md (requirements → Validated)
 - STATE.md (reset for next milestone)
-
-Tagged: v[X.Y]
 EOF
 )"
 ```
 
-Confirm: "Committed: chore: complete v[X.Y] milestone"
+Confirm: "Committed: chore: complete [Name] milestone"
 
 </step>
 
 <step name="offer_next">
 
 ```
-✅ Milestone v[X.Y] [Name] complete
+✅ Milestone [Name] complete
 
 Shipped:
 - [N] phases ([M] plans, [P] tasks)
 - [One sentence of what shipped]
 
-Archived to milestones/v[X.Y]/:
+Archived to milestones/{slug}/:
 - ROADMAP.md
 - REQUIREMENTS.md
 - research/ (if existed)
 
 Summary: .planning/MILESTONES.md
-Tag: v[X.Y]
 
 ---
 
@@ -624,8 +589,8 @@ Milestone completion is successful when (ordered by skip risk):
 - [ ] All shipped requirements moved to Validated in PROJECT.md
 - [ ] Key Decisions updated with outcomes
 - [ ] MILESTONES.md entry created with stats and accomplishments
-- [ ] Roadmap archive created (milestones/v[X.Y]/ROADMAP.md)
-- [ ] Requirements archive created (milestones/v[X.Y]/REQUIREMENTS.md)
+- [ ] Roadmap archive created (milestones/{slug}/ROADMAP.md)
+- [ ] Requirements archive created (milestones/{slug}/REQUIREMENTS.md)
 - [ ] REQUIREMENTS.md deleted (fresh for next milestone)
 - [ ] STATE.md updated with fresh project reference