skills.rest
smrik
smrikCOMMUNITY
Explore all skills by this author →
GitHub

writing-plans

Generates test-driven implementation plans for software development tasks.

1|Updated Mar 5, 2026
Search Tags:#workflow#planning#tdd#development#documentation#engineering
One-click install
npx skills add https://github.com/smrik/ai-fund --skill writing-plans-smrik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/smrik/ai-fund/tree/main/skills/writing-plans
Command: npx skills add https://github.com/smrik/ai-fund --skill writing-plans-smrik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of ambiguous or poorly scoped development tasks by forcing 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 and correctness.
  • Use Case: When tasked with building a new data ingestion module, use this skill to generate a step-by-step plan that includes specific file paths, test cases, and commit messages for every component.

Quick Start

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

Generate a structured implementation plan that decomposes complex features into granular 2-5 minute actionable steps, mandating failing test creation before implementation to ensure TDD adherence and DRY architecture.

What is the best way to break down ambiguous development tasks into verifiable steps?▼

Break down ambiguous development tasks by generating a rigorous implementation plan that decomposes features into bite-sized 2-5 minute actionable steps, specifying file modifications and test creation for verifiable execution.

How does test-driven development planning handle file modifications and commit messages?▼

Test-driven development planning handles file modifications and commit messages by providing a standardized documentation template that generates specific file paths, test cases, and commit messages for every component in the workflow.

When do I need to use a structured TDD-ready implementation plan?▼

You need a structured TDD-ready implementation plan when tasked with building new software modules or features with ambiguous scope, ensuring verifiable steps and adherence to TDD principles before any code is written.

Can I generate implementation plans for data ingestion modules using this approach?▼

Yes, you can generate implementation plans for data ingestion modules by creating a step-by-step plan that includes specific file paths, test cases, and commit messages for every component based on provided requirements.

Related Skills

Explore More Software Engineering Skills→
DevQwietDevQwiet

writing-plans

Generate implementation plans for multi-step software development tasks.

Community
Advanced
danshapirodanshapiro
198

trycycle-planning

Generates step-by-step implementation plans with file modifications, tests, and execution commands.

Community
Intermediate
mymx2mymx2
4

ci-cd-and-automation

Configure GitHub Actions workflows to enforce quality gates on pull requests.

Community
Advanced
nicepkgnicepkg
276

agile

Guide Agile product management with Scrum, Kanban, and SAFe practices.

Official
Advanced