Add harness workflow and Material showcase design system
This commit is contained in:
@@ -0,0 +1,44 @@
|
||||
# Execution Plans
|
||||
|
||||
Execution plans make non-trivial work resumable and reviewable by both humans and agents.
|
||||
|
||||
## Naming
|
||||
|
||||
Use `YYYY-MM-DD-short-name.md`.
|
||||
|
||||
Examples:
|
||||
|
||||
- `2026-03-23-harness-foundation.md`
|
||||
- `2026-03-24-date-picker-accessibility.md`
|
||||
|
||||
## When To Add One
|
||||
|
||||
Create or update a plan when the change:
|
||||
|
||||
- spans multiple directories or validation surfaces
|
||||
- alters public contracts, release behavior, or build pipelines
|
||||
- is large enough that another person or agent may continue it later
|
||||
|
||||
## Status Model
|
||||
|
||||
Prefer one of these status values near the top of the plan:
|
||||
|
||||
- `proposed`
|
||||
- `in-progress`
|
||||
- `blocked`
|
||||
- `completed`
|
||||
- `abandoned`
|
||||
|
||||
## Minimum Contents
|
||||
|
||||
Every plan should cover:
|
||||
|
||||
- goal
|
||||
- scope
|
||||
- constraints or non-goals
|
||||
- affected surfaces
|
||||
- implementation steps
|
||||
- validation strategy
|
||||
- status log
|
||||
|
||||
Start from [TEMPLATE.md](./TEMPLATE.md).
|
||||
Reference in New Issue
Block a user