pgermishuys/opencode-weave/sdd-planning

# Implementation Plan: [Feature Name]
**Feature**: [{slug}](./)
**Status**: Draft | Approved
**Spec**: [spec.md](./spec.md)
 
## Technical Context
-**Stack**: [languages, frameworks, databases, runtimes]
-**Architecture pattern**: [MVC / layered / event-driven / etc.]
-**Key dependencies**: [list any new dependencies required]
-**Unknowns**: [mark as UNKNOWN — resolved in Phase 0]
 
## Constitution Check
| Principle | Status | Notes |
|-----------|--------|-------|
| [Principle Name] | ✅ Complies | [how] |
| [Principle Name] | ⚠ Partial | [gap and mitigation] |
| [Principle Name] | ❌ Violation | [BLOCKING — must resolve before proceeding] |
 
**Rule**: Any ❌ violation blocks the plan. Fix the violation or amend the constitution before continuing.
 
## Phase 0: Research
*Resolve all UNKNOWN items from Technical Context before designing.*
 
-[ ] Research [UNKNOWN item] → output findings to `./research.md`
-[ ] Investigate [integration point] → document API/contract details
-[ ] Spike [technical uncertainty] → prototype approach, document decision
 
## Phase 1: Design
 
### Data Model (`./data-model.md`)
For each entity:

 
### API Contracts (if applicable)
For each endpoint:

# [Feature Name] — Implementation Plan
 
## TL;DR
> [One sentence summary of what will be built and why]
 
## Context
 
### Feature
[Brief description of the feature and its goal]
 
### Spec reference
[Link to spec: `.specify/features/{slug}/spec.md`]
 
### Key technical decisions
[1-3 bullets on the key architectural decisions from the SDD plan]
 
## Objectives
-[ ] [Deliverable 1]
-[ ] [Deliverable 2]
-[ ] [Deliverable 3]
 
## TODOs
 
### Phase 0: Setup
-[ ] T001 [P1] [US0] Scaffold directory structure and dependencies
 
### Phase 1: Foundation
-[ ] T002 [P1] [US1] Create [core entity] data model
 
### Phase 2: User Stories
-[ ] T003 [P1] [US1] Implement [user story 1 behavior]
-[ ] T004 [P2] [US2] Implement [user story 2 behavior]
 
### Phase 3: Polish
-[ ] T005 [P1] [US1] Handle [edge case from spec]
-[ ] T006 [P2] [US2] Add error messages per spec SC-003
 
## Verification
-[ ] All FRs in spec.md have corresponding passing tests
-[ ] All SCs in spec.md are verifiable
-[ ] Constitution compliance confirmed

- [ ] T### [P1/P2/P3] [US#] Task description

## ❌ CONSTITUTIONAL VIOLATION DETECTED
 
**Principle**: [Principle Name]
**Violation**: [What the planned implementation would do that violates this principle]
**Resolution options**:
1. Change the implementation approach to [alternative]
2. Amend the constitution to allow [exception] (requires ratification)
3. Defer this feature until the violation is resolved