Skip to content

docs: use renamed rfc2119 npm package in AGENTS.md #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tylerwillis wants to merge 1 commit into from
Closed

docs: use renamed rfc2119 npm package in AGENTS.md #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,16 +5,16 @@ This repository enforces spec-driven testing with [2119](https://www.rfc-editor.

**When planning a feature**, write or update a spec in `specs/` first. Every
requirement is a numbered item under a `### REQ-NNN.M` heading with exactly one
RFC 2119 keyword. Run `npx 2119 lint` after editing specs.
RFC 2119 keyword. Run `npx rfc2119 lint` after editing specs.

**When implementing**, every MUST/SHALL requirement needs at least one test
annotated with a comment containing its ID, e.g. `// 2119: REQ-001.2.3`.
Write tests that would genuinely fail if the requirement were violated — a
fresh-context reviewer will judge each test's honesty, and tautological or
over-mocked tests will be rejected.

**Before finishing any task**, run `npx 2119 check`. It must exit 0. If it
reports pending judgment reviews, run `npx 2119 review` and dispatch each
**Before finishing any task**, run `npx rfc2119 check`. It must exit 0. If it
reports pending judgment reviews, run `npx rfc2119 review` and dispatch each
instruction file in `.2119/reviews/` to a fresh-context subagent (never
review your own work in the same context). CI runs the same check, so skipping
it locally only defers the failure.
Expand Down
Loading