This directory stores implementation-facing product requirement documents for the current Fulling codebase.
Put documents here when they define product behavior that directly affects:
- control-plane state
- UI-visible status semantics
- retry behavior
- persistence requirements
- API or workflow expectations for a concrete feature
Examples:
- import project control flow
- deploy project workflow
- install skill behavior
- database creation UX and state semantics
Do not put high-level strategy, roadmap thinking, or long-range architecture vision here. Those should stay in the handbook project space.
Recommended split:
handbook/projects/fulling/- vision
- roadmap
- version plans
- postmortems
- architecture direction
docs/prds/- implementation-facing feature requirements for the repository
- One PRD per feature or workflow
- Use stable kebab-case file names
- Prefer names like
import-project-control-flow.md
Each PRD should usually include:
- Goal
- Scope
- Success semantics
- Failure semantics
- State requirements
- UI requirements
- Retry behavior
- Persistence requirements
- Non-goals