Plan-driven

Use Plan when the task needs scope alignment, a reviewable approach, or explicit acceptance criteria before files are changed.

​

When to use Plan

• A feature spans several files or modules and the boundary must be agreed first.
• Several designs are possible and you want to compare tradeoffs before editing code.
• The team wants to review decomposition, risks, and verification steps.
• A design, API contract, or compatibility requirement must guide implementation.

​

Start a planned task

1. Open Add context in the task composer and select Plan. You can also type /plan and select Plan from the suggestions. The composer shows Turn off plan mode while it is active.
2. Describe the outcome, allowed scope, constraints, and verification requirements.
3. Review Qoder CN's planning response. When the task boundary is unclear, Qoder CN may ask follow-up questions; provide the information that affects scope, implementation choices, and validation.
4. For an engineering task that requires implementation, review the goals, affected files, steps, risks, and validation method before asking Qoder CN to proceed or revise the approach. A simple analysis or checklist may be returned directly in the conversation instead of opening a separate Plan work surface.

An actionable plan should cover goals and non-goals, relevant files or modules, implementation steps, risks and dependencies, and verification. Ask Qoder CN to revise missing sections before implementation. Qoder CN keeps the plan and execution in the same task. Review tool activity, changed files, tests, and evidence as work progresses. Open the code-review area when the task finishes and verify tests or builds before committing or pushing.

​

Plan versus Goal