todo-create

Create persistent markdown todos with YAML frontmatter for status and dependencies.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill todo-create-ybbms777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: todo-create
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/todo-create
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill todo-create-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill solves the problem of losing critical work context, progress, and planned actions when development sessions end, which forces teams to re-research and re-plan long-running tasks every time they return to them.

Core Features & Use Cases

  • Persistent File-Based Storage: All todos are saved as markdown files that persist across sessions, so work context is never lost between sittings.
  • Structured Todo Templates: Pre-defined sections for problem statements, findings, proposed solutions, acceptance criteria, and work logs ensure all necessary context is captured for every work item.
  • Dependency & Status Management: Track todo status (pending/ready/complete) and dependencies between work items to manage complex multi-step projects and identify unblocked work.
  • Use Case: After a code review finds 12 missing test scenarios that will take 4 hours to fix, create a durable todo to track the work across multiple sessions without losing the review findings, proposed solutions, and acceptance criteria.

Quick Start

Use the todo-create skill to make a new p1 priority todo for fixing the N+1 query issue in the comment service, including the problem statement, proposed solutions, and acceptance criteria.

Frequently Asked Questions about todo-create

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

FAQPage Schema
How do I track technical debt and code review findings across multiple development sessions?

You can track technical debt and code review findings across sessions by creating durable, file-based markdown todos that persist context, dependencies, and progress instead of losing them when a session ends.

What is the best way to manage work items with dependencies for long-running tasks?

The best way to manage work items with dependencies is using file-based markdown storage with YAML frontmatter, which tracks status, priority, and dependencies to identify unblocked work for multi-step projects.

How do I create a persistent todo with structured sections for problem statements and acceptance criteria?

To create a persistent todo with structured sections, use a template that captures problem statements, findings, proposed solutions, acceptance criteria, and work logs in a markdown file with YAML frontmatter.

Can I track planned feature work and technical debt without losing context between sittings?

Yes, you can track planned feature work and technical debt without losing context by saving work items as durable markdown files that persist across sessions, ensuring all necessary context is captured.

Does file-based todo tracking support dependency management for complex projects?

File-based todo tracking supports dependency management by using YAML frontmatter to record todo status and dependencies between work items, helping you manage complex multi-step projects effectively.

When should I use file-based markdown todos instead of relying on session memory?

You should use file-based markdown todos when tasks span multiple development sessions, such as fixing multiple code review findings or addressing technical debt that requires tracking context over time.