todero-converting-plans-to-tasks

Convert Todero plans into executable issue graphs with dependencies and assignments.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/nabitllc/todero --skill todero-converting-plans-to-tasks-nabitllc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todero-converting-plans-to-tasks
Source: https://github.com/nabitllc/todero/tree/main/skills/todero-converting-plans-to-tasks
Command: npx skills add https://github.com/nabitllc/todero --skill todero-converting-plans-to-tasks-nabitllc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning an approved plan into actual work often produces bloated task lists, unclear ownership, and broken dependency chains. This Skill provides a disciplined method for translating any plan into a minimal, executable Todero issue graph where every task has a justified owner, explicit blockers, and a clear reason to exist. ## Core Features & Use Cases - Minimal Issue Graphs: Enforces a merge-back pass so only tasks with a qualifying boundary (different owner, parallel deliverable, hard dependency, review gate) become separate issues. - Dependency Wiring: Requires real blockers declared via blockedByIssueIds so Todero's executor auto-starts unblocked work and wakes dependents when blockers complete. - Specialty-Based Assignment: Directs you to look up company agents and their specialties before assigning, surfacing gaps instead of hiding them. - Use Case: After a planning issue is approved, use this Skill to produce a task matrix with owners, statuses, and blockers, create the issues in Todero, then verify the graph before closing the planning issue. ## Quick Start Ask the agent to convert the approved plan into Todero tasks with owners, blockers, and a justification for every separate issue.

Frequently Asked Questions about todero-converting-plans-to-tasks

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

FAQPage Schema
How do I convert a plan into tasks in Todero?

Start from one end-to-end task and add issues only for qualifying boundaries such as a different owner, parallel deliverable, hard dependency, or review gate. Write a task matrix with owner, status, blockers, and qualifying reason, then wire dependencies via blockedByIssueIds.

When should I split work into separate Todero issues?

Split only when a different specialist must own the work, a deliverable can run in parallel, a hard dependency needs its own lifecycle, or a review gate has an independent owner. Otherwise keep steps as checklists inside the parent issue.

How do task dependencies work in Todero?

Dependencies are declared through blockedByIssueIds on the dependent issue, not through parent/child nesting or prose. When a blocker reaches done, Todero's executor automatically wakes and starts the dependent task.

How should review tasks be structured in Todero?

Review tasks must instruct the reviewer to post findings on their own review issue and mark it done, since low-trust reviewers get a 403 on the parent issue. Wire the dependent issue's blockedByIssueIds to the review issue so the verdict wakes the right owner.

Does this planning method only apply to software development?

No, the same rules apply to marketing, research, ops, design, hiring, and finance work. The skill is domain-agnostic and only governs how plans become assigned, dependency-wired issues.