Reusable agent instructions for delivering software through human gates, user/system requirements, red-first TDD, and V-model traceability.
The process traces:
EPIC -- optionally groups --> UR and/or SR
UR -> acceptance scenario -> TEST_CASE -> TEST_RESULT
UR acceptance scenario -- may require --> SR
SR -> CODE -> TEST_CASE -> TEST_RESULT
Normal development passes planning, technical review, human entry, red-first evidence, implementation, cleanup, verification, delivery, reconciliation, and human completion. An eligible source-scoped baseline uses existing-proof verification and one human acceptance instead; publication alone proves neither verification nor delivery.
Product repositories hold authoritative process records in one selected store,
alongside specifications, code, tests, evidence, and attributable gate answers.
file-state/ defines the canonical serialization of those records: a
store-backed repository materializes the shapes as uncommitted snapshots and
projections, a file-backed repository versions them as the store itself — one
or the other, never both at once.
AGENTS.md— binding agent rules.PROCESS.md— the complete canonical process.skills/rdd-start/SKILL.md— session entry and scope routing.skills/rdd-deliver/SKILL.md— complete-loop orchestration; use the otherskills/rdd-*/SKILL.mdfiles for explicitly bounded passes.
PROCESS.md is the single source for process semantics. Skills
apply that model; file-state/ serializes its records without redefining it.
| Path | Purpose |
|---|---|
AGENTS.md |
shared agent policy and canonical entry point |
PROCESS.md |
complete canonical process |
skills/ |
delivery orchestration, an autopilot sprint (rdd-autopilot), and focused passes; rdd-verify for entered verification work; rdd-reverse-engineer for baseline publication or DERIVED additions; rdd-reverse-engineer-verify and rdd-reverse-engineer-accept for eligible existing baselines; rdd-audit for documents and citations |
file-state/ |
canonical serialization shapes for Epic, requirement, gate, work-selection, and backlog/gap records |
Consuming repositories do not vendor this repository. A distribution tool —
for ModernPath workspaces, the modernpath CLI — embeds a byte-identical
snapshot of these files and installs it under .modernpath/rdd/, so in a
consuming repository the canonical process resolves at
.modernpath/rdd/PROCESS.md with every skills/rdd-*/SKILL.md beside it.
Platform-specific metadata, compatibility files, registration and hooks belong
to the distribution tool. This repository supplies the shared instructions and
skills; the installer supplies the adapters for each platform in use.
In a store-backed consuming repository the tooling additionally materializes
two uncommitted projections (for ModernPath workspaces,
.modernpath/working-set/ and .modernpath/your-move/): the session working
set — shape files pulled on demand, each stamped with its source-store
revision — and the pending human-decision queue, which lists only OPEN
human gates with current passing prerequisites. Neither is an authority; see
PROCESS.md "State records and reconciliation".
Changes to lifecycle, status meanings, trace relationships, gate requirements,
evidence rules, or record ownership belong in PROCESS.md. Validate internal
links and search the skills and flat-file shapes for competing authority
statements whenever it changes.
License: MIT.