writing-plans

Generate structured implementation plans with test-driven steps for coding tasks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill solves the problem of vague or poorly structured development tasks by forcing the creation of a rigorous, step-by-step implementation plan before any code is written.

Core Features & Use Cases

  • Task Decomposition: Breaks complex requirements into bite-sized, 2-5 minute actionable steps.
  • TDD Enforcement: Mandates a red/green testing cycle for every feature to ensure code quality.
  • Use Case: When starting a new feature, use this skill to generate a detailed plan that maps out file changes, test cases, and commit points, ensuring an agent can execute the work autonomously without losing context.

Quick Start

Use the writing-plans skill to create an implementation plan for the new user authentication module based on the provided requirements.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate an implementation plan for a complex software feature?

To generate an implementation plan, you decompose complex software requirements into granular, actionable steps. This forces a rigorous, step-by-step plan that maps out file changes and test cases before any code is written.

What is test-driven development planning and how does it structure coding tasks?

Test-driven development planning structures coding tasks by mandating a red/green testing cycle for every feature. It breaks multi-step projects into bite-sized instructions with test verification and frequent commits to maintain code integrity.

How do I decompose requirements into test-driven steps for autonomous coding?

You decompose requirements by creating a detailed plan mapping out file changes, test cases, and commit points. This test-driven step decomposition ensures an agent can execute work autonomously without losing context.

Can I use this implementation planning approach for multi-step refactoring projects?

Yes, you can use this implementation planning approach for multi-step refactoring projects. It applies to any multi-step coding project requiring clear architectural boundaries and test-driven workflows to maintain code integrity.