writing-plans

Name: writing-plans
Availability: InStock
Author: sunmin-oss

Generate test-driven implementation plans with granular tasks and commit sequences.

1|Updated Oct 12, 2025

Search Tags:#workflow #planning #tdd #development #implementation #engineering

Ready to run

npx skills add https://github.com/sunmin-oss/sunmin-oss --skill writing-plans-sunmin-oss

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of disorganized or incomplete development by enforcing a rigorous, test-driven implementation plan before any code is written.

Core Features & Use Cases

Bite-Sized Tasking: Breaks complex features into granular, 2-5 minute actionable steps.
TDD Enforcement: Mandates the creation of failing tests before implementation to ensure code quality.
Use Case: When starting a new feature, use this skill to generate a comprehensive roadmap that includes exact file paths, specific test cases, and commit messages, ensuring the developer stays focused and follows best practices.

Quick Start

Use the writing-plans skill to generate an 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 test-driven implementation plan for a new software feature?▼

To generate a test-driven implementation plan, break complex features into 2-5 minute actionable steps that mandate failing tests before implementation, ensuring strict adherence to TDD, DRY, and YAGNI principles.

What is the best way to structure bite-sized development tasks in an unfamiliar codebase?▼

The best way to structure bite-sized development tasks is creating a granular roadmap with exact file paths, specific test definitions, and commit sequences, keeping developers focused on 2-5 minute increments.

Can I use this planning workflow to define exact commit sequences before writing code?▼

Yes, you can use this planning workflow to define exact commit sequences before writing code by generating a comprehensive roadmap that includes specific test cases, file modifications, and structured commit messages.

Does this implementation plan enforce DRY and YAGNI principles for software engineering?▼

Yes, this implementation plan enforces DRY and YAGNI principles by mandating a rigorous, test-driven roadmap before any code is written, ensuring code quality and preventing over-engineering in new or unfamiliar codebases.

When do I need a TDD-ready implementation plan for my development workflow?▼

You need a TDD-ready implementation plan when starting a new feature to prevent disorganized development, ensuring you follow best practices with granular action items and failing tests created before implementation.