Sample Plan: Add Todo-Based Workflow

Goal

Create a small, traceable workflow for implementing a feature with clear todos, validation steps, and completion criteria.

Scope

• Identify the affected package or feature area.
• Make the smallest correct code change.
• Add or update tests only where they verify behavior.
• Run the smallest relevant checks before completion.

Todos

• Inspect the relevant files and existing patterns.
• Confirm whether the change belongs in Kilo-owned code or shared upstream code.
• Implement the minimal code change.
• Add or update targeted tests if behavior changes.
• Run formatting or linting if the touched package requires it.
• Run the smallest relevant typecheck or test command.
• Fix any failures introduced by the change.
• Summarize changed files and verification results.

Implementation Notes

• Prefer Kilo-owned directories for Kilo-specific behavior.
• If shared upstream files must be edited, keep the change narrow and add kilocode_change markers where required.
• Avoid broad refactors unless they are necessary for the requested behavior.
• Preserve existing style, naming, and package conventions.

Verification

• Run the targeted test for the changed behavior when available.
• Run the package typecheck if TypeScript code changes.
• Run any repo-specific guard required by touched files, such as annotation or source-link checks.

Completion Criteria

• The requested behavior is implemented.
• Tests or checks relevant to the change pass, or any inability to run them is documented.
• No unrelated files are modified.
• The final response includes a concise summary and verification status.