write-todos

Write self-contained todos with plan references, file inventories, and acceptance criteria.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/peerasak-u/pi-config --skill write-todos-peerasak-u
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-todos
Source: https://github.com/peerasak-u/pi-config/tree/main/skills/write-todos
Command: npx skills add https://github.com/peerasak-u/pi-config --skill write-todos-peerasak-u

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures every planning-derived todo is self-contained and actionable, so workers can execute without depending on the planning discussion.

Core Features & Use Cases

  • Self-contained todos: Each todo includes its plan reference, required files, constraints, and acceptance criteria.
  • Plan-to-work artifacts: Enforces explicit mapping from planning artifacts to executable work items.
  • Deterministic guidance: Provides a clear example and structure to prevent drift from architectural intent.

Quick Start

Create the first todo body exactly as described in the plan artifact and ensure it is self-contained.

Frequently Asked Questions about write-todos

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

FAQPage Schema
How do I create self-contained todos that workers can execute without reading the planning discussion?

To create self-contained todos, structure each task with explicit plan references, required file inventories, constraints, and acceptance criteria. This prevents drift and allows workers to execute work items independently without needing the original planning context.

Why do my planning-derived tasks drift from the original architectural intent?

Tasks drift when they lack deterministic guidance and strict structure. Enforcing clear constraints, required files, and acceptance criteria within each todo ensures workers execute precisely against the plan artifact without misinterpreting the architectural intent.

What is the best way to map planning artifacts to executable work items?

The best way to map planning artifacts to work items is by enforcing explicit references between them. Each todo must include the plan reference, file inventory, constraints, and acceptance criteria to maintain a deterministic link from plan to execution.

How do I structure a todo to include constraints and acceptance criteria?

Structure a todo by defining its plan reference, listing required files, specifying constraints, and detailing acceptance criteria. Providing a clear example alongside this strict structure prevents execution drift and ensures the task remains self-contained.

Do I need a plan artifact to generate actionable todos?

Yes, a plan artifact is required. You create the first todo body exactly as described in the plan artifact, ensuring it remains self-contained by incorporating explicit references, file inventories, and constraints to guide worker execution.

Can I use this approach to prevent task drift in automated planning workflows?

Yes, this approach prevents task drift in automated planning by applying deterministic guidance to every todo. It enforces strict structure with constraints and acceptance criteria, ensuring generated tasks remain aligned with the original plan artifact.