todo-create

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

6|Updated Jan 29, 2023

Search Tags:#workflow #template #markdown #todo #triage #code-review #project-management

Ready to run

npx skills add https://github.com/rethinkhealth/glion --skill todo-create-rethinkhealth

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: todo-create
Source: https://github.com/rethinkhealth/glion/tree/main/.agents/skills/todo-create
Command: npx skills add https://github.com/rethinkhealth/glion --skill todo-create-rethinkhealth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Provides a file-based system to track durable work items such as code-review feedback, technical debt, and feature requests, across sessions by persisting them as markdown files in a canonical path and a read-only legacy path.

Core Features & Use Cases

Canonical (write) path: .context/compound-engineering/todos/
Legacy (read) path: todos/
File naming: {issue_id}-{status}-{priority}-{description}.md
Todo template: uses assets/todo-template.md to initialize new todos
Lifecycle & workflows: supports pending, ready, and complete statuses, cross-session work logs, dependencies, and triage via the todo-triage workflow

Quick Start

Create a new todo by following the canonical path and using the provided template to initialize a pending item.

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 feedback across sessions?▼

Track technical debt and code-review feedback across sessions by persisting items as markdown files in a canonical directory. This enforces a standardized naming pattern and uses a shared template to initialize new work items.

What is the best way to organize long-running feature requests in markdown?▼

Organize long-running feature requests in markdown by applying a canonical write path and a structured template. This enables a cross-session triage workflow with defined statuses like pending, ready, and complete, plus a dedicated work log.

How do I structure a markdown todo for project management triage?▼

Structure a markdown todo for project management triage using a standardized file name pattern that includes issue ID, status, priority, and description. A shared template initializes the item, supporting dependencies and a work log.

Can I use a legacy read path for existing markdown todos?▼

Yes, you can use a legacy read path for existing markdown todos. The system reads from a legacy directory while enforcing a canonical write path for creating and updating new items to maintain cross-session durability.

What statuses should I use for cross-session work item triage?▼

Use pending, ready, and complete statuses for cross-session work item triage. These defined statuses integrate with a work log to track progress on technical debt, feature requests, and code-review feedback.

When should I not use file-based markdown tracking for project management?▼

Avoid file-based markdown tracking for project management if your work items require real-time multi-user collaboration rather than durable cross-session persistence. This approach relies on a canonical file path and template structure without concurrent editing features.