writing-plans

Develop implementation plans with milestones and 2-5 minute tasks.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/walker-hzx/AI-Assistant --skill writing-plans-walker-hzx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/walker-hzx/AI-Assistant/tree/main/skills/writing-plans
Command: npx skills add https://github.com/walker-hzx/AI-Assistant --skill writing-plans-walker-hzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert a messy or incomplete specification into a clear, detailed implementation plan before any coding begins, reducing back-and-forth and rework.

Core Features & Use Cases

  • Structured planning: break down complex requirements into small, testable tasks (2-5 minutes each) with clear ownership.
  • Milestones & validation: define milestones and concrete validation criteria to track progress and quality.
  • Documentation output: save the plan to docs/plans/YYYY-MM-DD-<feature-name>.md for traceability and reuse.

Quick Start

Provide a feature name and requirements and I will generate a detailed implementation plan.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn feature specifications into actionable implementation plans?▼

To turn feature specifications into actionable implementation plans, provide the feature name and requirements to generate a structured breakdown with milestones, validation checkpoints, and granular tasks saved directly to docs/plans.

What is the best way to break down complex requirements into testable tasks?▼

Breaking down complex requirements involves splitting the work into small, testable tasks with a 2-5 minute granularity. This approach ensures clear ownership and defines concrete validation criteria to track progress and quality.

How do I define milestones and validation checkpoints before coding begins?▼

Defining milestones and validation checkpoints before coding requires capturing the initial requirements and outlining a structured task breakdown that specifies concrete validation criteria for each phase of the software project.

Can I use this for structured task splitting in software project coordination?▼

Yes, you can use this for structured task splitting in software project coordination. It applies to product features and any scenario requiring a structured task breakdown, ensuring requirements are captured and milestones are defined.

Where are the generated implementation plan documents saved?▼

Generated implementation plan documents are saved to docs/plans/YYYY-MM-DD-<feature-name>.md. This documentation output ensures traceability and allows teams to reuse the structured plans for future coordination.