todo-to-node

Convert a project TODO into a ResearchOps tree node with commands and checks.

174|17|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/CurryTang/Amadeus --skill todo-to-node
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-to-node
Source: https://github.com/CurryTang/Amadeus/tree/main/skills/todo-to-node
Command: npx skills add https://github.com/CurryTang/Amadeus --skill todo-to-node

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts a plain project TODO into a fully-specified ResearchOps tree node, enabling concrete planning from an initial idea and hypothesis.

Core Features & Use Cases

  • Clarification phase to resolve ambiguities by communicating with the user and collecting contextual details before node generation.
  • Automated node generation that maps a TODO to a node with fields like id, title, kind, assumptions, targets, commands, and checks.
  • Review and patch workflow that allows attaching the new node under an optional parent and patching it into the project plan.

Use Case: A project manager inputs a TODO with a title and hypothesis, and the system expands it into an executable ResearchOps node with concrete steps and acceptance criteria.

Quick Start

Provide a TODO item with id, title, and hypothesis, and optionally a parentNodeId, then request a new ResearchOps node following the defined steps.

Frequently Asked Questions about todo-to-node

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

FAQPage Schema
How do I convert a project TODO into an executable research plan node?

To convert a project TODO into an executable research plan node, provide the TODO's id, title, and hypothesis. The system clarifies ambiguities and generates a ResearchOps node with concrete commands, checks, and acceptance criteria.

Can I attach a generated ResearchOps node to an existing parent node in the project plan?

Yes, you can attach a generated ResearchOps node to an existing parent node. By providing an optional parentNodeId during generation, the system outputs a standardized payload suitable for patch operations directly into your project plan.

What is the clarification phase in ResearchOps node generation?

The clarification phase in ResearchOps node generation resolves ambiguities by communicating with the user. It collects contextual details before node generation to ensure the final executable node accurately reflects the initial TODO and hypothesis.

How do I expand a software project hypothesis into executable commands and checks?

You expand a software project hypothesis into executable commands and checks by inputting it as a TODO. The system automatically maps the hypothesis to a fully specified ResearchOps tree node containing targets, commands, and validation checks.

What specific fields are included in a generated ResearchOps tree node?

A generated ResearchOps tree node includes fields for id, title, kind, assumptions, targets, commands, and checks. These fields provide the concrete steps and acceptance criteria needed for executable project planning.