writing-plans

Generate structured implementation plans with TDD steps and exact file paths.

9|Updated Jul 1, 2026
One-click install
npx skills add https://github.com/Cyapstaye/Adame_ver.open --skill writing-plans-cyapstaye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/Cyapstaye/Adame_ver.open/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/Cyapstaye/Adame_ver.open --skill writing-plans-cyapstaye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of vague, incomplete, or poorly structured development tasks that lead to bugs and wasted time. It forces the creation of granular, actionable implementation plans that ensure every step is verified and documented.

Core Features & Use Cases

  • Bite-Sized Tasking: Breaks complex features into 2-5 minute, verifiable steps.
  • TDD Enforcement: Mandates the full test-driven development cycle for every code-producing task.
  • Use Case: When starting a new feature, use this skill to generate a comprehensive plan that includes exact file paths, specific test cases, and verification commands, ensuring the implementation is obvious and error-free.

Quick Start

Use the writing-plans skill to generate a detailed implementation plan for the new user authentication module.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I generate a TDD implementation plan for complex feature development?

To generate a TDD implementation plan, break complex feature development into bite-sized, verifiable steps using test-driven development principles. This process mandates exact file path referencing and specific test cases to ensure error-free code execution.

What is the best way to structure development tasks for subagent delegation?

Structuring development tasks for subagent delegation requires creating granular, actionable implementation plans with 2-5 minute verifiable steps. This ensures delegated work includes specific documentation formats and verification commands for obvious execution.

How does test-driven development planning improve refactoring workflows?

Test-driven development planning improves refactoring workflows by enforcing a full test-driven cycle for every code-producing task. This structured approach prevents vague tasking and ensures every modification is verified through specific test cases before completion.

Can I use TDD planning for both new features and code refactoring?

Yes, you can use TDD planning for both new feature development and code refactoring. The methodology applies structured, bite-sized tasking with verification-driven execution to any software development task requiring precise documentation and error-free implementation.

Why does implementation planning require exact file path referencing?

Implementation planning requires exact file path referencing to eliminate vague development tasks and prevent bugs. Precise documentation formats ensure every granular step is actionable, verifiable, and obvious for the executing developer or subagent.

What are the limitations of using bite-sized tasking for software development?

Bite-sized tasking for software development requires strict adherence to documentation formats and verification commands, which may overhead rapid prototyping. It is best suited for complex features and refactoring needing precise, error-free execution rather than quick experimental changes.