todo-create

Name: todo-create
Availability: InStock
Author: andreicr1

Create durable markdown todos with frontmatter and a 3-part template.

Updated Mar 14, 2026

Search Tags:#workflow #markdown #todo #triage #code-review #tracking

Ready to run

npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill todo-create-andreicr1

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: todo-create
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/todo-create
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill todo-create-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This skill provides a file-based system to create, track, and complete durable work items across multiple sessions, ensuring findings and tasks persist beyond a single editing session.

Core Features & Use Cases

Durable cross-session todos persisted as markdown files.
Canonical and legacy paths for creation, triage, and read operations.
Structured templates for consistent problem statements, findings, and action items.

Quick Start

Create a new durable todo by filling out the template under the canonical path and saving it to .context/compound-engineering/todos/.

Frequently Asked Questions about todo-create

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

FAQPage Schema

How do I track durable todos across multiple code editing sessions?▼

To track durable todos across sessions, you use a file-based markdown system that persists work items beyond a single editing session. This approach saves items to a canonical directory, ensuring tasks and findings survive session restarts.

What is the best way to triage code review findings into persistent tasks?▼

The best way to triage code review findings is using a structured markdown template with standard frontmatter. This template guides you through documenting the problem statement, findings, and action items to ensure consistent resolution tracking.

How do I create a cross-session todo file for engineering workflows?▼

You create a cross-session todo by filling out a 3-part markdown template and saving it to the canonical path at .context/compound-engineering/todos/. This enforces a standard structure for problem statements and action items.

Does this markdown todo system require any external dependencies?▼

No, this markdown todo system requires no external dependencies. It relies entirely on a file-based structure with standard frontmatter and canonical paths to organize and persist work items natively.

Why use a file-based todo system instead of standard task trackers for engineering workflows?▼

A file-based todo system keeps durable work items directly within your engineering workspace. This enforces a canonical write path and standard frontmatter, ensuring triage and resolution context persists locally alongside your code.

When do I need a cross-session todo tracking system for code reviews?▼

You need a cross-session todo tracking system when code review findings and action items must persist beyond a single editing session. It prevents losing triage context by saving structured markdown files to a canonical directory.