| name | plan | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| description | Agent-first enterprise planning skill with a strict JSON CLI, deterministic validation, idempotent execution, and governance-aware rollback. | ||||||||
| license | MIT | ||||||||
| compatibility | opencode | ||||||||
| metadata |
|
- Use
opencode-plan; JSON is the machine contract. - Never guess. Validate before execute.
- Exit codes are authoritative:
0ok,1validation,2execution,3approval,4drift,5unknown. - Keep execution state under
.plan/and make execution idempotent. - Keep the skill docs and the packaged runtime aligned.
opencode-plan init --template <enterprise|agile|compliance> --out plan.jsonopencode-plan validate plan.json --strict --auto-fixopencode-plan simulate plan.json --iterations 10000opencode-plan execute plan.json --mode plan-only|plan-and-execute|continuousopencode-plan audit plan.json --format json|sarif|markdownopencode-plan rollback plan.json --to latest --dry-runopencode-plan schema --target plan|response
Every plan should include:
- outcomes / OKRs
- current state analysis
- decisions and assumptions
- phases with concrete tasks
- explicit dependency graph
- risk register and rollback plan
- done criteria and approvals
- metrics and learning fields
- Check for an approved plan.
- Validate the plan and repair trivial dependency cycles.
- Simulate risk and duration.
- Approve or request approval.
- Execute one bounded step at a time.
- Audit each state change.
- Roll back on drift.
- Learn from actual vs planned duration.
- Approval gates must be explicit.
- Audit records must be machine-readable.
- Drift must pause execution.
- Rollback must be dry-runable before apply.
The old stage-heavy design is still valid as the planning policy, but the runtime is now the packaged CLI under src/plan_cli/.