reversa-to-do

Decompose roadmaps into atomic tasks with sequential IDs, dependencies, and parallelism markers.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompõe roadmaps em ações atômicas com IDs sequenciais, dependências e marcador de paralelismo, para transformar um plano em uma lista de tarefas executável.

Core Features & Use Cases

  • Geração de ações atômicas com IDs estáveis (ex.: T001, T002, …) e diagrama de dependências.
  • Marcação de paralelismo para identificar tarefas que podem rodar em paralelo.
  • Saída direta em um arquivo actions.md pronto para revisão e acompanhamento.

Quick Start

Diga "/reversa-to-do" para transformar seu roadmap em uma lista de tarefas executável.

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 roadmap into an executable to-do list?

Task decomposition breaks down a roadmap into atomic tasks with sequential IDs, dependencies, and a parallelism marker. It applies a five-phase decomposition process to transform a high-level plan into an executable to-do list.

Can I mark parallelizable tasks when converting a roadmap into task management items?

Yes, converting a roadmap through task decomposition automatically marks parallelizable tasks. This identifies which atomic actions can run simultaneously, optimizing your project planning and execution timeline.

How do I generate sequential task IDs for project planning?

Generating sequential task IDs for project planning is handled automatically during roadmap decomposition. The process assigns stable identifiers like T001 and T002 to atomic tasks, ensuring clear dependency tracking and execution order.

What is the best way to track dependencies in a roadmap to-do list?

Tracking dependencies in a roadmap to-do list is best achieved by decomposing the plan into atomic tasks with sequential IDs. The output captures task relationships and parallelism markers directly in an actions.md file for review.

Do I need any specific tools to output my decomposed roadmap tasks?

No specific tools are required to output decomposed roadmap tasks. The process directly generates an actions.md file containing your atomic tasks, sequential IDs, and dependency diagrams, ready for immediate review and tracking.