writing-plans

Create detailed implementation plans with file lists, task sequencing, and verification commands.

1|Updated Apr 27, 2026

Search Tags:#tdd #implementation planning #verification #task decomposition #handoff #packetization

Ready to run

npx skills add https://github.com/AIChuY/ai_workflow --skill writing-plans-aichuy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/AIChuY/ai_workflow/tree/main/writing-plans
Command: npx skills add https://github.com/AIChuY/ai_workflow --skill writing-plans-aichuy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an approved design or clear requirement into a concrete implementation plan before any code is changed. It removes ambiguity by spelling out files, sequencing, verification, and handoff decisions so execution can proceed without guesswork.

Core Features & Use Cases

File-level decomposition: Maps the exact files to create or modify and explains each file's responsibility.
Task sequencing: Breaks work into small, actionable steps with real dependencies and verification checkpoints.
Packet-ready planning: Supports splitting large efforts into execution packets when one session is not enough.
Use Case: You have an approved feature design and need a detailed plan that another engineer or agent can execute safely and consistently.

Quick Start

Ask the writing-plans skill to turn your approved design into a detailed implementation plan before you start coding.

Frequently Asked Questions about writing-plans

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

FAQPage Schema

How do I turn an approved software design into an actionable implementation plan?▼

To create an implementation plan, you decompose the approved design into file-level tasks, sequence them with dependencies, and define verification checkpoints to ensure buildable execution without placeholders.

What is task packetization for engineering handoff?▼

Task packetization splits large implementation plans into smaller execution packets, allowing work to be distributed across multiple sessions or handed off to another engineer or agent safely and consistently.

How do I break down a multi-step software feature into buildable tasks?▼

You break down a feature by mapping exact files to modify, defining each file's responsibility, sequencing bite-sized tasks with real dependencies, and specifying verification commands for each step.

Do I need a finalized design before creating an implementation plan?▼

Yes, you need an approved design or clear requirement before planning begins, because the process requires explicit file lists and task sequencing to remove ambiguity and guesswork from execution.

How do I add verification checkpoints to a software implementation plan?▼

You add verification checkpoints by specifying real verification commands after sequencing bite-sized tasks, ensuring each step of the implementation plan is tested before proceeding to the next.

What is the best way to plan multi-step engineering work for agent execution?▼

The best way is creating a packet-ready plan with explicit file lists, bite-sized tasks, and review checkpoints, ensuring an agent can execute the work safely without guessing at placeholders.