Persist durable work items as markdown todos in a canonical path.
npx skills add https://github.com/rethinkhealth/glion --skill todo-create-rethinkhealth
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
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.
Create a new todo by following the canonical path and using the provided template to initialize a pending item.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
Andreicr1Create durable markdown todos with frontmatter and a 3-part template.
merlyn-huntressManage file-based todos with markdown and YAML frontmatter.
udecodePersist work items as markdown files with structured templates and triage.
barkleesandersCreate and track file-based todos for code review feedback and technical debt.
