Planning Templates
PRD Update Template
Use this to add the containerisation work to the project requirements.
Current state
Describe the application as it exists today. What does it do? How is it deployed? What breaks?
Proposed changes
Describe what containerisation adds. Why Docker? What problems does it solve for the client?
Acceptance criteria
List what "done" looks like. Be specific -- measurable outcomes the client can verify.
Decomposition Plan Template
Use this to plan the sequence of work before starting.
Sequence
| Order | Task | Depends on | Context to include |
|---|---|---|---|
| 1 | What you do first | Nothing -- starting point | What AI needs to know for this task |
| 2 | What you do second | Task 1 output | What to include, what to exclude |
| 3 | What you do third | Tasks 1 and 2 | Relevant context for this task |
For each task, write a reason for its position. "Because the frontend depends on the API endpoint" is a dependency argument. "Because I want to start with the backend" is not.
Context per session
For each task, list what you'll include in the AI session and what you'll exclude. This is a decision, not a default.
Ticket Template
Ticket ID: T[N]
Title: [What this ticket accomplishes]
Depends on: [Other ticket IDs, or "none"]
Acceptance criteria:
- [ ] [Specific, verifiable outcome]
- [ ] [Specific, verifiable outcome]
Notes: [Anything the developer needs to know]