dev-todo

Convert backlog ideas into structured items ready for planning.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/AirMile/claude-config --skill dev-todo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-todo
Source: https://github.com/AirMile/claude-config/tree/main/skills/dev-todo
Command: npx skills add https://github.com/AirMile/claude-config --skill dev-todo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture backlog ideas and convert them into structured backlog items.

Core Features & Use Cases

  • Capture backlog items (features, changes, bugs, refactors, pages, components, a11y, performance) with optional thinking rounds.
  • Use with /dev-todo or /dev-todo [description] to capture an idea for the project backlog.
  • Bridge the gap between "I have an idea" and a backlog item ready for /dev-define.

Quick Start

Describe a new backlog item after typing /dev-todo [description] to capture it into the backlog.

Frequently Asked Questions about dev-todo

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

FAQPage Schema
How do I capture backlog ideas and convert them into structured items?

You can capture backlog ideas by providing a description, which converts them into structured backlog items ready for planning. This enforces a standardized item shape and supports optional thinking rounds to refine the capture.

What is the best way to structure feature definitions during ideation sessions?

Structuring feature definitions during ideation sessions is handled by applying a standardized item shape to your raw ideas. It bridges the gap between an initial idea and a pre-defined backlog item using optional thinking rounds.

Can I quickly capture bugs and refactors during meetings without breaking workflow?

Yes, you can quickly capture bugs, refactors, and changes during meetings without breaking your dev-workflow. The process converts quick captures into structured backlog items ready for immediate planning.

How do thinking rounds help with backlog management for software engineering?

Thinking rounds help with backlog management by applying optional, guided processing to your initial idea capture. This refines raw concepts into structured backlog items, ensuring they are fully prepared before feature definition.

Do I need a specific environment to link backlog items to downstream commands?

No specific environment is required to link backlog items to downstream commands. Captured items are automatically structured and prepared to link directly to downstream commands like feature definition processes.