Verify judges an accepted Work result against the current contract through actual execution and observation. It preserves uncertainty.
Items that were not executed or cannot be observed are not pass but unproven. Verification evidence belongs to the selected
artifact, and the implementation, contract, and project canon each remain in their respective owning routes.
Before performing this skill, open references/communication.mdand apply it to natural language sent to readers or stored in documents during execution. This includes guidance sent when terminating at a gate.
Enter with a valid contract
Before performing target-specific actions, open references/project-gate.mdand apply the verify row. If the gate routes elsewhere, change nothing.
If an index is available, read it first. Select only one immediate Work state specified by the user or the current route. If the target is undetermined and there are multiple eligible artifacts, do not use them and send to the user.
references/work-state.md, then open the selected state and sibling spec. Verification may begin only when the state grants Verify management authority, there are no blockers, it specifies a reachable committed safe point, and the spec explains the outcome, acceptance, and write boundary on its own. The spec's read_first documents, the details each criterion points to, and only the implementation, test, environment, and team context needed to execute the criterion. Before using any result as evidence, compare the current Git revision, relevant bytes, and safe point.
If required documents are missing, unreadable, or inconsistent, or the bytes to be judged cannot be precisely identified in the checkout, do not assume they are current. Without changing the project, note the inconsistency and send to resume.
If Verify already had clear management authority and a contract or owner defect was revealed during execution, record the remaining trustworthy evidence to the end, then disclose the failure owner in verification.md and the current management authority according to the common handoff contract in the Work state.
Personal settings are input that maintains the shared contract and adjusts the verification method for each team member. After confirming the valid contract and management authority and before executing the first criterion, .devflow/team/if present, references/project-gate.mdwith the current
team identity, .devflow/team/<current-member>/preferences/verify.md check only one. Reuse an identity already confirmed. If the file exists, open references/member-preferences.mdfirst and apply the personal file; if not, proceed with the default method without creating one.
Execute the acceptance contract
Evaluate the current acceptance criteria one by one independently. Record the following for each.
- Expected observable result
- What was actually observed and its revision, environment, channel
- Evidence supporting the observation
- Exactly one verdict:
proven,failed,unproven
Use actual execution or observation. A structural check does not prove visual results, a successful review does not prove a different environment, and if the revision or preconditions have changed, a past execution is not current evidence. If the necessary channel cannot be used, unprovenand record the resumption condition. If the spec designates that review surface, explicit user judgment may be used for qualitative acceptance, but do not fabricate silence as acceptance.
derive the overall result from criterion verdicts and do not create a second status field. For each failed or unproven criterion, write the broken or insufficient precondition, one failure_route, the specific target it owns, and what must change before retry.
- implementation, test, or local behavior →
work - goal, acceptance, write boundary, or shaping contract →
direct - product or Domain meaning →
product - structure, dependency, runtime, data flow, or verification channel →
architecture - UI or interaction principle →
design - maintained source readiness or disposition →
adopt - evidence that only a person or external decision can provide →
useror the corresponding decision route
This list verification.mddetermines the actual failure owner to record in. Implementation defects send Work state to work, and the remaining higher-level judgments, explorations to preserve, and user answers are sent according to the handoff contract of references/work-state.mdto
direct.
Do not modify code, test, spec, Product, Architecture, Design, Domain, or adoption canon. Do not weaken a criterion in order to directly repair or pass a failed result in a verification session.
disclose evidence before route
the project's standard summary와 read_when as one current whole-file record with a
verification.mdheader, write
- first. This file owns the following.
- 각 criterion의 expected result, observation, evidence, verdict
- the derived overall judgment
- 각 failure route와 retry precondition
- evidence of sustainable current facts discovered during verification
Only the verification file owns the verdict. Do not duplicate the verdict or evidence in state. After rereading the completed verification record, replace state.mdlast according to the common state contract. Preserve the implementation safe point and existing unresolved candidates. Add knowledge_candidateonly when new evidence supports a sustainable current fact worth judging in canon. Observations, verdicts, code paths, and test results are not candidates.
Choose one next route and action within the defined scope.
- For a failed or unproven criterion, preserve the recorded failure route and retry precondition, but send only implementation defects to
work, and other judgments todirect. - A proven intermediate-risk criterion returns to
directorworkif a scoped follow-up action remains in the spec. - When the stop condition is reached and all closure criteria are proven, judge the candidate and, after reflecting the confirmed facts, close the artifact
worksend to.
State disclosure is the last commit point. verification.mdAfter writing, if the session stopped before writing the matching state, or the state is absent or points beyond an unreadable verification record, the result is not current.
Resume reconcile -> verifymust report. Do not append attempts or preserve replaced verdict copies. If Direct later modifies acceptance or a guardrail, only the still-needed failure memory continues, and Direct is responsible for deleting stale verification records.
returns a judgment
reports the following.
대상:the judged artifact and the exact revision, environment, channelCriteria:각 criterion,proven·failed·unprovenverdict, evidenceRoute와 행동:after disclosing, one route and a scoped action미검증:unavailable observations and resumption conditions, ornone읽은 범위:all projects, Works, implementations, evidence, and personal configuration paths actually opened
It is complete when every current criterion has an honest verdict, evidence was disclosed before the route, there are no verdict copies in state, the next owner can know what to change or close, and Verify has not changed the implementation, contract, or project canon.