writing-plans

Generate step-by-step implementation plans from product specifications.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill writing-plans-sammy9322
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/sammy9322/ventura-dental-facturacion/tree/main/.agents/skills/writing-plans
Command: npx skills add https://github.com/sammy9322/ventura-dental-facturacion --skill writing-plans-sammy9322

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of inconsistent, incomplete, or context-starved implementation work that occurs when engineers receive a feature spec without a clear, structured plan for execution. It ensures all necessary context, file paths, test steps, and code quality guardrails are documented upfront to reduce rework and speed up delivery.

Core Features & Use Cases

  • Structured Task Decomposition: Breaks down complex specs into bite-sized, independently testable tasks with explicit file creation/modification paths, code snippets, and test commands.
  • Best Practice Enforcement: Embeds core development principles like DRY, YAGNI, and TDD directly into every task to ensure consistent, maintainable, and well-tested code.
  • Use Case: For example, when building a new multi-currency payment processing module for the Ventura Dental clinic system, this Skill generates a full plan that tells the engineer exactly which backend API routes and frontend components to modify, what test cases to write, and how to commit changes, even if they have no prior context with the codebase.

Quick Start

Use the writing-plans skill to generate a complete, step-by-step implementation plan for the new patient billing feature described in the attached product specification.

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 step-by-step implementation plan for a new software feature?

To create an implementation plan, you decompose product specifications into bite-sized, independently testable tasks. This process provides explicit file modification paths, test commands, and code quality guardrails like DRY and YAGNI to ensure consistent execution.

How do I break down complex engineering specifications into testable tasks?

Breaking down engineering specifications involves task decomposition to isolate each requirement into independently testable units. Each generated task includes exact file creation paths, necessary code snippets, and specific test commands to verify functionality.

What is the best way to implement TDD workflows when planning a bug fix?

The best way to implement TDD workflows is by embedding test-driven development directly into every task within your implementation plan. This ensures each bug fix or system change includes explicit test cases before code modifications are committed atomically.

Can I generate a development plan for an existing codebase with no prior project context?

Yes, you can generate development plans for existing codebases with minimal prior context. The plan documents all necessary context, file paths, and test steps upfront, allowing engineers to implement system changes accurately without prior project knowledge.

How does task decomposition improve code quality for multi-step development?

Task decomposition improves code quality by enforcing DRY, YAGNI, and frequent atomic commits within each isolated step. Structuring development into independently testable tasks reduces rework and maintains consistent code standards across multi-step features.