moveros 4.0.8 → 4.1.0

package/src/workflows/init-plan.md

@@ -1,16 +1,16 @@
----
-description: DEPRECATED in V4.6. Plan generation merged into /ignite. Kept for backwards compatibility.
----
-
-# Plan Generator — DEPRECATED
-
-**This workflow has been merged into `/ignite`.**
-
-As of V4.6, `/ignite` generates both the Project Brief AND the Plan (plan.md) in a single workflow. There is no need to run `/init-plan` separately.
-
-**If the user runs `/init-plan`:**
-1. Check if `project_brief.md` exists in the current project folder.
-2. If yes: "Plan generation is now part of `/ignite`. Since you already have a project brief, I'll generate plan.md now." Then execute the plan generation logic from `/ignite` Section 12.
-3. If no: "Run `/ignite` to create both the project brief and plan in one workflow."
-
-**If the user needs to regenerate a plan from an existing brief:** Execute `/ignite` Section 12 (THE PLAN) directly, skipping the interrogation.
+---
+description: DEPRECATED in V4.6. Plan generation merged into /ignite. Kept for backwards compatibility.
+---
+
+# Plan Generator — DEPRECATED
+
+**This workflow has been merged into `/ignite`.**
+
+As of V4.6, `/ignite` generates both the Project Brief AND the Plan (plan.md) in a single workflow. There is no need to run `/init-plan` separately.
+
+**If the user runs `/init-plan`:**
+1. Check if `project_brief.md` exists in the current project folder.
+2. If yes: "Plan generation is now part of `/ignite`. Since you already have a project brief, I'll generate plan.md now." Then execute the plan generation logic from `/ignite` Section 12.
+3. If no: "Run `/ignite` to create both the project brief and plan in one workflow."
+
+**If the user needs to regenerate a plan from an existing brief:** Execute `/ignite` Section 12 (THE PLAN) directly, skipping the interrogation.

package/src/workflows/morning.md

@@ -1,222 +1,222 @@
----
-description: Quick primer to start a work session. Read Identity, set Single Test, check energy. Works anytime, not just mornings.
----
-
-# Session Primer (V4)
-
-**Trigger:** User runs `/morning`
-**Role:** Session Coach.
-**Task:** Prime the user for focused execution. Reconnect with identity and strategy.
-**Risk Tier:** LOW
-**Duration:** 5 minutes.
-
----
-
-## 0. PRE-FLIGHT
-
-Global Rules are pre-loaded as CLAUDE.md / GEMINI.md. Output `[Rules Loaded - DATE]`.
-
-LOAD (Light — Active_Context is the cache):
-1. Active_Context.md (has Identity Snapshot S5, Active Patterns S5.5, Strategic Verdict S1, Active Sessions S6)
-2. Today's Daily Note (if exists)
-NOTE: Identity Snapshot in Active_Context S5 provides Archetype, Core Drive, Anti-Identity, and Ritual for the morning prime. Active Patterns S5.5 provides pattern alerts. Strategic Verdict S1 provides the Primary Metric for Single Test. If Active_Context is stale (>2 days), flag it and suggest /analyse-day first.
-
-CONSTRAINTS:
-- Keep this fast: 5 minutes max
-- Grounded in Identity and Strategy files
-- No lengthy analysis (save that for /analyse-day)
-
----
-
-## 1. IDENTITY VISCERALIZATION
-
-Read Identity_Prime.md. Display:
-- Core Identity section
-- The Code (Non-Negotiables)
-- Daily Affirmations (if they exist)
-
-"Take 30 seconds. Close your eyes. Visualize becoming this person today."
-
-**The Subconscious Prime:**
-- Read the Anti-Identity section. These are the autopilot behaviors to reject today.
-- If today's plan exists: select top 2 Anti-Identity triggers relevant to the plan. Cite: [Daily Note].
-- If no plan exists: pick the 2 most recently triggered from Auto_Learnings.md. Cite: [Auto_Learnings.md].
-- "Today, watch for: [top 2 Anti-Identity triggers]."
-- "The person you're becoming would [specific behavior aligned with today's tasks]. Act as that person first."
-- Keep this to 2-3 sentences. Not a lecture — a calibration.
-
----
-
-## 2. CONTEXT CHECK
-
-Read Active_Context.md and today's Daily Note.
-
-**System maturity:** If `setup_date` exists in Workflow State, calculate days since setup. If first week: "Day [N] of Mover OS. This week is about building data — run /log and /analyse-day daily. The system learns from your patterns."
-
-Summarize: "Here's where you are: [Current Project], [Current Phase], [Main Blocker]."
-
-If Active_Context is stale (>3 days): "Your context is [X] days old. Consider running `/reboot` if you've been away, or update after this session."
-
----
-
-## 2.3 MONTHLY REVIEW CHECK
-
-Read `monthly_review_last_run` from Active_Context.md Workflow State.
-
-Quick date check (no subagent — pure math):
-- Is today within the **last 3 days of the month**?
-- Has `monthly_review_last_run` already fired this month?
-
-If last 3 days of month AND monthly review hasn't run this month:
-- "Monthly review hasn't run yet this month and the month ends in [X] days. Run `/review-week` before the month closes — it triggers monthly mode automatically on the last review-day."
-
-Otherwise: skip silently. No output.
-
----
-
-## 2.5 PROJECT PORTFOLIO (Quick Health Scan)
-
-Scan `{VAULT_ROOT}/01_Projects/` for all project folders. For each, check:
-- Does `plan.md` exist? When was it last modified?
-- Does `project_state.md` exist? Read `## SYSTEM STATE` last entry date if available.
-- Any `[x]` vs `[ ]` ratio in plan.md? (Quick completion health check)
-
-Classify each project using the Staleness Scale [Mover_Global_Rules.md: S19]:
-- 0-3 days: Active
-- 3-7 days: Stale
-- 8-14 days: Cooling
-- 15-30 days: Cold
-- 30+: Frozen
-
-Output a one-line summary per project:
-```
-Projects: [Name] (Active) | [Name] (Stale - 5d) | [Name] (Cold - 18d)
-```
-
-If any project is Cooling or worse: "Project [Name] hasn't been touched in [X] days. Intentional pause or drift?"
-
-Keep this under 30 seconds. Use file modification dates, not full reads. Delegate to a haiku subagent if 5+ projects exist.
-
----
-
-## 2.7 PLAN ALIGNMENT CHECK (Escalating Friction — Level 1)
-
-If today's Daily Note exists:
-1. Read `## Focus` section. Check for **Sacrifice** line (things explicitly banned today).
-2. Read `## Tasks` section. What's Priority 1? What's the Single Test?
-3. If the user's first request in this session conflicts with the Sacrifice or bypasses Priority 1:
-   - **Level 1:** "Your plan for today says: [Single Test]. It also bans: [Sacrifice item]. You're asking me to work on [request]. Intentional override or did you forget?"
-   - If user overrides: **Level 2:** "Why is this more important than [Single Test]? One sentence."
-   - If user gives a reason: **Level 3:** "Logged. 30 minutes on this, then we return to [Priority 1]. Deal?"
-   - Log in Session Log: `[OVERRIDE] User chose [X] over [plan item]. Reason: "[reason]"`
-4. If no conflict: proceed normally. Don't create friction where there isn't any.
-
-This check fires ONCE at session start, not repeatedly. The user is an adult — one conscious decision is enough.
-
----
-
-## 3. LIBRARY PRIMER (Quick)
-
-If today's Daily Note exists AND has tasks involving coding, debugging, or building:
-1. Scan `03_Library/Cheatsheets/` for entries relevant to today's task domain
-2. Scan `03_Library/Principles/` for applicable decision patterns
-3. If relevant entries found: "From your Library: [1-2 sentence summary]. [[Link]]"
-4. If nothing relevant: skip silently
-
-If today's Daily Note does not exist yet: skip Step 3 entirely. [No Daily Note for today — Step 3 skipped.]
-
-Keep this under 30 seconds. Don't read every file — scan directory names and headers only.
-
----
-
-## 4. THE SINGLE TEST
-
-From Strategy.md: What's the Primary Metric right now?
-If no Primary Metric found in Strategy.md: "Your Strategy has no Primary Metric defined — this should be added during `/analyse-day` or `/review-week`." Skip Single Test derivation.
-
-"What is the ONE thing that, if you complete today, makes today a win?"
-(If Daily Note exists with a Single Test already defined, remind them of it.)
-
----
-
-## 5. ENERGY CHECK
-
-"How's your energy right now? (1-10)"
-- If < 5: "Start with a low-friction task to build momentum. Stack small wins."
-- If >= 5: "Attack The Frog first. Hardest task while energy is highest."
-- If >= 8: "Peak state. Do the creative/strategic work now. Save admin for later."
-- If Auto_Learnings shows a pattern of crashes at a specific time today: "Heads up — you tend to crash around [time] based on past data. Front-load the hard work."
-- If yesterday's Daily Note shows low energy but user reports high today: acknowledge the recovery, don't question it. Momentum matters.
-
----
-
-## 6. PATTERN CHECK
-
-Quick scan of Auto_Learnings.md for active patterns relevant to this time of day.
-If relevant pattern found: surface it briefly. "Reminder: [Pattern] (Conf: [X])."
-
-**Pattern → Workflow Routing** [Mover_Global_Rules.md: S12]:
-If any pattern has Confidence 3+ AND is actionable right now, suggest the specific workflow:
-- Avoidance/resistance pattern active → "Pattern says you avoid [X]. Run `/debug-resistance` before starting?"
-- Strategy misalignment → "Pattern shows drift from Strategy. Consider `/pivot-strategy` or address in `/analyse-day`."
-- Energy pattern → Build it into Step 5 energy advice (already done above).
-- Scope creep → "Pattern: scope creep. Stay on plan.md today. Run `/overview` if the plan feels stale."
-
-One suggestion max. Don't overload the primer.
-
----
-
-## 7. THE LAUNCH
-
-"Your Identity is loaded. Your Single Test is set. Go win this session."
-
----
-
-## 8. SELF-VERIFICATION (CISC)
-
-Before outputting, self-check:
-1. All claims grounded in Identity_Prime.md, Strategy.md, and Active_Context.md? (90%+ accuracy)
-2. Session kept under 5 minutes (no lengthy analysis)?
-3. No banned phrases in output?
-4. Pattern surfacing grounded in Auto_Learnings.md?
-
-If any section < 90% confident: flag it explicitly.
-
----
-
-## 9. PROACTIVE SUGGESTIONS
-
-Based on observations during this session:
-1. If Active_Context is stale (>3 days): "Context is [X] days old — pattern may indicate avoidance of reflection." - Confidence: 2
-2. If energy < 5 and pattern in Auto_Learnings matches low-energy mornings: surface it. - Confidence: [from Auto_Learnings]
-3. If today's Single Test conflicts with Strategy's Primary Metric: "Alignment issue detected — want to reconcile?" - Confidence: 3
-
-"Want me to address any of these?"
-
----
-
-## 10. 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: Identity_Prime.md, Strategy.md, Active_Context.md, Auto_Learnings.md, today's Daily Note (if exists)
-Confidence range: [Determined by pattern quality in Auto_Learnings.md; flag any claim below 3]
-
-**Next:**
-- If plan exists: "Start executing your plan."
-- If no plan: "Want me to run `/plan-tomorrow` first?"
-- If returning after break: "Consider `/reboot` if you've been away 3+ days."
-
-Key rules still active:
-- All claims must be grounded in loaded files
-- Confidence < 3 = ask, don't assert
-- Append-only: never delete from Auto_Learnings.md
+---
+description: Quick primer to start a work session. Read Identity, set Single Test, check energy. Works anytime, not just mornings.
+---
+
+# Session Primer (V4)
+
+**Trigger:** User runs `/morning`
+**Role:** Session Coach.
+**Task:** Prime the user for focused execution. Reconnect with identity and strategy.
+**Risk Tier:** LOW
+**Duration:** 5 minutes.
+
+---
+
+## 0. PRE-FLIGHT
+
+Global Rules are pre-loaded as CLAUDE.md / GEMINI.md. Output `[Rules Loaded - DATE]`.
+
+LOAD (Light — Active_Context is the cache):
+1. Active_Context.md (has Identity Snapshot S5, Active Patterns S5.5, Strategic Verdict S1, Active Sessions S6)
+2. Today's Daily Note (if exists)
+NOTE: Identity Snapshot in Active_Context S5 provides Archetype, Core Drive, Anti-Identity, and Ritual for the morning prime. Active Patterns S5.5 provides pattern alerts. Strategic Verdict S1 provides the Primary Metric for Single Test. If Active_Context is stale (>2 days), flag it and suggest /analyse-day first.
+
+CONSTRAINTS:
+- Keep this fast: 5 minutes max
+- Grounded in Identity and Strategy files
+- No lengthy analysis (save that for /analyse-day)
+
+---
+
+## 1. IDENTITY VISCERALIZATION
+
+Read Identity_Prime.md. Display:
+- Core Identity section
+- The Code (Non-Negotiables)
+- Daily Affirmations (if they exist)
+
+"Take 30 seconds. Close your eyes. Visualize becoming this person today."
+
+**The Subconscious Prime:**
+- Read the Anti-Identity section. These are the autopilot behaviors to reject today.
+- If today's plan exists: select top 2 Anti-Identity triggers relevant to the plan. Cite: [Daily Note].
+- If no plan exists: pick the 2 most recently triggered from Auto_Learnings.md. Cite: [Auto_Learnings.md].
+- "Today, watch for: [top 2 Anti-Identity triggers]."
+- "The person you're becoming would [specific behavior aligned with today's tasks]. Act as that person first."
+- Keep this to 2-3 sentences. Not a lecture — a calibration.
+
+---
+
+## 2. CONTEXT CHECK
+
+Read Active_Context.md and today's Daily Note.
+
+**System maturity:** If `setup_date` exists in Workflow State, calculate days since setup. If first week: "Day [N] of Mover OS. This week is about building data — run /log and /analyse-day daily. The system learns from your patterns."
+
+Summarize: "Here's where you are: [Current Project], [Current Phase], [Main Blocker]."
+
+If Active_Context is stale (>3 days): "Your context is [X] days old. Consider running `/reboot` if you've been away, or update after this session."
+
+---
+
+## 2.3 MONTHLY REVIEW CHECK
+
+Read `monthly_review_last_run` from Active_Context.md Workflow State.
+
+Quick date check (no subagent — pure math):
+- Is today within the **last 3 days of the month**?
+- Has `monthly_review_last_run` already fired this month?
+
+If last 3 days of month AND monthly review hasn't run this month:
+- "Monthly review hasn't run yet this month and the month ends in [X] days. Run `/review-week` before the month closes — it triggers monthly mode automatically on the last review-day."
+
+Otherwise: skip silently. No output.
+
+---
+
+## 2.5 PROJECT PORTFOLIO (Quick Health Scan)
+
+Scan `{VAULT_ROOT}/01_Projects/` for all project folders. For each, check:
+- Does `plan.md` exist? When was it last modified?
+- Does `project_state.md` exist? Read `## SYSTEM STATE` last entry date if available.
+- Any `[x]` vs `[ ]` ratio in plan.md? (Quick completion health check)
+
+Classify each project using the Staleness Scale [Mover_Global_Rules.md: S19]:
+- 0-3 days: Active
+- 3-7 days: Stale
+- 8-14 days: Cooling
+- 15-30 days: Cold
+- 30+: Frozen
+
+Output a one-line summary per project:
+```
+Projects: [Name] (Active) | [Name] (Stale - 5d) | [Name] (Cold - 18d)
+```
+
+If any project is Cooling or worse: "Project [Name] hasn't been touched in [X] days. Intentional pause or drift?"
+
+Keep this under 30 seconds. Use file modification dates, not full reads. Delegate to a haiku subagent if 5+ projects exist.
+
+---
+
+## 2.7 PLAN ALIGNMENT CHECK (Escalating Friction — Level 1)
+
+If today's Daily Note exists:
+1. Read `## Focus` section. Check for **Sacrifice** line (things explicitly banned today).
+2. Read `## Tasks` section. What's Priority 1? What's the Single Test?
+3. If the user's first request in this session conflicts with the Sacrifice or bypasses Priority 1:
+   - **Level 1:** "Your plan for today says: [Single Test]. It also bans: [Sacrifice item]. You're asking me to work on [request]. Intentional override or did you forget?"
+   - If user overrides: **Level 2:** "Why is this more important than [Single Test]? One sentence."
+   - If user gives a reason: **Level 3:** "Logged. 30 minutes on this, then we return to [Priority 1]. Deal?"
+   - Log in Session Log: `[OVERRIDE] User chose [X] over [plan item]. Reason: "[reason]"`
+4. If no conflict: proceed normally. Don't create friction where there isn't any.
+
+This check fires ONCE at session start, not repeatedly. The user is an adult — one conscious decision is enough.
+
+---
+
+## 3. LIBRARY PRIMER (Quick)
+
+If today's Daily Note exists AND has tasks involving coding, debugging, or building:
+1. Scan `03_Library/Cheatsheets/` for entries relevant to today's task domain
+2. Scan `03_Library/Principles/` for applicable decision patterns
+3. If relevant entries found: "From your Library: [1-2 sentence summary]. [[Link]]"
+4. If nothing relevant: skip silently
+
+If today's Daily Note does not exist yet: skip Step 3 entirely. [No Daily Note for today — Step 3 skipped.]
+
+Keep this under 30 seconds. Don't read every file — scan directory names and headers only.
+
+---
+
+## 4. THE SINGLE TEST
+
+From Strategy.md: What's the Primary Metric right now?
+If no Primary Metric found in Strategy.md: "Your Strategy has no Primary Metric defined — this should be added during `/analyse-day` or `/review-week`." Skip Single Test derivation.
+
+"What is the ONE thing that, if you complete today, makes today a win?"
+(If Daily Note exists with a Single Test already defined, remind them of it.)
+
+---
+
+## 5. ENERGY CHECK
+
+"How's your energy right now? (1-10)"
+- If < 5: "Start with a low-friction task to build momentum. Stack small wins."
+- If >= 5: "Attack The Frog first. Hardest task while energy is highest."
+- If >= 8: "Peak state. Do the creative/strategic work now. Save admin for later."
+- If Auto_Learnings shows a pattern of crashes at a specific time today: "Heads up — you tend to crash around [time] based on past data. Front-load the hard work."
+- If yesterday's Daily Note shows low energy but user reports high today: acknowledge the recovery, don't question it. Momentum matters.
+
+---
+
+## 6. PATTERN CHECK
+
+Quick scan of Auto_Learnings.md for active patterns relevant to this time of day.
+If relevant pattern found: surface it briefly. "Reminder: [Pattern] (Conf: [X])."
+
+**Pattern → Workflow Routing** [Mover_Global_Rules.md: S12]:
+If any pattern has Confidence 3+ AND is actionable right now, suggest the specific workflow:
+- Avoidance/resistance pattern active → "Pattern says you avoid [X]. Run `/debug-resistance` before starting?"
+- Strategy misalignment → "Pattern shows drift from Strategy. Consider `/pivot-strategy` or address in `/analyse-day`."
+- Energy pattern → Build it into Step 5 energy advice (already done above).
+- Scope creep → "Pattern: scope creep. Stay on plan.md today. Run `/overview` if the plan feels stale."
+
+One suggestion max. Don't overload the primer.
+
+---
+
+## 7. THE LAUNCH
+
+"Your Identity is loaded. Your Single Test is set. Go win this session."
+
+---
+
+## 8. SELF-VERIFICATION (CISC)
+
+Before outputting, self-check:
+1. All claims grounded in Identity_Prime.md, Strategy.md, and Active_Context.md? (90%+ accuracy)
+2. Session kept under 5 minutes (no lengthy analysis)?
+3. No banned phrases in output?
+4. Pattern surfacing grounded in Auto_Learnings.md?
+
+If any section < 90% confident: flag it explicitly.
+
+---
+
+## 9. PROACTIVE SUGGESTIONS
+
+Based on observations during this session:
+1. If Active_Context is stale (>3 days): "Context is [X] days old — pattern may indicate avoidance of reflection." - Confidence: 2
+2. If energy < 5 and pattern in Auto_Learnings matches low-energy mornings: surface it. - Confidence: [from Auto_Learnings]
+3. If today's Single Test conflicts with Strategy's Primary Metric: "Alignment issue detected — want to reconcile?" - Confidence: 3
+
+"Want me to address any of these?"
+
+---
+
+## 10. 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: Identity_Prime.md, Strategy.md, Active_Context.md, Auto_Learnings.md, today's Daily Note (if exists)
+Confidence range: [Determined by pattern quality in Auto_Learnings.md; flag any claim below 3]
+
+**Next:**
+- If plan exists: "Start executing your plan."
+- If no plan: "Want me to run `/plan-tomorrow` first?"
+- If returning after break: "Consider `/reboot` if you've been away 3+ days."
+
+Key rules still active:
+- All claims must be grounded in loaded files
+- Confidence < 3 = ask, don't assert
+- Append-only: never delete from Auto_Learnings.md