alex/dotfiles
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: structure planning and execution state

Browse Source
This commit is contained in:
alex wiesner
2026-03-13 21:36:55 +00:00
parent 9d7961f334
commit a3045255a7
6 changed files with 36 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
.config/opencode/skills/writing-plans/SKILL.md
View File

@@ -20,6 +20,14 @@ Every approved plan must include:
- Verification oracle
- Risks and open findings
When parallelization or phased verification matters, each lane must also specify:
- **Claimed files/areas** — paths or named surfaces the lane owns exclusively.
- **Dependencies** — which lanes (if any) must complete first.
- **Verification intent** — what will be checked and at what mode (`smoke` for intermediate checkpoints, `full` for final completion). Default to the shared mode rules in `AGENTS.md` when not otherwise specified.
The plan must give builder enough information to create the structured `executions/<slug>` note (lane claims, ownership, exit conditions, verification ledger shape) without guessing.
## Workflow
1. Gather enough evidence to remove guesswork.
@@ -33,3 +41,5 @@ Every approved plan must include:
- No ambiguous acceptance criteria.
- No hidden scope expansion.
- Verification is specific and runnable.
- Lane claims do not overlap in files or verification steps when parallel execution is intended.
- Verification mode (`smoke` or `full`) is stated or defaults are unambiguous for each checkpoint.