reversa-to-do

Decompose roadmap.md into atomic tasks with stable IDs and dependencies.

1|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-to-do-rdinda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-to-do
Source: https://github.com/Rdinda/FMA_Pontos/tree/main/.agents/skills/reversa-to-do
Command: npx skills add https://github.com/Rdinda/FMA_Pontos --skill reversa-to-do-rdinda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns a feature roadmap into an actionable execution plan by decomposing it into atomic tasks with stable IDs and clear dependencies.

Core Features & Use Cases

  • Atomic task decomposition: Breaks each roadmap item into single-turn, coherent actions with stable IDs (T001, T002, ...).
  • Dependency and parallelism mapping: Annotates which tasks depend on others and which can run in parallel using explicit columns and [//] markers.
  • Execution-ready actions.md: Generates a structured actions.md organized by the standard phases (Preparação, Testes, Núcleo, Integração, Polimento).

Quick Start

Use the reversa-to-do skill by typing /reversa-to-do to convert roadmap.md into a generated feature-dir/actions.md with numbered, dependency-aware tasks.

Frequently Asked Questions about reversa-to-do

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

FAQPage Schema
How do I convert a feature roadmap into an execution-ready task list?

To convert a feature roadmap into an execution-ready task list, you decompose roadmap items into atomic actions with stable IDs and explicit dependencies, generating a structured actions.md file organized by standard execution phases.

What is the best way to map task dependencies when decomposing a roadmap?

Mapping task dependencies during roadmap decomposition involves annotating which tasks must finish before others start and which can run in parallel. This is achieved using explicit columns and [//] markers within the generated actions.md file.

How does atomic task decomposition work in software engineering planning?

Atomic task decomposition breaks each roadmap item into single-turn, coherent actions. Each task receives a stable identifier like T001 or T002, ensuring clear tracking and explicit dependency mapping across the entire implementation workflow.

Do I need a roadmap.md file to generate an actions.md execution plan?

Yes, you need an existing roadmap.md file. The generation process enforces prechecks via active-requirements and roadmap existence before producing a deterministic actions.md under your specified feature directory.

Can I apply before-to-do and after-to-do hooks in my execution workflow?

Yes, you can apply before-to-do and after-to-do hooks according to the Reversa framework. These hooks execute alongside the generation of phase-based actions, ensuring your active-requirements are integrated into the workflow.

What are the limitations of generating actions.md from a feature roadmap?

The generation process strictly requires a pre-existing roadmap.md and enforces active-requirements prechecks. Without the roadmap file or required hooks specified by the Reversa framework, it cannot produce the deterministic actions.md output.