moveros 4.0.8 → 4.1.0

package/src/workflows/refactor-plan.md

@@ -1,135 +1,135 @@
----
-description: Safely updates the roadmap without deleting history. System-triggered or manual.
----
-
-# Refactor Plan (V4)
-
-**Trigger:** User runs `/refactor-plan` OR system suggests it after strategy pivot.
-**Role:** Surgical Plan Editor.
-**Task:** Update plan.md based on strategy change WITHOUT deleting history.
-**Risk Tier:** MEDIUM
-
-In V4, this is typically triggered by the system (after `/pivot-strategy` or when plan.md drifts from Strategy.md), but can also be run manually.
-
----
-
-## 0. PRE-FLIGHT
-
-Global Rules are pre-loaded as CLAUDE.md / GEMINI.md. Output `[Rules Loaded - DATE]`.
-
-LOAD (Light + Strategy — Active_Context is the cache):
-1. Active_Context.md (has Active Patterns S5.5 for plan drift patterns, Strategic Verdict S1)
-2. Strategy.md (FULL — needed for direct comparison: plan.md Architecture vs Strategy.md targets)
-3. Current plan.md (READ ONLY first)
-4. project_state.md (for changelog)
-NOTE: Strategy.md is the exception — refactor-plan compares plan.md against Strategy.md changes directly. Active Patterns S5.5 provides drift pattern history. If Active_Context is stale (>2 days), flag it and suggest /analyse-day first.
-
-CONSTRAINTS:
-- SURGICAL EDITING. Never rewrite the entire file.
-- Never delete completed tasks [x] or Execution Log entries.
-- Mark obsolete tasks as [-] (Skipped), not deleted.
-- Append-only for new tasks and changelog.
-- Windows: no && in commands.
-
----
-
-## 0.5. PRE-READ & PROJECT IDENTIFICATION
-
-**Read plan.md NOW.** Output: "Current state: [X] completed tasks, [Y] open tasks, [Z] phases. Plan targets: [goal from plan.md]."
-
-If multiple projects have plan.md files in `01_Projects/`: "Which project are we refactoring? [list them]." Do not proceed until user confirms.
-
----
-
-## 1. ANALYZE & UPDATE ARCHITECTURE
-
-Target: `plan.md` > `## ARCHITECTURE`
-If stack/rules changed (compare plan.md Architecture vs project_brief.md Stack): update this section ONLY. If they match, skip Step 1.
-
----
-
-## 2. UPDATE ROADMAP (The Pivot)
-
-Target: `plan.md` > `## ROADMAP`
-
-1. Find steps made obsolete. Mark as `[-]` (e.g., `[-] Step 2: Setup Supabase`).
-2. Insert NEW steps with `[ ]` into appropriate phase.
-3. If new Phase needed: insert between existing phases or at end.
-4. Never delete `[x]` completed tasks.
-5. Never delete Execution Log entries.
-
----
-
-## 3. LOG THE CHANGE
-
-Target: `project_state.md` > `## CHANGELOG`
-Append: `* [YYYY-MM-DD] STRATEGY PIVOT - {Summary of changes}`
-
----
-
-## 4. SELF-VERIFICATION (CISC)
-
-Before outputting, self-check:
-1. No completed tasks deleted? (90%+ accuracy required)
-2. No execution log entries removed?
-3. Obsolete tasks marked [-] not deleted?
-4. New tasks properly inserted?
-5. All edits grounded in Strategy.md changes — not invented?
-
-If any check < 90% confident: flag it explicitly before writing.
-
----
-
-## 5. CONFIRMATION
-
-Output a diff-style summary:
-- "Skipped [X] obsolete tasks."
-- "Added [Y] new tasks."
-- "Updated architecture section."
-- "Logged change to project_state.md."
-
----
-
-## 6. ANSWER GATING
-
-Do not suggest handoff until:
-- User has reviewed the diff-style summary (Section 5).
-- User has confirmed no completed tasks were lost.
-
-If pending: "Please confirm the diff above is accurate before I finalize. Any tasks missing or incorrectly marked?"
-
----
-
-## 7. PROACTIVE SUGGESTIONS
-
-Based on observations during this workflow:
-1. [If Auto_Learnings shows plan.md has drifted before] - Confidence: [X] - "This is a recurring drift. Consider aligning plan.md with Strategy.md after every `/pivot-strategy`."
-2. [If multiple phases are now obsolete] - Confidence: [X] - "A large portion of the roadmap changed. Run `/overview` to verify project direction is still coherent."
-3. [If project_state.md CHANGELOG is getting long] - Confidence: [X] - "Many pivots logged. Consider an architecture review."
-
-"Want me to address any of these?"
-
----
-
-## 8. SELF-IMPROVEMENT
-
-If user corrected AI during this workflow:
-1. Acknowledge: "I made a mistake."
-2. Identify the rule violated.
-3. Append to Auto_Learnings.md:
-   `* [YYYY-MM-DD] CORRECTION: [Description]. Source: User correction. Confidence: 3.`
-4. If same correction seen 3x+, escalate confidence to 5.
-
----
-
-## HANDOFF
-
-Sources used: Auto_Learnings.md, Active_Context.md, Strategy.md, plan.md, project_state.md
-Confidence range: [X-Y across outputs]
-
-**Next:** "Plan updated. Continue executing, or run `/overview` to see the new state."
-
-Key rules still active:
-- All claims must be grounded in Strategy.md and plan.md content
-- Confidence < 3 = ask, don't assert
-- Append-only: never delete from plan.md or project_state.md
+---
+description: Safely updates the roadmap without deleting history. System-triggered or manual.
+---
+
+# Refactor Plan (V4)
+
+**Trigger:** User runs `/refactor-plan` OR system suggests it after strategy pivot.
+**Role:** Surgical Plan Editor.
+**Task:** Update plan.md based on strategy change WITHOUT deleting history.
+**Risk Tier:** MEDIUM
+
+In V4, this is typically triggered by the system (after `/pivot-strategy` or when plan.md drifts from Strategy.md), but can also be run manually.
+
+---
+
+## 0. PRE-FLIGHT
+
+Global Rules are pre-loaded as CLAUDE.md / GEMINI.md. Output `[Rules Loaded - DATE]`.
+
+LOAD (Light + Strategy — Active_Context is the cache):
+1. Active_Context.md (has Active Patterns S5.5 for plan drift patterns, Strategic Verdict S1)
+2. Strategy.md (FULL — needed for direct comparison: plan.md Architecture vs Strategy.md targets)
+3. Current plan.md (READ ONLY first)
+4. project_state.md (for changelog)
+NOTE: Strategy.md is the exception — refactor-plan compares plan.md against Strategy.md changes directly. Active Patterns S5.5 provides drift pattern history. If Active_Context is stale (>2 days), flag it and suggest /analyse-day first.
+
+CONSTRAINTS:
+- SURGICAL EDITING. Never rewrite the entire file.
+- Never delete completed tasks [x] or Execution Log entries.
+- Mark obsolete tasks as [-] (Skipped), not deleted.
+- Append-only for new tasks and changelog.
+- Windows: no && in commands.
+
+---
+
+## 0.5. PRE-READ & PROJECT IDENTIFICATION
+
+**Read plan.md NOW.** Output: "Current state: [X] completed tasks, [Y] open tasks, [Z] phases. Plan targets: [goal from plan.md]."
+
+If multiple projects have plan.md files in `01_Projects/`: "Which project are we refactoring? [list them]." Do not proceed until user confirms.
+
+---
+
+## 1. ANALYZE & UPDATE ARCHITECTURE
+
+Target: `plan.md` > `## ARCHITECTURE`
+If stack/rules changed (compare plan.md Architecture vs project_brief.md Stack): update this section ONLY. If they match, skip Step 1.
+
+---
+
+## 2. UPDATE ROADMAP (The Pivot)
+
+Target: `plan.md` > `## ROADMAP`
+
+1. Find steps made obsolete. Mark as `[-]` (e.g., `[-] Step 2: Setup Supabase`).
+2. Insert NEW steps with `[ ]` into appropriate phase.
+3. If new Phase needed: insert between existing phases or at end.
+4. Never delete `[x]` completed tasks.
+5. Never delete Execution Log entries.
+
+---
+
+## 3. LOG THE CHANGE
+
+Target: `project_state.md` > `## CHANGELOG`
+Append: `* [YYYY-MM-DD] STRATEGY PIVOT - {Summary of changes}`
+
+---
+
+## 4. SELF-VERIFICATION (CISC)
+
+Before outputting, self-check:
+1. No completed tasks deleted? (90%+ accuracy required)
+2. No execution log entries removed?
+3. Obsolete tasks marked [-] not deleted?
+4. New tasks properly inserted?
+5. All edits grounded in Strategy.md changes — not invented?
+
+If any check < 90% confident: flag it explicitly before writing.
+
+---
+
+## 5. CONFIRMATION
+
+Output a diff-style summary:
+- "Skipped [X] obsolete tasks."
+- "Added [Y] new tasks."
+- "Updated architecture section."
+- "Logged change to project_state.md."
+
+---
+
+## 6. ANSWER GATING
+
+Do not suggest handoff until:
+- User has reviewed the diff-style summary (Section 5).
+- User has confirmed no completed tasks were lost.
+
+If pending: "Please confirm the diff above is accurate before I finalize. Any tasks missing or incorrectly marked?"
+
+---
+
+## 7. PROACTIVE SUGGESTIONS
+
+Based on observations during this workflow:
+1. [If Auto_Learnings shows plan.md has drifted before] - Confidence: [X] - "This is a recurring drift. Consider aligning plan.md with Strategy.md after every `/pivot-strategy`."
+2. [If multiple phases are now obsolete] - Confidence: [X] - "A large portion of the roadmap changed. Run `/overview` to verify project direction is still coherent."
+3. [If project_state.md CHANGELOG is getting long] - Confidence: [X] - "Many pivots logged. Consider an architecture review."
+
+"Want me to address any of these?"
+
+---
+
+## 8. SELF-IMPROVEMENT
+
+If user corrected AI during this workflow:
+1. Acknowledge: "I made a mistake."
+2. Identify the rule violated.
+3. Append to Auto_Learnings.md:
+   `* [YYYY-MM-DD] CORRECTION: [Description]. Source: User correction. Confidence: 3.`
+4. If same correction seen 3x+, escalate confidence to 5.
+
+---
+
+## HANDOFF
+
+Sources used: Auto_Learnings.md, Active_Context.md, Strategy.md, plan.md, project_state.md
+Confidence range: [X-Y across outputs]
+
+**Next:** "Plan updated. Continue executing, or run `/overview` to see the new state."
+
+Key rules still active:
+- All claims must be grounded in Strategy.md and plan.md content
+- Confidence < 3 = ask, don't assert
+- Append-only: never delete from plan.md or project_state.md