SR Method EN
Codex Project Pack
The handoff folder between product discovery and Codex execution.
Codex Project Pack
The Codex Project Pack is the handoff folder between discovery and Codex execution.
Its role is to prevent starting Codex with a vague or incomplete conversation.
End-of-iteration product prompt
Which documents should be produced so the Codex developer can understand and build the project?
I expect at minimum a codex_project_pack/ with:
00_PROJECT_BRIEF.md
01_PRD.md
02_FUNCTIONAL_SPECS.md
03_TECHNICAL_ARCHITECTURE.md
04_DATA_MODEL.md
05_API_CONTRACTS.md
06_UI_UX_SPEC.md
07_SECURITY_PRIVACY.md
08_TEST_STRATEGY.md
09_DELIVERY_ROADMAP.md
10_INITIAL_SR_LOTS.yaml
11_CODEX_BOOTSTRAP_PROMPT.md
12_DOMAIN_EXPERTISE_MAP.md
13_DOMAIN_SKILLS_PLAN.yaml
project-skills/README.md
project-skills/<domain-skill>/SKILL.md
Also propose additional documents needed by the project.Practical role of documents
| Document | Role |
|---|---|
00_PROJECT_BRIEF.md | Executive summary: promise, target, problem, scope. |
01_PRD.md | Product vision, users, journeys, objectives and acceptance criteria. |
02_FUNCTIONAL_SPECS.md | Features, rules and edge cases. |
03_TECHNICAL_ARCHITECTURE.md | Stack, modules, boundaries, dependencies and technical principles. |
04_DATA_MODEL.md | Entities, relations, constraints, storage and planned migrations. |
05_API_CONTRACTS.md | Endpoints, payloads, errors, security and conventions. |
06_UI_UX_SPEC.md | Screens, navigation, states, components and visual expectations. |
08_TEST_STRATEGY.md | Automated, manual, E2E tests and validation criteria. |
10_INITIAL_SR_LOTS.yaml | First proposed lots, with scope and stop conditions. |
12_DOMAIN_EXPERTISE_MAP.md | Business domain map and critical rules. |
13_DOMAIN_SKILLS_PLAN.yaml | Plan for Codex domain skills to create. |
Additional documents
Depending on the project, add regulation, business rules, mobile/offline, RAG, runtime agents, existing migration, API integration, security or specialized UX.