devflow-plan-reconciliation

Skill: devflow-plan-reconciliation

Plan-vs-Implementation guard. The plan is the contract; implementation should respect it. This skill forces an honest accounting before evidence-gathering (devflow-verification-gate), so the review actually corresponds to what was approved.

When to use

In review state, before devflow-verification-gate. After self-review (devflow-receiving-review) and before the final flow_update review→done.

Process

1 · Pull the approved plan + the change-set + the wiki snapshot

flow_get({ id })                  // returns implementation_plan + acceptance_criteria
git diff main...HEAD --stat       // file-level summary
git log main..HEAD --oneline      // commits since branch
planning_context({ flowId: id })  // related ADRs + parallel flows + reference flows + arch modules
wiki_get_briefing({ flowId: id }) // current relatedAdrs / relatedDocs / gaps / briefing

The planning_context + wiki_get_briefing calls let you compare the wiki state at planning-time (as cited in the plan) against the wiki state right now. moved rows in the reconciliation table almost always indicate an extend-write candidate. Iron Law — extend > dismiss: never close a gap surfaced here via dismiss; either extend an existing entry, create a new one, or intent_defer with substantive reason.

2 · Build the reconciliation table

For each acceptance criterion and each top-level section of the implementation plan, decide one of:

Status	Meaning	Action required
done	Implemented as planned	Note the commit / file
partial	Started but not finished	Either finish it now, or file intent_defer with horizon
missing	Plan says do it; not done	Either do it now, or intent_defer with substantive reason
extra	Done but not in the plan	Document why — scope-creep gets a one-line rationale
moved	Done but in a way that doesn't match the plan	Document the deviation + reason (often this becomes a wiki update via extend)