forge-resumelisted

# forge-resume Re-orient after a session break. Inject the stage-appropriate context and state the exact next action — no re-discovery required. ## When to Use - User runs `/forge:resume` - User starts a new session and asks to continue Forge work - User says "pick up where we left off", "resume", "what was I doing?" - After a long gap and the context window is fresh ## Pre-flight Run this check first: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py --cwd . read ``` If the command fails or the directory has no `pipeline/state.md`, tell the user the project is not initialized and suggest `/forge:init`. ## Steps ### 1. Read pipeline state ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/state-manager.py --cwd . read ``` Extract: `current_stage`, `current_task`, `current_milestone`, `last_updated`, `blockers`. ### 2. Load stage-appropriate context ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/context-pruner.py \ --stage <current_stage> \ --cwd . \ --budget 1800 ``` For each artifact in the returned `artifacts` list: - Read its `content` field directly (do not re-read from disk — use what the pruner returned) - Inject the content into your working context These artifacts are already priority-ordered and budget-capped. Do not load additional files beyond what the pruner returns unless the user explicitly asks. ### 3. Read last reflection From `pipeline/state.md`, extract the **Last Reflection** section. This shows what happened in the previous se