task-planning

Converts Todero issues into structured implementation plans with child tasks, blockers, and acceptance criteria.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill task-planning-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-planning
Source: https://github.com/nabitllc/todero/tree/main/packages/skills-catalog/catalog/bundled/todero-operations/task-planning
Command: npx skills add https://github.com/nabitllc/todero --skill task-planning-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large or ambiguous issues in Todero cannot be delegated or executed until they are broken into concrete, owned, and verifiable work items. This Skill turns an issue or request into a structured implementation plan that the Todero executor can actually run. ## Core Features & Use Cases - Structured Plan Documents: Produces a plan with goal, context reviewed, constraints, approach, work breakdown, acceptance bar, risks, and deferrals, saved as the issue's plan document via the Todero API. - Delegation-Ready Work Breakdown: Splits work into child issues with imperative titles, owner specialties, deliverables, acceptance criteria, and explicit blocked-by relationships. - Approval Workflow: Files the plan with PUT /api/issues/{issueId}/documents/plan, comments a summary, and creates a request_confirmation interaction when approval is required, moving the issue to in_review. - Use Case: A manager inherits an issue like "Build the onboarding flow" that is too large for one heartbeat. The Skill produces a plan with ordered child issues for engineering, design, and QA, each independently checkout-able, then requests confirmation before any subtasks are created. ## Quick Start Ask the agent to plan the current Todero issue and save the breakdown as the issue's plan document for review.

Frequently Asked Questions about task-planning

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

FAQPage Schema
How do I break down a large issue into child tasks in Todero?

Use the task-planning workflow to produce a work breakdown where each child issue has an imperative title, one owner specialty, deliverables, acceptance criteria, and explicit blocked-by relationships. Save it as the issue's plan document via PUT /api/issues/{issueId}/documents/plan.

How to write an implementation plan that an AI agent executor can run?

Include goal, context reviewed, constraints, approach, ordered work breakdown, acceptance bar, risks, and deferrals. Each child task must be understandable from its title and description alone, with real blocker chains rather than prose.

When should I not create a task plan for an issue?

Skip planning when the issue is a single small change shippable in one heartbeat, when it is a diagnostic issue needing root-cause analysis first, or when a current plan document already exists and only needs a minor update.

Does task planning create subtasks before the plan is approved?

No. Implementation subtasks are only created after the plan is accepted. When approval is required, the workflow posts a request_confirmation interaction bound to the plan revision and sets the issue to in_review.

Why do child issues fail at delegation time?

Children fail when their descriptions say "see parent", mix multiple specialties, lack acceptance criteria, or hide blocker chains in prose. Each child must be checkout-able by its owner from its title and description alone.