What problem does it solve? Turning a project goal into an actionable plan often produces vague tasks with no clear completion criteria or ordering. This Skill produces a plan in the exact fenced todero-plan block format that the Todero platform parses, with three to seven features and four to twelve tasks, each carrying a done-when line and dependency ordering. ## Core Features & Use Cases - Fixed plan block format: Outputs a single fenced block with a goal, features (name, why, done_when), and tasks (title, feature, output, optional after) that Todero parses directly. - Ordering rules: Enforces foundation-first, data-before-UI, core-before-edge, and shared-before-specific sequencing, using after only for true dependencies so independent features run in parallel. - Done-when discipline: Requires every feature to carry a done-when line and every task to name the check a reviewer looks at, splitting any feature with four or more separate checks. - Use Case: A product lead asks an agent to plan a new note-taking app; the agent returns a parseable plan block with six features, ten ordered tasks, and up to three open questions with recommended answers. ## Quick Start Ask the agent to plan your project using the todero plan block format, stating your goal in one sentence.
