writing-plans

Generate structured test-driven implementation plans for complex software tasks.

21|9|Updated May 27, 2026

Search Tags:#workflow #planning #tdd #documentation #task-management #software-engineering

Ready to run

npx skills add https://github.com/cq112233/unibestX --skill writing-plans-cq112233

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of disorganized or poorly defined project execution by enforcing a structured, test-driven planning phase before any code is written.

Core Features & Use Cases

Task Decomposition: Breaks down large requirements into granular, 2-5 minute actionable steps.
TDD Enforcement: Mandates the creation of failing tests before implementation to ensure code quality.
Use Case: When tasked with building a new feature, use this skill to generate a comprehensive plan that outlines file changes, test cases, and implementation steps, ensuring the AI agent stays focused and avoids common pitfalls.

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 structure complex software development tasks into actionable plans?▼

Test-driven development planning mandates creating failing tests before writing implementation code. This ensures code quality and systematic progress verification by defining test cases and file changes upfront in the documented checklist.

What is the best way to break down a large feature requirement for AI agents?▼

The best way to break down a large feature requirement is through task decomposition into granular, actionable steps. This generates a comprehensive plan outlining file changes and test cases, ensuring the AI agent stays focused and avoids common execution pitfalls.

Does task decomposition for engineering workflows require architectural boundaries?▼

Before using a test-driven implementation plan, you need defined software requirements and a target architectural structure. Providing these inputs allows the plan to accurately map file changes, test cases, and granular 2-5 minute actionable steps for the workflow.

When do I need a test-driven implementation plan for software engineering?▼

You need a test-driven implementation plan for software engineering when executing multi-step workflows with complex requirements. It is essential when your project demands TDD, DRY principles, and systematic progress verification through documented checklists before coding begins.