research-tasking

Generate a structured TODO.yaml from ANALYSIS.md for research task planning.

23|2|Updated Jun 9, 2025
One-click install
npx skills add https://github.com/kaptinlin/gozod --skill research-tasking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-tasking
Source: https://github.com/kaptinlin/gozod/tree/main/.agents/skills/research-tasking
Command: npx skills add https://github.com/kaptinlin/gozod --skill research-tasking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts ANALYSIS.md into a structured TODO.yaml, turning research planning into concrete, executable tasks.

Core Features & Use Cases

  • Reads ANALYSIS.md to extract module-level research goals and priorities.
  • Generates exactly one TODO.yaml task per module (e.g., R01, R02) with titles, descriptions, and a false-complete flag.
  • Writes the resulting TODO.yaml to the project root and aligns task formatting with the referenced template.

Quick Start

Run the research-tasking skill after ensuring ANALYSIS.md exists at the project root.

Frequently Asked Questions about research-tasking

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

FAQPage Schema
How do I convert ANALYSIS.md into structured research tasks?

To convert ANALYSIS.md into structured research tasks, you need a tool that reads the file and outputs a TODO.yaml. This automation creates one task per module with titles, descriptions, and a false-complete flag for tracking.

What is the best way to automate research planning from a markdown analysis file?

Automating research planning from a markdown file involves generating a structured TODO.yaml. This approach extracts module-level goals and priorities, creating concrete executable tasks aligned with your template formatting.

Can I generate a TODO.yaml file from ANALYSIS.md for project task tracking?

Yes, you can generate a TODO.yaml file from ANALYSIS.md for project task tracking. The automation writes the resulting file to your project root, assigning metadata like R01 and R02 to each module task.

Does research task automation work without existing module definitions?

No, research task automation requires an existing ANALYSIS.md file at the project root. It applies when research tasks need to be created and extracts module-level goals directly from this document.

How do I structure research TODOs from a markdown analysis document?

You structure research TODOs by generating a YAML file with one task per module. Each task includes a title, description, and a false-complete flag, written to the project root for execution.

Why does my generated YAML research plan only include module-level tasks?

Your generated YAML research plan only includes module-level tasks because the automation extracts goals and priorities directly from the modules defined in your ANALYSIS.md, outputting exactly one task per module.