task

Breaks down approved specs from .otto/ into prioritized, independently verifiable tasks and workflows for review.

14|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/brsbl/ottonomous --skill task-brsbl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task
Source: https://github.com/brsbl/ottonomous/tree/main/skills/task
Command: npx skills add https://github.com/brsbl/ottonomous --skill task-brsbl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating a complex specification into actionable work can be slow and error-prone; this Skill automatically converts a spec into atomic, prioritized tasks with clear dependencies to speed up planning and execution.

Core Features & Use Cases

  • Generate tasks by breaking approved specs into small, verifiable steps.
  • Organize tasks into sessions to enable parallel execution and clear progress tracking.
  • Define dependencies and priorities to prevent bottlenecks and support incremental delivery.
  • Provide a structured draft (including spec reference, sessions, and tasks) ready for review and approval.

Quick Start

Provide a spec ID to generate the initial task draft and begin the review workflow.

Frequently Asked Questions about task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a spec into atomic tasks for parallel execution?

Work-breakdown structure generation converts a complex specification into atomic, independently verifiable tasks. It organizes these tasks into sessions with defined dependencies and priorities to enable parallel execution and clear progress tracking.

How do I generate a task dependency draft from a specification?

Generating a task dependency draft requires providing a spec ID to analyze the specification file. The process outputs a structured JSON draft containing spec references, execution sessions, and atomic tasks ready for principal-engineer review and approval.

What is the best way to parallelize tasks from a software spec?

The best way to parallelize spec-driven tasks is by organizing the work-breakdown structure into discrete sessions with strict dependency mapping. This approach prevents execution bottlenecks and supports incremental delivery of independently verifiable tasks.

Do I need a principal-engineer review before executing generated tasks?

A principal-engineer review is required because the skill produces a draft JSON structure rather than final executable work. This review step ensures the generated sessions, atomic tasks, and dependencies are approved before parallel execution begins.

Can I use spec analysis to create sessions for automated review?

Spec analysis can be used to create sessions specifically designed for automated review. By breaking down specifications into atomic, independently verifiable tasks, the generated structure supports both automated verification and parallel execution workflows.