to-tasks
To Tasks
Break agreed work into independently actionable tasks. Make each task a narrow, complete vertical slice and record the tasks that block it.
Stay on the user's current Git branch. Never create or switch branches while planning or publishing task documents. Derive task paths from the current branch or agreed work without changing branches.
Workflow
1. Gather context
- Work from the conversation and any supplied plan or wiki article.
- If the user supplies a file, issue, URL or wiki article, read its complete body and relevant comments before drafting tasks.
- Read applicable agent instructions and project planning conventions.
2. Explore the project when useful
Inspect the relevant code, tests, architecture decisions, and domain vocabulary unless the current context already establishes them. Use project terminology in task titles and descriptions. Look for prefactoring that would make later changes easy; schedule genuinely necessary prefactoring before the work it enables.
If docs/wiki contains an internal OKF wiki, read the indexes and concepts relevant to the work. Link each task to the canonical wiki entries that constrain or explain it. Do not invent wiki references when no relevant entry exists.