Requirements that survive a change of stack.
A complete business contract, replaceable architecture, and executable tests before implementation. One atom, one unit of knowledge.
Keep the business contract
Rules, concepts and AC must be sufficient to reproduce functionality without reading the old code. IDs preserve meaning across ports.
Replace the architecture
Technologies, component contracts and constraints live in a separate domain. Replace them while preserving the business guarantees.
A verifiable contract before code.
Gate A — Analysis
Actors, rules, invariants and guarantees without the old code.
Gate B — Gherkin
Stable AC and concrete, observable outcomes.
Gate C — Tests · RED
Real execution before behavior; failure caused by the requirement.
Gate D — Implementation · GREEN
The same tests and affected regressions pass.
After GREEN comes acceptance: requirement → scenario → test → result. Environment errors and skips are neither RED nor PASS. One agent can perform the roles.
Create the link while writing the code
Declare an existing requirement ID first, then add its URI and a meaningful explanation in the same change. This example illustrates the syntax.
# atomic-spec://PAYMENT-001/DR-1
# Retrying a payment never increases the total debit.
def apply_payment():
...A configured project Guard takes priority. Formal PASS validates references in the selected scope; meaning and behavior need their own review. Atomic Spec Guard
One skill, the complete workflow
apm install dab512/atomic-spec --target agent-skillsFor a pinned installation, download skill archive 2.0.2 and extract it into .agents/skills/. It contains templates, role instructions and Git Guard without local dependencies.
Open release 2.0.2Documentation
- Getting started
- Methodology
- Atom anatomy
- Architecture and portability
- Gates and acceptance
- Traceability
- Migration to 2.0
- Classifying changes
The previous edition remains in history. Status implemented refers only to an accepted implementation scope and does not imply deployment.