Context is limited, so it is important to document requirements, changes and
tasks so that they can be reviewed and used between sessions. Other files
ensure the same process is followed between sessions and that the current
status is always clear.
PRD
Requirements.md
The product requirements document is the source of truth. Requirements use IDs such as FR-7 (functional), NFR-3 (non-functional) and UX-7 (user experience), so code, tests and reviews cite the same rule. Changes need founder approval and an ADR.
ADR
docs/decisions/ADR-*.md
An Architecture Decision Record is a short file for one decision: context, choice, consequences and date. ADR-001 records the agent and model assignments, ADR-004 that AI is optional, ADR-005 test-type enablement and ADR-024 pacing. Settled decisions are not re-argued from memory.
Task brief
docs/tasks/*.md
One work package per session. The brief states the goal, acceptance criteria, product rules, likely files, references and out-of-scope work, then records the handoff.
Status
docs/STATUS.md
Read first and updated last. It records what is done, what is next, open questions and the decision log.
Instructions
Agents.md and skills
Agents.md carries the project rules, toolchain and agent policy. Versioned skills give the agents task-specific guidance — for example, how to apply the card and deck rules, how the spaced-repetition engines behave, how to use the on-device AI features, and how the content pipeline works. They are updated when the PRD changes.
Operations
docs/ops/
Runbooks, manual test checklists and evaluation reports. They are the evidence trail for releases and AI quality work.