forge-planlisted

# Forge Plan The second step in the issue pipeline: `confirmed → approved`. Turns a triaged issue into a concrete implementation plan a coding agent can follow without re-exploring the codebase. Planning is the highest-value step in the pipeline. A good plan saves the coding step from wasting tokens on exploration, wrong turns, and rework. > **English-only**: every byte written to the issue's `plan` field MUST be in English regardless of the issue's source language. See [`../README.md` § English-only rule](../README.md) for the full rule + the ISS-43 incident that motivates it. Translate user wording to English before embedding in the plan. ## Usage ``` /forge-plan <documentId> ``` ## Two-tier planning - **Lightweight (Simple / Medium):** `knowledge.json` + issue description + targeted Glob to identify files; read at most 1-2 source files; focus on **what** (files, changes, approach). - **Deep (Complex):** full codebase exploration; read all affected files, trace dependencies, verify patterns; be concrete about **what** and **how** (paths, function names, pattern references). Tier is determined by the triage comment's complexity classification. ## Status transitions (set in Step 6) | Complexity | Status set | Trigger | |---|---|---| | Simple / Medium | `approved` | auto-approved — forge-code dispatches immediately | | Complex atomic (not decomposed) | `waiting` | human reviews + approves before code starts | | Complex composite (decomposed) | `waiting` + children at