mindforge-cc 9.0.0 → 10.0.1

package/.agent/workflows/mindforge-pause-work.md

@@ -1,176 +0,0 @@
-<purpose>
-Create structured `.planning/HANDOFF.json` and `.continue-here.md` handoff files to preserve complete work state across sessions. The JSON provides machine-readable state for `/mindforge-resume-work`; the markdown provides human-readable context.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-<step name="detect">
-Find current phase directory from most recently modified files:
-
-```bash
-# Find most recent phase directory with work
-ls -lt .planning/phases/*/PLAN.md 2>/dev/null | head -1 | grep -oP 'phases/\K[^/]+'
-```
-
-If no active phase detected, ask user which phase they're pausing work on.
-</step>
-
-<step name="gather">
-**Collect complete state for handoff:**
-
-1. **Current position**: Which phase, which plan, which task
-2. **Work completed**: What got done this session
-3. **Work remaining**: What's left in current plan/phase
-4. **Decisions made**: Key decisions and rationale
-5. **Blockers/issues**: Anything stuck
-6. **Human actions pending**: Things that need manual intervention (MCP setup, API keys, approvals, manual testing)
-7. **Background processes**: Any running servers/watchers that were part of the workflow
-8. **Files modified**: What's changed but not committed
-
-Ask user for clarifications if needed via conversational questions.
-
-**Also inspect SUMMARY.md files for false completions:**
-```bash
-# Check for placeholder content in existing summaries
-grep -l "To be filled\|placeholder\|TBD" .planning/phases/*/*.md 2>/dev/null
-```
-Report any summaries with placeholder content as incomplete items.
-</step>
-
-<step name="write_structured">
-**Write structured handoff to `.planning/HANDOFF.json`:**
-
-```bash
-timestamp=$(node ".agent/bin/mindforge-tools.cjs" current-timestamp full --raw)
-```
-
-```json
-{
-  "version": "1.0",
-  "timestamp": "{timestamp}",
-  "phase": "{phase_number}",
-  "phase_name": "{phase_name}",
-  "phase_dir": "{phase_dir}",
-  "plan": {current_plan_number},
-  "task": {current_task_number},
-  "total_tasks": {total_task_count},
-  "status": "paused",
-  "completed_tasks": [
-    {"id": 1, "name": "{task_name}", "status": "done", "commit": "{short_hash}"},
-    {"id": 2, "name": "{task_name}", "status": "done", "commit": "{short_hash}"},
-    {"id": 3, "name": "{task_name}", "status": "in_progress", "progress": "{what_done}"}
-  ],
-  "remaining_tasks": [
-    {"id": 4, "name": "{task_name}", "status": "not_started"},
-    {"id": 5, "name": "{task_name}", "status": "not_started"}
-  ],
-  "blockers": [
-    {"description": "{blocker}", "type": "technical|human_action|external", "workaround": "{if any}"}
-  ],
-  "human_actions_pending": [
-    {"action": "{what needs to be done}", "context": "{why}", "blocking": true}
-  ],
-  "decisions": [
-    {"decision": "{what}", "rationale": "{why}", "phase": "{phase_number}"}
-  ],
-  "uncommitted_files": [],
-  "next_action": "{specific first action when resuming}",
-  "context_notes": "{mental state, approach, what you were thinking}"
-}
-```
-</step>
-
-<step name="write">
-**Write handoff to `.planning/phases/XX-name/.continue-here.md`:**
-
-```markdown
----
-phase: XX-name
-task: 3
-total_tasks: 7
-status: in_progress
-last_updated: [timestamp from current-timestamp]
----
-
-<current_state>
-[Where exactly are we? Immediate context]
-</current_state>
-
-<completed_work>
-
-- Task 1: [name] - Done
-- Task 2: [name] - Done
-- Task 3: [name] - In progress, [what's done]
-</completed_work>
-
-<remaining_work>
-
-- Task 3: [what's left]
-- Task 4: Not started
-- Task 5: Not started
-</remaining_work>
-
-<decisions_made>
-
-- Decided to use [X] because [reason]
-- Chose [approach] over [alternative] because [reason]
-</decisions_made>
-
-<blockers>
-- [Blocker 1]: [status/workaround]
-</blockers>
-
-<context>
-[Mental state, what were you thinking, the plan]
-</context>
-
-<next_action>
-Start with: [specific first action when resuming]
-</next_action>
-```
-
-Be specific enough for a fresh the agent to understand immediately.
-
-Use `current-timestamp` for last_updated field. You can use init todos (which provides timestamps) or call directly:
-```bash
-timestamp=$(node ".agent/bin/mindforge-tools.cjs" current-timestamp full --raw)
-```
-</step>
-
-<step name="commit">
-```bash
-node ".agent/bin/mindforge-tools.cjs" commit "wip: [phase-name] paused at task [X]/[Y]" --files .planning/phases/*/.continue-here.md .planning/HANDOFF.json
-```
-</step>
-
-<step name="confirm">
-```
-✓ Handoff created:
-  - .planning/HANDOFF.json (structured, machine-readable)
-  - .planning/phases/[XX-name]/.continue-here.md (human-readable)
-
-Current state:
-
-- Phase: [XX-name]
-- Task: [X] of [Y]
-- Status: [in_progress/blocked]
-- Blockers: [count] ({human_actions_pending count} need human action)
-- Committed as WIP
-
-To resume: /mindforge-resume-work
-
-```
-</step>
-
-</process>
-
-<success_criteria>
-- [ ] .continue-here.md created in correct phase directory
-- [ ] All sections filled with specific content
-- [ ] Committed as WIP
-- [ ] User knows location and how to resume
-</success_criteria>

package/.agent/workflows/mindforge-plan-milestone-gaps.md

@@ -1,273 +0,0 @@
-<purpose>
-Create all phases necessary to close gaps identified by `/mindforge-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 `/mindforge-add-phase` per gap.
-</purpose>
-
-<required_reading>
-Read all files referenced by the invoking prompt's execution_context before starting.
-</required_reading>
-
-<process>
-
-## 1. Load Audit Results
-
-```bash
-# Find the most recent audit file
-ls -t .planning/v*-MILESTONE-AUDIT.md 2>/dev/null | head -1
-```
-
-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 `/mindforge-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
-# Get sorted phase list, extract last one
-HIGHEST=$(node ".agent/bin/mindforge-tools.cjs" phases list --pick directories[-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:** {version}
-**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. Update REQUIREMENTS.md Traceability Table (REQUIRED)
-
-For each REQ-ID assigned to a gap closure phase:
-- Update the Phase column to reflect the new gap closure phase
-- Reset Status to `Pending`
-
-Reset checked-off requirements the audit found unsatisfied:
-- Change `[x]` → `[ ]` for any requirement marked unsatisfied in the audit
-- Update coverage count at top of REQUIREMENTS.md
-
-```bash
-# Verify traceability table reflects gap closure assignments
-grep -c "Pending" .planning/REQUIREMENTS.md
-```
-
-## 8. Create Phase Directories
-
-```bash
-mkdir -p ".planning/phases/{NN}-{name}"
-```
-
-## 9. Commit Roadmap and Requirements Update
-
-```bash
-node ".agent/bin/mindforge-tools.cjs" commit "docs(roadmap): add gap closure phases {N}-{M}" --files .planning/ROADMAP.md .planning/REQUIREMENTS.md
-```
-
-## 10. Offer Next Steps
-
-```markdown
-## ✓ Gap Closure Phases Created
-
-**Phases added:** {N} - {M}
-**Gaps addressed:** {count} requirements, {count} integration, {count} flows
-
----
-
-## ▶ Next Up
-
-**Plan first gap closure phase**
-
-`/mindforge-plan-phase {N}`
-
-<sub>`/clear` first → fresh context window</sub>
-
----
-
-**Also available:**
-- `/mindforge-execute-phase {N}` — if plans already exist
-- `cat .planning/ROADMAP.md` — see updated roadmap
-
----
-
-**After all gap phases complete:**
-
-`/mindforge-audit-milestone` — re-audit to verify gaps closed
-`/mindforge-complete-milestone {version}` — archive when audit passes
-```
-
-</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
-- [ ] REQUIREMENTS.md traceability table updated with gap closure phase assignments
-- [ ] Unsatisfied requirement checkboxes reset (`[x]` → `[ ]`)
-- [ ] Coverage count updated in REQUIREMENTS.md
-- [ ] Phase directories created
-- [ ] Changes committed (includes REQUIREMENTS.md)
-- [ ] User knows to run `/mindforge-plan-phase` next
-</success_criteria>