- AGENTS.md
- PRODUCT_SPEC.md
- ARCHITECTURE.md
- TASKS.md
Only these documents are authoritative.
Ignore all files under:
docs/
Never use files in docs/ as requirements.
Never implement features described only in docs/.
Product:
PRODUCT_SPEC.md
Architecture:
ARCHITECTURE.md
Tasks:
TASKS.md
If a conflict exists:
PRODUCT_SPEC.md
>
ARCHITECTURE.md
>
TASKS.md
>
everything else
PRODUCT_SPEC.md defines:
- Product
- Users
- User Journey
- UX
- Content
- Business Intent
ARCHITECTURE.md defines:
- System Design
- Technical Structure
- Repository Structure
- Constraints
TASKS.md defines:
- Current Work Scope
- Execution Order
Implement only the selected task.
Do not implement:
- future work
- roadmap items
- optional features
- assumptions
- inferred requirements
Implement only requirements explicitly defined by:
- PRODUCT_SPEC.md
- ARCHITECTURE.md
- TASKS.md
For every task:
- Read PRODUCT_SPEC.md
- Read ARCHITECTURE.md
- Read task definition
- Implement
- Test
- Stop
Do not start another task automatically.
If implementation conflicts with PRODUCT_SPEC.md:
STOP
Propose PRODUCT_SPEC.md update.
Do not silently change product behavior.
If implementation requires architecture changes:
- Update ARCHITECTURE.md
- Update implementation
Never allow architecture and code to diverge.
If implementation invalidates a task:
Update TASKS.md.
Prefer:
- simple
- explicit
- minimal
Avoid:
- abstraction without use
- premature optimization
- speculative features
Do not create new top-level documents unless explicitly requested.
Prefer modifying existing files.
Task is complete only when:
- product requirements satisfied
- architecture requirements satisfied
- task requirements satisfied
- code runs
- tests pass
Then stop.