Generate self-contained todos with constraints and acceptance criteria from plan artifacts.
npx skills add https://github.com/v36372/pi-stuff --skill write-todos
Please help me install this Agent Skill. Skill: write-todos Source: https://github.com/v36372/pi-stuff/tree/main/skills/write-todos Command: npx skills add https://github.com/v36372/pi-stuff --skill write-todos
This skill helps teams generate clear, self-contained todos that preserve architectural intent so workers can execute tasks without needing context from planning discussions.
Provide a plan artifact and generate a ready-to-execute set of todos that preserve architectural intent.
High-intent search queries and answers about installing and using this skill.
Decomposing software architecture plans into actionable todos preserves architectural intent by embedding explicit constraints, example patterns, and verifiable acceptance criteria within each task body, ensuring workers execute design decisions without needing context from original planning discussions.
To prevent architectural drift when delegating tasks, generate todos that embed explicit constraints and verifiable acceptance criteria directly within each task body, ensuring workers execute design decisions without needing context from original planning discussions.
Plan artifacts should follow the plans/YYYY-MM-DD-<name>.md file path format to enable accurate task decomposition. This structured markdown format allows the system to extract architectural intent and generate self-contained todos with proper plan path references.
Yes, generated todos include explicit architectural constraints and verifiable acceptance criteria. Each todo body contains design guardrails, an example pattern, and expected outcomes as verifiable acceptance criteria to enforce architectural decisions and ensure measurable task completion.
Automated todo generation requires existing plan artifacts in the plans/YYYY-MM-DD-<name>.md format to function, limiting its use to teams already maintaining structured planning documents. It cannot generate architectural intent from scratch, but only decomposes and translates existing plans into work items.
xaionaroTranslate product or project specs into step-by-step implementation plans.
2zap2Outline self-contained ExecPlans with milestones, decisions, and validation criteria.
TonyQ-AIEvaluate software architecture design and code structure through rule-based engineering analysis.
JohnRobert-OlanoConvert project plans, specifications, or PRDs into actionable issues.
