46 lines
1.8 KiB
Markdown
46 lines
1.8 KiB
Markdown
---
|
|
name: writing-plans
|
|
description: Planner workflow for producing execution-ready approved plans with explicit scope, lanes, and verification oracle
|
|
permalink: opencode-config/skills/writing-plans/skill
|
|
---
|
|
|
|
# Writing Plans
|
|
|
|
Use this skill when converting intent into an execution-ready `plans/<slug>` note.
|
|
|
|
## Required Plan Shape
|
|
|
|
Every approved plan must include:
|
|
|
|
- Objective
|
|
- Scope and out-of-scope boundaries
|
|
- Constraints and assumptions
|
|
- Concrete task list
|
|
- Parallelization lanes and dependency notes
|
|
- 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.
|
|
2. Decompose work into bounded tasks with clear owners.
|
|
3. Define verification per task and for final integration.
|
|
4. Check contract alignment with planner -> builder handoff rules.
|
|
5. Mark `Status: approved` only when execution can proceed without improvisation.
|
|
|
|
## Quality Gates
|
|
|
|
- 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.
|