korenko-git/opencode-setup/writing-plans

Writing Plans

Read the relevant code, tests, instructions, and configuration before planning. For uncertain structure, use Task with subagent_type: explore and give it the question, scope, and required report. Resolve material ambiguity with the user through question before proposing implementation.

Write a plan that states the goal, affected files and ownership, ordered tasks, test changes, and verification commands. Each task should produce a small, independently verifiable outcome; include exact interfaces or acceptance criteria when downstream work depends on them. Prefer existing modules and evidence-based extractions over new abstractions.

Review the plan for requirement coverage, conflicting names or interfaces, and missing verification. Save it only when the user requests a plan file. Do not create worktrees or commits automatically. For execution, use executing-plans for sequential work or subagent-driven-development when tasks can be delegated safely.