mindsystem-cc 3.22.1 → 4.0.0

package/commands/ms/check-todos.md

@@ -1,240 +0,0 @@
----
-name: ms:check-todos
-description: List pending todos and select one to work on
-argument-hint: [subsystem or priority filter]
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - AskUserQuestion
----
-
-<objective>
-List all pending todos, allow selection, load full context for the selected todo, and route to appropriate action.
-
-Enables reviewing captured ideas and deciding what to work on next.
-</objective>
-
-<context>
-@.planning/STATE.md
-@.planning/ROADMAP.md
-</context>
-
-<process>
-
-<step name="check_exist">
-```bash
-TODO_COUNT=$(ls .planning/todos/pending/*.md 2>/dev/null | wc -l | tr -d ' ')
-echo "Pending todos: $TODO_COUNT"
-```
-
-If count is 0:
-```
-No pending todos.
-
-Todos are captured during work sessions with /ms:add-todo.
-
----
-
-Would you like to:
-
-1. Continue with current phase (/ms:progress)
-2. Add a todo now (/ms:add-todo)
-```
-
-Exit.
-</step>
-
-<step name="parse_filter">
-Support multi-field filtering:
-- `/ms:check-todos` → show all
-- `/ms:check-todos p1` → filter to priority:p1 only (matches `p[1-3]`)
-- `/ms:check-todos api` → filter to subsystem or area matching "api"
-</step>
-
-<step name="list_todos">
-```bash
-for file in .planning/todos/pending/*.md; do
-  created=$(grep "^created:" "$file" | cut -d' ' -f2)
-  title=$(grep "^title:" "$file" | cut -d':' -f2- | xargs)
-  priority=$(grep "^priority:" "$file" | cut -d' ' -f2)
-  subsystem=$(grep "^subsystem:" "$file" | cut -d' ' -f2)
-  area=$(grep "^area:" "$file" | cut -d' ' -f2)
-  echo "${priority:-p3}|${subsystem:-${area:-general}}|$created|$title|$file"
-done | sort
-```
-
-Old-format todos (missing priority/subsystem) default to `p3`/`general`.
-
-Apply filter if specified:
-- Priority filter (`p1`-`p3`): match priority field
-- Subsystem/area filter: match either subsystem or area field
-
-Priority-grouped display with sequential numbering across groups. Omit empty groups. Use subsystem label (fall back to area, then "general"):
-
-```
-Pending Todos (N):
-
-### p1 — Urgent
-  1. auth: Fix token refresh race condition (2d ago)
-  2. api: Handle rate limit 429 responses (1d ago)
-
-### p2 — Important
-  3. ui: Add loading states to dashboard (5h ago)
-
-### p3 — Ideas
-  4. general: Explore caching strategy (3d ago)
-
----
-
-Reply with a number to view details, or:
-- `/ms:check-todos [subsystem]` to filter by subsystem
-- `/ms:check-todos p1` to filter by priority
-- `q` to exit
-```
-
-Format age as relative time.
-</step>
-
-<step name="handle_selection">
-Wait for user to reply with a number.
-
-If valid: load selected todo, proceed.
-If invalid: "Invalid selection. Reply with a number (1-[N]) or `q` to exit."
-</step>
-
-<step name="load_context">
-Read the todo file completely. Display:
-
-```
-## [title]
-
-**Subsystem:** [subsystem] | **Priority:** [priority] | **Source:** [source]
-**Phase Origin:** [phase_origin]
-**Created:** [date] ([relative time] ago)
-**Tags:** [tags or "None"]
-**Files:** [list or "None"]
-
-### Problem
-[problem section content]
-
-### Solution
-[solution section content]
-```
-
-Gracefully omit missing fields for old-format todos.
-
-If `files` field has entries, read and briefly summarize each.
-</step>
-
-<step name="check_roadmap">
-```bash
-ls .planning/ROADMAP.md 2>/dev/null && echo "Roadmap exists"
-```
-
-If roadmap exists:
-1. Check if todo's subsystem or area matches an upcoming phase
-2. Check if todo's files overlap with a phase's scope
-3. Check if todo's tags match phase keywords
-4. Note any match for action options
-</step>
-
-<step name="offer_actions">
-**If todo maps to a roadmap phase:**
-
-Use AskUserQuestion:
-- header: "Action"
-- question: "This todo relates to Phase [N]: [name]. What would you like to do?"
-- options:
-  - "Work on it now" — move to done, start working
-  - "Add to phase plan" — include when planning Phase [N]
-  - "Brainstorm approach" — think through before deciding
-  - "Put it back" — return to list
-
-**If no roadmap match:**
-
-Use AskUserQuestion:
-- header: "Action"
-- question: "What would you like to do with this todo?"
-- options:
-  - "Work on it now" — move to done, start working
-  - "Create a phase" — /ms:add-phase with this scope
-  - "Brainstorm approach" — think through before deciding
-  - "Put it back" — return to list
-</step>
-
-<step name="execute_action">
-**Work on it now:**
-```bash
-mv ".planning/todos/pending/[filename]" ".planning/todos/done/"
-```
-Update STATE.md todo count. Present problem/solution context. Begin work or ask how to proceed.
-
-**Add to phase plan:**
-Note todo reference in phase planning notes. Keep in pending. Return to list or exit.
-
-**Create a phase:**
-Display: `/ms:add-phase [description from todo]`
-Keep in pending. User runs command in fresh context.
-
-**Brainstorm approach:**
-Keep in pending. Start discussion about problem and approaches.
-
-**Put it back:**
-Return to list_todos step.
-</step>
-
-<step name="update_state">
-After any action that changes todo count:
-
-```bash
-ls .planning/todos/pending/*.md 2>/dev/null | wc -l
-```
-
-Update STATE.md "### Pending Todos" section if exists.
-</step>
-
-<step name="git_commit">
-If todo was moved to done/, commit the change:
-
-```bash
-git add .planning/todos/done/[filename]
-git rm --cached .planning/todos/pending/[filename] 2>/dev/null || true
-[ -f .planning/STATE.md ] && git add .planning/STATE.md
-git commit -m "$(cat <<'EOF'
-docs: start work on todo - [title]
-
-Moved to done/, beginning implementation.
-EOF
-)"
-```
-
-Confirm: "Committed: docs: start work on todo - [title]"
-</step>
-
-</process>
-
-<output>
-- Moved todo to `.planning/todos/done/` (if "Work on it now")
-- Updated `.planning/STATE.md` (if todo count changed)
-</output>
-
-<anti_patterns>
-- Don't delete todos — move to done/ when work begins
-- Don't start work without moving to done/ first
-- Don't create plans from this command — route to /ms:plan-phase or /ms:add-phase
-</anti_patterns>
-
-<success_criteria>
-- [ ] All pending todos listed grouped by priority (p1/p2/p3)
-- [ ] Subsystem label displayed (with area/general fallback for old todos)
-- [ ] Priority or subsystem filter applied if specified
-- [ ] Selected todo's full context loaded (subsystem, priority, source, phase, tags)
-- [ ] Old-format todos handled gracefully (missing fields omitted)
-- [ ] Roadmap context checked for phase match (subsystem, area, files, tags)
-- [ ] Appropriate actions offered
-- [ ] Selected action executed
-- [ ] STATE.md updated if todo count changed
-- [ ] Changes committed to git (if todo moved to done/)
-</success_criteria>

package/commands/ms/plan-milestone-gaps.md

@@ -1,288 +0,0 @@
----
-name: ms:plan-milestone-gaps
-description: Create phases to close all gaps identified by milestone audit
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - Grep
-  - AskUserQuestion
----
-
-<objective>
-Create all phases necessary to close gaps identified by `/ms:audit-milestone`.
-
-Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase.
-
-One command creates all fix phases — no manual `/ms:add-phase` per gap.
-</objective>
-
-<execution_context>
-@~/.claude/mindsystem/references/principles.md
-@~/.claude/mindsystem/workflows/plan-phase.md
-</execution_context>
-
-<context>
-**Audit results:**
-@.planning/MILESTONE-AUDIT.md
-
-**Original intent (for prioritization):**
-@.planning/PROJECT.md
-@.planning/REQUIREMENTS.md
-
-**Current state:**
-@.planning/ROADMAP.md
-@.planning/STATE.md
-</context>
-
-<process>
-
-## 1. Load Audit Results
-
-```bash
-cat .planning/MILESTONE-AUDIT.md
-```
-
-Parse YAML frontmatter to extract structured gaps:
-- `gaps.requirements` — unsatisfied requirements
-- `gaps.integration` — missing cross-phase connections
-- `gaps.flows` — broken E2E flows
-
-If no audit file exists or has no gaps, error:
-```
-No audit gaps found. Run `/ms:audit-milestone` first.
-```
-
-## 2. Prioritize Gaps
-
-Group gaps by priority from REQUIREMENTS.md:
-
-| Priority | Action |
-|----------|--------|
-| `must` | Create phase, blocks milestone |
-| `should` | Create phase, recommended |
-| `nice` | Ask user: include or defer? |
-
-For integration/flow gaps, infer priority from affected requirements.
-
-## 3. Group Gaps into Phases
-
-Cluster related gaps into logical phases:
-
-**Grouping rules:**
-- Same affected phase → combine into one fix phase
-- Same subsystem (auth, API, UI) → combine
-- Dependency order (fix stubs before wiring)
-- Keep phases focused: 2-4 tasks each
-
-**Example grouping:**
-```
-Gap: DASH-01 unsatisfied (Dashboard doesn't fetch)
-Gap: Integration Phase 1→3 (Auth not passed to API calls)
-Gap: Flow "View dashboard" broken at data fetch
-
-→ Phase 6: "Wire Dashboard to API"
-  - Add fetch to Dashboard.tsx
-  - Include auth header in fetch
-  - Handle response, update state
-  - Render user data
-```
-
-## 4. Determine Phase Numbers
-
-Find highest existing phase:
-```bash
-ls -d .planning/phases/*/ | sort -V | tail -1
-```
-
-New phases continue from there:
-- If Phase 5 is highest, gaps become Phase 6, 7, 8...
-
-## 5. Present Gap Closure Plan
-
-```markdown
-## Gap Closure Plan
-
-**Milestone:** {name}
-**Gaps to close:** {N} requirements, {M} integration, {K} flows
-
-### Proposed Phases
-
-**Phase {N}: {Name}**
-Closes:
-- {REQ-ID}: {description}
-- Integration: {from} → {to}
-Tasks: {count}
-
-**Phase {N+1}: {Name}**
-Closes:
-- {REQ-ID}: {description}
-- Flow: {flow name}
-Tasks: {count}
-
-{If nice-to-have gaps exist:}
-
-### Deferred (nice-to-have)
-
-These gaps are optional. Include them?
-- {gap description}
-- {gap description}
-
----
-
-Create these {X} phases? (yes / adjust / defer all optional)
-```
-
-Wait for user confirmation.
-
-## 6. Update ROADMAP.md
-
-Add new phases to current milestone:
-
-```markdown
-### Phase {N}: {Name}
-**Goal:** {derived from gaps being closed}
-**Requirements:** {REQ-IDs being satisfied}
-**Gap Closure:** Closes gaps from audit
-
-### Phase {N+1}: {Name}
-...
-```
-
-## 7. Create Phase Directories
-
-```bash
-mkdir -p ".planning/phases/{NN}-{name}"
-```
-
-## 8. Commit Roadmap Update
-
-```bash
-git add .planning/ROADMAP.md
-git commit -m "docs(roadmap): add gap closure phases {N}-{M}"
-```
-
-## 9. Offer Next Steps
-
-```markdown
-## ✓ Gap Closure Phases Created
-
-**Phases added:** {N} - {M}
-**Gaps addressed:** {count} requirements, {count} integration, {count} flows
-
----
-
-## ▶ Next Up
-
-`/ms:plan-phase {N}` — plan first gap closure phase
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/ms:execute-phase {N}` — if plans already exist
-- `cat .planning/ROADMAP.md` — see updated roadmap
-
----
-
-**After all gap phases complete:**
-
-`/ms:audit-milestone` — re-audit to verify gaps closed
-`/ms:complete-milestone` — archive when audit passes
-```
-
-## 10. Update Last Command
-
-```bash
-ms-tools set-last-command "ms:plan-milestone-gaps"
-```
-
-</process>
-
-<gap_to_phase_mapping>
-
-## How Gaps Become Tasks
-
-**Requirement gap → Tasks:**
-```yaml
-gap:
-  id: DASH-01
-  description: "User sees their data"
-  reason: "Dashboard exists but doesn't fetch from API"
-  missing:
-    - "useEffect with fetch to /api/user/data"
-    - "State for user data"
-    - "Render user data in JSX"
-
-becomes:
-
-phase: "Wire Dashboard Data"
-tasks:
-  - name: "Add data fetching"
-    files: [src/components/Dashboard.tsx]
-    action: "Add useEffect that fetches /api/user/data on mount"
-
-  - name: "Add state management"
-    files: [src/components/Dashboard.tsx]
-    action: "Add useState for userData, loading, error states"
-
-  - name: "Render user data"
-    files: [src/components/Dashboard.tsx]
-    action: "Replace placeholder with userData.map rendering"
-```
-
-**Integration gap → Tasks:**
-```yaml
-gap:
-  from_phase: 1
-  to_phase: 3
-  connection: "Auth token → API calls"
-  reason: "Dashboard API calls don't include auth header"
-  missing:
-    - "Auth header in fetch calls"
-    - "Token refresh on 401"
-
-becomes:
-
-phase: "Add Auth to Dashboard API Calls"
-tasks:
-  - name: "Add auth header to fetches"
-    files: [src/components/Dashboard.tsx, src/lib/api.ts]
-    action: "Include Authorization header with token in all API calls"
-
-  - name: "Handle 401 responses"
-    files: [src/lib/api.ts]
-    action: "Add interceptor to refresh token or redirect to login on 401"
-```
-
-**Flow gap → Tasks:**
-```yaml
-gap:
-  name: "User views dashboard after login"
-  broken_at: "Dashboard data load"
-  reason: "No fetch call"
-  missing:
-    - "Fetch user data on mount"
-    - "Display loading state"
-    - "Render user data"
-
-becomes:
-
-# Usually same phase as requirement/integration gap
-# Flow gaps often overlap with other gap types
-```
-
-</gap_to_phase_mapping>
-
-<success_criteria>
-- [ ] MILESTONE-AUDIT.md loaded and gaps parsed
-- [ ] Gaps prioritized (must/should/nice)
-- [ ] Gaps grouped into logical phases
-- [ ] User confirmed phase plan
-- [ ] ROADMAP.md updated with new phases
-- [ ] Phase directories created
-- [ ] Changes committed
-- [ ] User knows to run `/ms:plan-phase` next
-</success_criteria>