/plan-amend
Reference for the /plan-amend command: invocation, arguments, inputs and outputs.
Changes an existing plan suite without losing resolved decisions, re-deriving only the affected spec, phases and notes. Use when the user asks to 'amend the plan', 'add a phase to the plan' or 'revert a plan change'. Needs an existing suite; to create one use plan-generate.
Invocation
/plan-amend [amend|extend|refine|revert|weave] [suite-path] [--dry-run]Pipeline position
Wrapping / orthogonal. /plan-amend operates on a suite that already exists at any stage of the canonical sequence /plan-spec → /plan-generate → /plan-review → /plan-design (CONDITIONAL — architecture-bearing suites only) → /plan-execute. Invocable at any point once a suite exists; it inspects the suite's current stage and re-derives only the affected downstream artifacts. It never executes phase implementation work — it leaves the amended suite ready for re-review.
Inputs
The target suite's _spec/spec.md, _inputs/handoff-manifest.yml, infrastructure files (PREAMBLE.md, MASTER-PLAN.md, PROGRESS.md, PLAN-NOTES.md), phases/**/PHASE.md, and any existing phase reports. The PLAN-NOTES.md decision ledger is the authoritative record of prior resolved decisions and is read first.
Outputs
The re-derived subset of downstream artifacts the amendment touches (spec, master-plan, phase files, notes); an appended PLAN-NOTES.md decision-ledger entry recording the amendment mode, the affected artifacts, and the rationale; and an updated handoff manifest reflecting the amended suite shape. Artifacts the amendment does not touch are left byte-unchanged.
Next step
Invoke /plan-review on the amended suite. /plan-review re-audits the amended suite from scratch under the Blind Review Mandate, confirming the amendment introduced no regression before any downstream execution — it is the canonical successor to every amendment.
Source
Generated from src/apothem/commands/plan-amend.md, the command definition every harness installs.
/plan-execute
/plan-execute — अनुरूपता जाँच के साथ मास्टर प्लान सूट से किसी विशिष्ट फ़ेज़ को निष्पादित करता है।
/plan-audit
/plan-audit — /plan पाइपलाइन का बंद-लूप संरक्षक — spec → generate → review को लपेटता है और निष्कर्षों को सक्रिय रूप से ठीक करता है जब तक सूट एक समीक्षित, शून्य-निष्कर्ष समग्र न बन जाए।