Initial commit
This commit is contained in:
@@ -0,0 +1,33 @@
|
||||
# Implementation Plan: {{FEATURE}}
|
||||
|
||||
*Created: {{DATE}}*
|
||||
|
||||
Turn the spec into concrete technical decisions. Stay minimal: prefer the
|
||||
simplest structure that satisfies the spec, and justify anything that isn't.
|
||||
|
||||
## Technical Context
|
||||
|
||||
Language/runtime, dependencies, storage, testing approach, target platform,
|
||||
and any performance or scale constraints. Unknowns become research notes here
|
||||
— resolve them before writing tasks.
|
||||
|
||||
- Language:
|
||||
- Dependencies:
|
||||
- Storage:
|
||||
- Testing:
|
||||
|
||||
## Structure
|
||||
|
||||
The intended source layout: directories, modules, and where new code lands.
|
||||
|
||||
```
|
||||
(project tree sketch)
|
||||
```
|
||||
|
||||
## Decisions
|
||||
|
||||
Each significant choice with its one-line rationale and the alternative that
|
||||
was rejected. Anything that adds complexity needs a justification tied to a
|
||||
requirement.
|
||||
|
||||
- D1: … — because …
|
||||
Reference in New Issue
Block a user