Repository navigation
docs: add 'Writing and running a spec' to the README - #6
Merged
Merged
Conversation
…ff wording The convention enforces issues at or above enforce-from-issue, so the documented cutoff must be the latest issue or PR number plus one. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Acceptance self-test (fixture)
Updated for commit 3d41cfc, workflow run. This comment is edited in place, never repeated. |
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.
Adds a developer-facing section (anchor
#writing-and-running-a-spec): a worked example (issue to spec, spec committed first, red then green), the exact local validate/run/proof commands, how to read the PR checks and sticky comment, the rules (red on base, green on head, not-run, report vs enforce, cutoff), the two human-only labels, and troubleshooting.Also fixes an inconsistency: the cutoff was documented as the latest issue number, but the check enforces issues at or above it, so it must be the latest issue or PR number plus one (README and docs/adopting.md).
Every command was run against a scratch app (command and api specs, red then green, base-check proof, passes-on-base failure, invalid spec). Unit tests: 136 pass.
🤖 Generated with Claude Code