reversa-to-do

Convert a Reversa feature roadmap into an executable actions.md with dependencies.

1.5k|383|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/sandeco/reversa --skill reversa-to-do-sandeco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reversa-to-do
Source: https://github.com/sandeco/reversa/tree/main/agents/reversa-to-do
Command: npx skills add https://github.com/sandeco/reversa --skill reversa-to-do-sandeco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a feature roadmap into an executable task plan so AI coding agents can implement legacy-system changes safely and in a traceable order.

Core Features & Use Cases

  • Atomic action decomposition: Breaks roadmap items into single-turn, coherent tasks with stable sequential IDs (T001, T002, ...).
  • Dependency-aware execution: Records explicit dependencies and a primary target file per action to guide correct build order.
  • Parallelism signaling: Marks tasks that can run concurrently with [//] when they touch different files and do not depend on each other.
  • Guardrails for correct inputs: Fails fast if required Reversa state/requirements and the roadmap are missing.

Quick Start

Run /reversa-to-do to generate feature-dir/actions.md by decomposing feature-dir/roadmap.md into an actions list with dependencies and parallelism markers.

Frequently Asked Questions about reversa-to-do

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

FAQPage Schema
How do I decompose a legacy feature roadmap into executable agent actions?

It breaks roadmap items into single-turn, coherent tasks with stable sequential IDs like T001 and T002. Each atomic action records explicit dependencies and a primary target file to guide the correct build order for AI coding agents.

How does parallel execution work for AI coding tasks in a dependency graph?

The skill validates feature-dir/roadmap.md and fails fast if required Reversa state or requirements files are missing. It reads .reversa/state.json and .reversa/active-requirements.json to ensure proper environment setup before generating actions.md.

What's the best way to generate an actions.md file with phase tables from a roadmap?

It applies to forward planning workflows in Reversa when converting roadmap.md into actions.md for collaborative AI coding and implementation. It validates feature-dir/roadmap.md and uses the standard actions-template to write phase tables with parallelism annotations.

Do I need .reversa/state.json to decompose a roadmap into atomic actions?

Yes, the skill requires reading .reversa/state.json and .reversa/active-requirements.json to function. It applies guardrails that fail fast if required Reversa state, requirements, and the roadmap are missing.

Why does my task decomposition fail when converting roadmap.md into actions.md?

Task decomposition fails fast when required Reversa state or requirements files are missing. The skill needs .reversa/state.json, .reversa/active-requirements.json, and a valid feature-dir/roadmap.md to generate the executable task plan.