writing-plans

Generate test-driven development implementation plans with step-by-step instructions.

Updated Feb 24, 2026
One-click install
npx skills add https://github.com/chokky-education/science-club-web --skill writing-plans-chokky-education
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/chokky-education/science-club-web/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/chokky-education/science-club-web --skill writing-plans-chokky-education

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of disorganized or overly broad development tasks by forcing a structured, test-driven approach that ensures every feature is implemented with clear, bite-sized steps.

Core Features & Use Cases

  • TDD-First Planning: Automatically structures tasks to include failing tests, minimal implementation, and verification steps.
  • Standardized Documentation: Enforces a consistent header and task format for all feature plans, ensuring high-quality documentation.
  • Use Case: When starting a new feature, use this skill to generate a detailed roadmap that guides an AI agent through writing tests, implementing code, and committing changes in a disciplined, DRY-compliant manner.

Quick Start

Use the writing-plans skill to create 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 TDD implementation plan for a new software feature?

To generate a TDD implementation plan, provide your software engineering task details to obtain a step-by-step roadmap. This roadmap structures feature development into granular instructions for writing failing tests, minimal implementation, and verification.

What is test-driven development planning and when do I need it for my workflow?

Test-driven development planning is a structured approach that forces tasks into bite-sized, DRY-compliant steps. You need it when starting a new feature to ensure every development phase includes clear testing and version control instructions for consistent delivery.

How do I create standardized documentation for feature development tasks?

You create standardized documentation by enforcing a consistent header and task format for all feature plans. This ensures high-quality, uniform documentation that guides an AI agent through the entire development workflow.

Does this structured planning approach work for complex engineering modules?

Yes, this structured planning approach works for complex engineering modules by breaking down broad tasks into granular, step-by-step instructions. It guides you through writing tests, implementing code, and committing changes in a disciplined manner.

Why does my development workflow lack discipline during feature implementation?

Your development workflow lacks discipline due to disorganized or overly broad tasks. Forcing a structured, test-driven approach ensures every feature is implemented with clear, bite-sized steps, resolving inconsistent code delivery.