plan-audit

To audit plan spec impact, the active plan is loaded from ~/.claude/plans and classified as trivial or substantive using spec-capture guidance to determine go/no-go readiness. Substantive plans trigger a process story creation and targeted spec section audits to ensure alignment with architecture and epic goals.

A process story in plan auditing is a narrative record generated for substantive plans to capture the execution flow and spec alignment context. It is needed when a plan is classified as substantive rather than trivial, ensuring architecture and epic goals are verified before proceeding.

Classifying a plan as trivial or substantive relies on signals defined in the spec-capture-guide reference to evaluate the scope of changes and potential impacts. Substantive classifications require deeper spec audits and AVFL validation checkpoints before a go/no-go decision is finalized.

AVFL checkpoints can be run during plan exit validation when applicable, coordinating validation alongside the generated Spec Impact section. The workflow updates sprint-status and plan files with the final go/no-go decision after these checkpoints pass.

Plan auditing works without external dependencies, relying entirely on internal scripts and reference guides like spec-capture-guide.md. It operates by locating the active plan locally and extracting the title from the first H1 heading to begin the classification and audit process.

Automated spec impact generation is limited to plans located in the ~/.claude/plans directory and requires an H1 heading to extract the plan title. Plans lacking proper heading structure or stored outside this directory cannot be audited or classified by the workflow.