qstack-plan-adherence-reviewlisted

Review whether an approved QStack HTML plan was faithfully executed by comparing plan.html with execution.md, executor.md, or legacy implementation notes and the actual committed and uncommitted code changes. Build a requirement-to-evidence matrix, identify missing or unapproved deviations, check whether the execution record matches reality, and assign a guarded 0-5 adherence score. Use when invoked as /qstack-plan-adherence-review, when asked whether a plan was followed, or before closing or landing planned work.
hani-q/qstack · ★ 7 · Code & Development · score 78

Install: claude install-skill hani-q/qstack

# /qstack-plan-adherence-review Audit the implementation against the plan. Treat the plan as the contract, the code and test results as ground truth, and the execution record as supporting evidence that must itself be checked. This is report-only work. Do not edit the plan, execution record, code, tests, or repository instructions. Do not commit or push. Write an `adherence-review.md` only when the user explicitly asks for a saved artifact; otherwise report in the final response. ## Resolve the evidence 1. Use a plan path supplied by the user. 2. Otherwise use a plan clearly referenced in the conversation. 3. Otherwise inspect `qstack/compound_engineering/plans/*/plan.html`, then legacy `compound-engineering/plans/*/plan.html` and `plan.md`. Never select `.template/`. Use the only plausible candidate; ask when multiple candidates remain. 4. In the plan directory, prefer `execution.md`. Also read `executor.md` and legacy `implementation-notes.md` when present; do not discard history merely because a newer filename exists. 5. Read `board-events.js` beside them when it exists. Run `node --check`, then skip its required format header and fold the remaining `qstackBoardEvent({...});` calls in file order for each card's final status, owner, `refs`, and `files`. Stop on broken JavaScript. Agents write the board while they work, so it has the standing `execution.md` already has here: evidence to be checked against the code, never trusted on its own.