Repository navigation
feat(plan,verify): checkable Given/When/Then criteria, traced from the spec (#69) - #121
Merged
Merged
Conversation
…e spec (#69) plan writes acceptance criteria per task with a named proof, asks about vague spec items before the build, and records answers. verify writes its own list from APP.md/RELEASE.md before reading PLAN.md, then traces every promised feature to a criterion and proof; untraced promises are issues. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #69.
In plain words
Today a task is "done" when a loose line like "Profile screen works" is ticked, and
verifyonly checks the plan, so anything the plan forgot is never checked. Now each task says exactly what must be true (Given … When … Then …) and what proves it, andverifyfirst writes its own list from the spec, so a forgotten feature shows up as a gap.What changed
plan: new "Acceptance Criteria" section.<spec-clarifications>. Underautonomousit never asks: it records the safest reading assource="assumed".via="screen"(what's on screen) orvia="package"(a Swift package's public functions), and a<proof>: test / flow / lint / manual.verify: Step 1 writes its own list from the spec without opening PLAN.md; Step 2 compares and traces feature → criterion → proof. A must-feature with no criterion fails; missing proofs and missed cases are partial. Older plans with no criteria still verify, against<done>.build: agents write the tests the criteria name, testing from outside.autonomous: the independent verifier gets the spec first; assumptions show in the phase recap.Test
./scripts/validate.shpasses. Behavior needs a real project run (next/apple:plan+/apple:verify).🤖 Generated with Claude Code