@ryanthedev/build-doctrine
BImplements a coding task from a written spec with Done-When acceptance items. Use when given a spec to implement: stub the interface, implement it, then write tests that validate the Done-When items and any important behavior beyond them.
Install
agr install @ryanthedev/build-doctrine --target claudeWrites 1 file into .claude/skills/, pinned to git-fa781dca.
- .claude/skills/build-doctrine/SKILL.md
Document
name: build-doctrine description: "Implements a coding task from a written spec with Done-When acceptance items. Use when given a spec to implement: stub the interface, implement it, then write tests that validate the Done-When items and any important behavior beyond them."
Build Doctrine
Implement the task described in the provided spec so it satisfies the spec's Done-When (DW) items. Write all code and tests to the exact output paths the spec names.
Process
- Stub the interface — lay down the function/class signatures and data shapes the spec calls for, with empty bodies.
- Implement — fill in the bodies until every DW item's behavior is complete.
- Validate — write tests after the implementation:
- Cover every DW item. Name those tests for their DW-ID (e.g.
test_DW_1_1_parses_hours). - Then go past the DW list: add tests for the edge cases, error paths, and boundaries the implementation surfaced — anything you judge matters, even when no DW item names it.
- Assert on intended behavior (input → expected output), not on whatever the code happens to return.
- Run the suite. Every test must pass.
- Cover every DW item. Name those tests for their DW-ID (e.g.
Trustgrade B
- passBody integrity
Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.
- passType matchnot applicable to this artifact type
Whether the artifact is really the kind of thing its metadata claims it is.
- passFreshness
How long since the source repository was last pushed to.
- passPrompt injection
Scans the artifact's own text for instructions aimed at your agent rather than at you.
- warnLicenseno SPDX license detected
Whether the source repository declares an SPDX license permissive enough to redistribute.
How the grade is calculated
Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:
- Aevery check passed
- Bone warning
- Ctwo warnings
- Dprompt injection or body integrity failed, or three warnings
- Fone of those failed, and something else is wrong
These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.
Versions
git-fa781dca5f632026-07-31