writing-plans

Convert product requirements into implementation plans with tasks and milestones.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/lightxue/dotfiles --skill writing-plans-lightxue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/lightxue/dotfiles/tree/main/agent/skills/writing-plans
Command: npx skills add https://github.com/lightxue/dotfiles --skill writing-plans-lightxue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing a feature plan from a spec often stalls teams waiting for a concrete blueprint. This Skill generates a complete, plan-first blueprint that outlines required files, tests, docs, and commits, enabling rapid, aligned execution.

Core Features & Use Cases

  • Plan generation from a spec: Converts a feature description into a structured plan with tasks and milestones.
  • File and task mapping: Proposes exact files to touch and how to decompose work into self-contained steps.
  • Plan documentation templates: Produces standardized plan documents ready for execution handoff and review.

Quick Start

Provide a feature specification and a detailed, task-by-task implementation plan will be generated.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I turn a product specification into an actionable implementation plan?

To turn a product specification into an implementation plan, provide the feature description to generate a structured blueprint with concrete tasks, milestones, and file touchpoints. This process ensures rapid, aligned execution by mapping exact files and decomposing work into self-contained steps.

How do I break down a feature spec into tasks and milestones for development?

To break down a feature spec into tasks, you convert the product requirement into a standardized plan document with milestones. This decomposes the work into self-contained steps, proposing exact files to touch and outlining tests and commits for execution handoff.

What is the best way to document file touchpoints and commit strategies for a software project?

The best way to document file touchpoints and commit strategies is by using a standardized planning template. This generates a plan-first blueprint that outlines required files, tests, and documentation, ensuring consistent handoffs and aligned team execution.

Can I generate a standardized plan document for execution handoff in multi-module projects?

Yes, you can generate a standardized plan document for execution handoff in multi-module projects. Providing a feature specification yields a comprehensive implementation plan with structured task breakdowns and frontmatter metadata for consistent team review.

Does implementation planning work without predefined software engineering dependencies?

Yes, implementation planning works without predefined software engineering dependencies. The plan generation operates directly on the provided feature specification to produce task breakdowns, milestones, and file mapping without requiring external components.