todo

Generate implementation-ready TODO checklists with owners, dependencies, and acceptance criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/WannaCry081/React-Workflow-Starter --skill todo-wannacry081
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo
Source: https://github.com/WannaCry081/React-Workflow-Starter/tree/main/.agents/skills/todo
Command: npx skills add https://github.com/WannaCry081/React-Workflow-Starter --skill todo-wannacry081

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating a clear, implementation-ready TODO checklist from vague feature requests, bugs, or change notices so teams can start work with zero guesswork.

Core Features & Use Cases

  • Automatic Todo generation: Convert user stories, defects, or requests into structured, actionable task lists.
  • Context-aware planning: Tailor TODOs to project scope, priorities, and acceptance criteria.
  • Use Case: Given a feature request like "Add user profile avatars," generate a detailed set of tasks with ownership and dependencies.

Quick Start

Write or paste a feature request, bug report, or change description to generate a ready-to-run TODO checklist.

Frequently Asked Questions about todo

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

FAQPage Schema
How do I generate an actionable TODO checklist from a feature request?

To generate a TODO checklist from a feature request, input the user story or bug description. The Skill outputs a structured task breakdown with assigned owners, dependencies, and acceptance criteria for immediate execution.

What is the best way to break down a vague bug report into developer tasks?

Breaking down a vague bug report into developer tasks requires context-aware planning. The Skill parses defect descriptions to generate an executable task list with clear dependencies and acceptance criteria.

Can I generate task breakdowns and acceptance criteria for both frontend and backend changes?

Yes, you can generate task breakdowns and acceptance criteria for both frontend and backend changes. The Skill tailors TODOs across frontend, backend, and QA scopes from any change request.

Do I need to provide project scope and priorities to generate a structured TODO list?

You need to provide the feature request or bug description to generate a structured TODO list. The Skill applies context-aware planning, tailoring the generated tasks and acceptance criteria to the provided project scope and priorities.

How does automatic task generation handle dependencies and ownership for QA tasks?

Automatic task generation handles dependencies and ownership for QA tasks by analyzing the change request input. It outputs a complete plan identifying task owners, mapping dependencies, and defining acceptance criteria for handoff.