writing-plans

Generate multi-step implementation plans with files, code changes, and testing steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning multi-step software tasks before coding helps ensure clarity, completeness, and traceability for engineers, reducing rework and miscommunication.

Core Features & Use Cases

  • Generates a complete, executable implementation plan that lists files to touch, code changes, testing steps, and documentation tasks.
  • Breaks work into bite-sized tasks with clear priorities and commit goals for efficient teamwork.
  • Supports saving the plan to a standard location (project/plans/YYYY-MM-DD-<feature-name>.md) for consistent archival and onboarding.

Quick Start

Provide a comprehensive implementation plan for a new feature and save it to project/plans/YYYY-MM-DD-<feature-name>.md.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I plan multi-step software tasks before coding?

Plan multi-step software tasks before coding by generating a complete implementation plan that lists files to touch, code changes, testing steps, and documentation tasks, ensuring clarity and traceability.

What is the best way to break down a feature implementation plan for engineers?

The best way to break down a feature implementation plan is to divide work into bite-sized tasks with clear priorities and commit goals, reducing rework and miscommunication for efficient teamwork.

How do I document an implementation plan for a new software feature?

Document an implementation plan for a new software feature by saving it to a standard location at project/plans/YYYY-MM-DD-<feature-name>.md, ensuring consistent archival and onboarding.

Can I use a task plan for software refactors and bug fixes?

Yes, you can use a task plan for software refactors and bug fixes where clear execution steps and documentation are needed to ensure completeness and reduce rework.

Does an implementation plan require a specific file format to save?

Yes, an implementation plan requires saving as a Markdown file at project/plans/YYYY-MM-DD-<feature-name>.md with frontmatter-defined metadata for consistent archival.

What should be included in a software implementation plan?

A software implementation plan should include files to touch, specific code changes, testing steps, documentation tasks, task priorities, and commit goals for clear execution.