Missions

Use when the input is a user-approved design doc or implementation plan and the agent needs to turn it into an executable issues CSV before handing off to CSV execution.

Use when executing an existing task CSV and the agent needs to push all actionable rows to closed-loop completion without stopping between issues.

Use when the input is a complex task description that needs decomposition, persistence, and recovery before execution through a generated .mission CSV.

Use when the user wants to continue, resume, or recover interrupted mission work and the agent needs to locate unfinished CSV artifacts before execution resumes.

Use when a task may be a user-approved design/plan document, an existing task CSV, a markdown execution or investigation document, a long-running task description, or a recovery request and needs routing to the right mission sub-skill.

Use when the input is a markdown document and the agent must decide whether it belongs on the approved-doc execution path or the long-task execution path.