Project Verification Flow

Trigger

implement-spec reaches a visibly exercisable acceptance criterion and selects its verification scenario and app.

Creation

An Uncovered Surface invokes create-verification-skill during implement-spec. The creator interviews the repository and existing wiki knowledge, writes the missing app reference, and completes one Reference Smoke Proof. A ready result resumes the original scenario. A blocked result blocks the affected acceptance criteria.

Scaffold and update post-command flows do not invoke creation. They leave Project Verifier content unchanged.

Verification

verify-behavior loads the project index, selected app reference, applicable Feature Map entries, and any Cross-App Journey. It exercises the real user path and returns evidence to implement-spec, which owns acceptance and any affected rerun.

Uncovered Behavior

When the app reference exists but the selected scenario has no Feature Map entry or executable drive path, implement-spec invokes update-verification-skill. The updater reads applicable wiki and code evidence, adds or repairs only the executable knowledge required by that scenario, and proves the path before returning control.

A ready result resumes the original scenario. A blocked result keeps the scenario and affected acceptance criteria blocked. The updater returns unchanged, updated, blocked, or product-failure; product failures route to debugging-phase instead of changing expected behavior. Targeted updates preserve unrelated references, while an explicit full-audit invocation may cover suspected broad drift.

Documentation Boundary

docs-ingest-phase never invokes update-verification-skill and never creates, edits, regenerates, or maintains Feature Maps. Wiki specifications, behavior pages, flows, and domain knowledge remain inputs that the creator and updater may consume.

Review Boundary

review-phase remains readonly Code Review. It does not own Verification evidence freshness, execute the Project Verifier, or rerun behavior proof.