opencode-plan-detailed

Generates bounded implementation plans with verification commands and acceptance criteria for single changes.

2|1|Updated Jun 25, 2026
One-click install
npx skills add https://github.com/Consiliency/agent-harness --skill opencode-plan-detailed-consiliency
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opencode-plan-detailed
Source: https://github.com/Consiliency/agent-harness/tree/main/skills-src/opencode/opencode-plan-detailed
Command: npx skills add https://github.com/Consiliency/agent-harness --skill opencode-plan-detailed-consiliency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a bug fix, small feature, or targeted refactor request into an immediately implementable plan, so a single developer or one OpenCode thread can execute the change end to end without scope creep or missing verification steps. ## Core Features & Use Cases - Bounded Planning: Researches the repo with local reads (rg, git status, targeted file inspection) and produces a plan covering every file change, documentation impact, dependencies, and ordering. - Verification Contract: Every plan includes machine-checkable verification commands and testable acceptance criteria, optionally referencing roadmap goal IDs like EC-<ALIAS>-<N>. - Handoff & Reflection Artifacts: Writes a plan artifact, a repo-local handoff with frontmatter metadata, a manifest entry, and a per-run reflection for continuous skill improvement. - Use Case: Ask for a plan to fix a specific bug; the skill inspects the relevant files, enumerates each change with reasons, and returns a plan with acceptance criteria you can hand directly to an implementer. ## Quick Start Ask the agent to create a detailed implementation plan for your specific bug fix or small feature, for example: plan the change to add rate limiting to the login endpoint.

Frequently Asked Questions about opencode-plan-detailed

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a detailed implementation plan for a bug fix?▼

Invoke the skill with a clear task description; it researches the repo with git status, git log, and targeted rg searches, then returns a plan listing every file change, documentation impact, verification commands, and testable acceptance criteria.

When should I use a detailed plan instead of a phase roadmap?▼

Use a detailed plan when a single developer or one OpenCode thread should do the work end to end. The phase roadmap pipeline is for multi-phase efforts; this skill handles one bounded change, typically under about 8 source files.

Does the planning skill run tests or verification commands?▼

No. In planning-only runs it lists verification commands in the plan but does not execute tests, builds, or formatters, since those can dirty the repo. Commands run only when the user explicitly asks for validation or execution.

What artifacts does the plan produce besides the plan file?▼

It writes a repo-local handoff with frontmatter metadata, updates a latest.md pointer, appends a typed entry to plans/manifest.json, and writes a per-run reflection covering what worked and proposed improvements.

What are the limits of a bounded plan?▼

If a change would touch more than roughly 8 source files or more than 3 conceptually distinct changes, the skill recommends splitting it into multiple bounded plans rather than producing one large plan.