47 lines
697 B
Markdown
47 lines
697 B
Markdown
# <Plan Title>
|
|
|
|
- Status: `proposed`
|
|
- Owner: `<name or agent>`
|
|
- Date: `YYYY-MM-DD`
|
|
|
|
## Goal
|
|
|
|
Describe the outcome in one short paragraph.
|
|
|
|
## Scope
|
|
|
|
- In scope:
|
|
- Out of scope:
|
|
|
|
## Constraints
|
|
|
|
- List technical or product constraints.
|
|
|
|
## Affected Surfaces
|
|
|
|
- `packages/ui`
|
|
- `apps/docs`
|
|
- `tests`
|
|
- `registry`
|
|
- other paths as needed
|
|
|
|
## Plan
|
|
|
|
1. Step one.
|
|
2. Step two.
|
|
3. Step three.
|
|
|
|
## Validation
|
|
|
|
- `pnpm harness:validate:component`
|
|
- `pnpm harness:validate:docs`
|
|
- Add or remove commands for the actual task
|
|
|
|
## Orchestration Task Sketch
|
|
|
|
- Optional task IDs and dependencies when the work should be dispatched through `pnpm harness:orch`
|
|
|
|
## Status Log
|
|
|
|
- `YYYY-MM-DD HH:MM` initial note
|