skills.rest
tjsasakifln
tjsasakiflnCOMMUNITY
Explore all skills by this author →
GitHub

reversa-to-do

Decomposes a roadmap into atomic tasks with sequential IDs, dependencies, and parallelism markers.

1|Updated Jul 10, 2026
Search Tags:#planning#agent workflow#roadmap#task decomposition#spec-driven development#dependency tracking#atomic tasks
One-click install
npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-to-do-tjsasakifln
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reversa-to-do
Source: https://github.com/tjsasakifln/extra-cli/tree/main/.agents/skills/reversa-to-do
Command: npx skills add https://github.com/tjsasakifln/extra-cli --skill reversa-to-do-tjsasakifln

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a high-level roadmap into an executable task list is error-prone: tasks end up too coarse, dependencies are implicit, and parallelizable work goes unmarked. This Skill converts a roadmap.md file into a structured actions.md with atomic, trackable tasks. ## Core Features & Use Cases - Atomic decomposition: Breaks each roadmap item into tasks executable in a single agent turn, split across five standard phases (preparation, tests, core, integration, polish). - Stable IDs and dependency tracking: Assigns zero-padded IDs (T001, T002...) that are never recycled, with explicit dependency columns and a [//] marker for parallelizable tasks. - Confidence inheritance and summary: Carries over confidence indicators from the roadmap and reports totals, parallelizable count, and the longest dependency chain. - Use Case: After running /reversa-plan to produce a roadmap, invoke this Skill to generate an actionable checklist ready for /reversa-coding. ## Quick Start Type /reversa-to-do to decompose the current feature roadmap into an executable actions.md task list.

Frequently Asked Questions about reversa-to-do

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

FAQPage Schema
How do I break a software roadmap into atomic tasks?▼

Run the reversa-to-do skill after generating a roadmap.md. It splits each roadmap item into tasks small enough to complete in one agent turn, assigns zero-padded IDs like T001, and records dependencies and target files in a table.

What makes a task atomic in task decomposition?▼

A task is atomic when an agent can finish it in a single turn without human feedback. This skill splits any action with more than five logical subpoints, touching more than three unrelated files, or containing sequential phrasing like 'and then'.

What happens if roadmap.md is missing when running reversa-to-do?▼

The skill aborts with a clear message pointing to /reversa-plan instead of trying to fill in the roadmap itself. It also aborts toward /reversa-requirements if active-requirements.json is absent.

How are parallelizable tasks marked in the generated task list?▼

Tasks that touch different files and have no mutual dependencies are marked with [//] at the start of the line. The summary also reports the total count of parallelizable tasks and the longest dependency chain.

Can task IDs be reused or renumbered later?▼

No. IDs are never recycled, even if a task is removed in a later review. Renumbering only happens when the actions.md document is generated for the first time.

Related Skills

Explore More Software Engineering Skills→
Pabloprogramador23Pabloprogramador23

reversa-plan

Translate feature requirements into technical delta artifacts for legacy systems.

Community
Advanced
luicabref97luicabref97

sadd:subagent-driven-development

Dispatch fresh subagents for isolated implementation tasks with code-review checkpoints.

Community
Advanced
RuggeryRuggery

reversa-to-do

Decomposes a feature roadmap into atomic tasks with IDs, dependencies, and parallelism markers.

Community
Intermediate
prestariusprestarius
1

to-issues

Convert plans or backlogs into independent tracker issues with acceptance criteria.

Community
Intermediate