qstack-plan-close

# /qstack-plan-close Turns a finished piece of work into compounding knowledge. The plan is not the lesson. **The lesson is the delta between the plan and reality**: what diverged, what surprised you, what cost hours that nothing predicted. This skill captures that delta and writes it where the next plan in this area will read it. ## The convention ``` qstack/compound_engineering/plans/<feature-slug>/ ├── plan.html # BEFORE: what we predicted. Frozen once work starts. ├─��� board-events.js # DURING: append-only card events, written by agents. ├── execution.md # DURING: decisions, deviations, validation, and reviews. └── outcome.md # AFTER: this skill writes it. ``` If the repo has `qstack/compound_engineering/README.md`, read it first: it may extend or override what follows. Also support the legacy `compound-engineering/plans/<feature-slug>/` layout and its README. Prefer the QStack layout when both contain the requested feature. If neither plan root exists, offer to create the QStack layout before proceeding. ## Hard rules - **Never edit `plan.html` or legacy `plan.md`.** The plan is frozen once work starts; divergence is recorded in `outcome.md`, not by rewriting history. - **Never commit.** Write files and stop. The user commits. - **Do not implement anything.** This skill only writes documentation. ## Steps ### 1. Identify the plan folder ```bash ls qstack/compound_engineering/plans/ ls compound-eng...