36 lines
1012 B
Markdown
36 lines
1012 B
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
|
|
|
|
## 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.
|