write-todo

Generate todo specification files with Spec and Plan sections.

Updated Aug 23, 2026

Search Tags:#planning #documentation #task management #spec #todo

Ready to run

npx skills add https://github.com/justinmoon/configs --skill write-todo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-todo
Source: https://github.com/justinmoon/configs/tree/main/home/skills-disabled/write-todo
Command: npx skills add https://github.com/justinmoon/configs --skill write-todo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill transforms high-level user requests or planning discussions into detailed, actionable todo specifications, ensuring clarity and completeness in project execution.

Core Features & Use Cases

Structured Spec Generation: Creates markdown files with distinct 'Spec' and 'Plan' sections.
Actionable Planning: Outlines implementation steps with acceptance criteria and includes manual QA gates.
Use Case: After a brainstorming session, use this skill to document the agreed-upon features into a clear todos/feature-x.md file, ready for development.

Quick Start

Use the write-todo skill to create a todo spec for the new user authentication feature.

Frequently Asked Questions about write-todo

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

FAQPage Schema

How do I create a todo spec from a brainstorming session?▼

To create a todo spec from a brainstorming session, this Skill transforms high-level planning discussions into detailed markdown files. It structures the output into 'Spec' and 'Plan' sections, detailing intent, approach, and step-by-step implementation.

How do I generate a task management document with acceptance criteria?▼

To generate a task management document with acceptance criteria, this Skill creates a specification file in the `todos/` directory. It outlines implementation steps and includes manual QA gates to ensure project execution clarity and completeness.

What is the best way to document implementation steps for a new feature?▼

The best way to document implementation steps for a new feature is to use this Skill to generate a structured markdown file. It details the outcome, approach, and acceptance criteria, readying the `todos/feature-x.md` file for development.

Does this approach to writing planning specs require any specific dependencies?▼

Writing planning specs with this approach requires no specific dependencies. It directly generates a concrete todo specification file from user requests, structuring the output into distinct 'Spec' and 'Plan' sections.

Can I use this to structure a todo file for manual QA testing?▼

Yes, you can use this to structure a todo file for manual QA testing. The generated specification includes step-by-step implementation details with specific acceptance criteria and manual QA gates to validate the outcome.

What limitations exist when generating todo specifications from user requests?▼

A limitation when generating todo specifications is that the output relies entirely on the detail provided in the initial user request or planning discussion. It formats this input into a structured 'Spec' and 'Plan' markdown file without adding external context.