skills.rest
michaelvolz
michaelvolzCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

todo-create

Create structured markdown todo files in .context/compound-engineering/todos.

Updated Nov 11, 2023
Search Tags:#markdown#todo#triage#workflows#tracking#compound-engineering
One-click install
npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill todo-create
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: todo-create
Source: https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb/tree/main/.opencode/skills/ce/todo-create
Command: npx skills add https://github.com/michaelvolz/redmuffin.Blazor.StaticWeb --skill todo-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Coordinates durable work item tracking by keeping todos in structured Markdown files so that findings, technical debt, and planning steps persist across sessions without getting lost in ephemeral notes.

Core Features & Use Cases

  • Canonical storage: Always write new todos into .context/compound-engineering/todos/ while Legacy todos/ remains a read-only reference for older entries.
  • Structured lifecycle: Follow the prescribed filename convention, metadata frontmatter, and required sections (Problem Statement, Findings, Proposed Solutions, Recommended Action, Acceptance Criteria, Work Log) to capture each item consistently.
  • Workflow guidance: Includes detailed triage, dependency management, and completion steps plus integration hints for /ce:review, /todo-triage, and /todo-resolve scenarios, making it ideal for code review findings that need prioritization and follow-up.

Quick Start

Create a new todo markdown file in .context/compound-engineering/todos using the provided template and populate each required section for your work item.

Frequently Asked Questions about todo-create

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

FAQPage Schema
How do I persist code review findings across sessions using markdown?▼

You track durable todos by creating structured markdown files with metadata frontmatter and required sections like Problem Statement, Findings, and Acceptance Criteria, storing them under `.context/compound-engineering/todos/` to ensure persistence across sessions.

What is the best way to triage technical debt items from code reviews?▼

The best way to triage technical debt is using structured markdown workflows that capture proposed solutions, recommended actions, and dependency management steps, enabling prioritization and follow-up for findings generated during code reviews.

What sections are required when creating a structured todo markdown file?▼

Required sections for a structured todo markdown file include Problem Statement, Findings, Proposed Solutions, Recommended Action, Acceptance Criteria, and a Work Log, along with standard metadata frontmatter and a prescribed filename convention.

Where should durable todo files be stored for compound engineering workflows?▼

Durable todo files for compound engineering workflows should be created in the `.context/compound-engineering/todos/` directory, while a legacy `todos/` directory remains read-only for referencing older entries.

Can I use existing todos from a legacy directory when creating new work items?▼

Yes, existing todos in a legacy `todos/` directory remain accessible as a read-only reference, but all new work items must be created in the `.context/compound-engineering/todos/` directory to maintain proper lifecycle tracking.

Related Skills

Explore More Software Engineering Skills→
rethinkhealthrethinkhealth
6

todo-create

Persist durable work items as markdown todos in a canonical path.

Official
Intermediate
CuriousCrow123CuriousCrow123

file-todos

Track code review feedback and technical debt in markdown todo files.

Community
Intermediate
hackefellerhackefeller
1

file-todos

Manage file-based todos with markdown and YAML frontmatter.

Official
Intermediate
barkleesandersbarkleesanders
5

file-todos

Create and track file-based todos for code review feedback and technical debt.

Community
Intermediate