Reusable
Templates
Start every feature with structured intent. Copy these into requirements.md or a section PRD.
User Story
Goals, not implementation. Checkboxes for done.
## US-XXX — [Short title] **As a** [specific role], **I want** [capability or outcome], **So that** [benefit — why this matters]. ### Acceptance Criteria - [ ] Criterion 1 — objective, testable - [ ] Criterion 2 ### Out of Scope - Explicitly excluded items
Requirements
Living document with Clarification Gate built in.
# Requirements — [Project / Feature Name] > Living document. Zero open items before implementation. ## Vision One paragraph: what this is and why it exists. ## Open Items (Clarification Gate) | ID | Question | Status | |----|----------|--------| | OI-001 | _Question_ | [OPEN] | ## User Stories <!-- Copy from user-story template -->
Tasks (Section 2)
Atomic tasks with dependency order, requirement links, and verification — after Clarification Gate passes.
### Task 1: [Title] | Field | Value | |-------|-------| | **Requirement** | REQ-XXX — [title] | | **Depends on** | — or Task N | | **Description** | [Atomic unit of work] | **Verification:** - [ ] [Objective criterion]
Guidelines
Write goals, not implementation details
One story, one outcome — split large features
Checkboxes for done — no subjective completion
Log open items — unresolved questions block the gate
AgentOS memory (Section 6)
Persistent project context — plan, roadmap, and stack — so AI assistants reload focus every session.
plan.mdSee templates/plan.md in the repo
roadmap.mdSee templates/roadmap.md in the repo
techstack.mdSee templates/techstack.md in the repo
Full templates also live in the repo at
templates/user-story.md, templates/requirements.md, templates/tasks.md, and AgentOS templates/plan.md, roadmap.md, techstack.md.