Create Task

Use as few output tokens as possible while completing the task correctly. Write in plain English. Apply this to documents, progress messages, and final replies.

Create a Todo or roadmap initiative when scope and work type are clear. Use one-task-management for ambiguous work, one-report-issue for bugs or feature requests, and one-initiative-brief when a brief needs shaping.

Instructions

• For developer/coding-agent work, state the goal and why, existing area/pattern to reuse, and done-when with real repo check commands; never invent them. Repo conventions win. Keep Todos to a few lines; use one-initiative-brief for fuller initiatives.
• Use create-initiative for planned product work tied to roadmap goals, companies, components, or team progress. It supports title, description, status, workspace, assignees, teams, parentInitiativeId, and taxonomyLabelIds.
• Use create-todo for simple personal follow-up, not as a substitute for roadmap work. It supports title, description, status, topic, and workspace.
• Set initiativeId on a Todo representing a delivered initiative slice; this creates a PART_OF relation.
• For completed implementation write-back, create the Todo with status: "Completed", then call add-task-comment with its task ID, workspace, and source: "skill":

**Changes**
- What changed: <delivered work>
- Why: <goal or root cause>