writing-plans

Generate implementation plans with file paths, code samples, and tests.

1.2k|81|Updated Sep 5, 2024
One-click install
npx skills add https://github.com/udecode/dotai --skill writing-plans-udecode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/udecode/dotai/tree/main/.claude-plugin/plugins/plan/skills/writing-plans
Command: npx skills add https://github.com/udecode/dotai --skill writing-plans-udecode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates comprehensive, bite-sized implementation plans that empower any engineer, regardless of their codebase familiarity, to execute tasks efficiently. It eliminates ambiguity by providing exact file paths, complete code examples, and clear verification steps.

Core Features & Use Cases

  • Zero-Context Planning: Assumes minimal domain knowledge, ensuring every detail needed for implementation is included.
  • Bite-Sized Tasks: Breaks down complex work into small, actionable steps (2-5 minutes each) for smooth execution.
  • Integrated Testing Strategy: Automatically decides when to include deterministic unit tests based on task complexity.
  • Use Case: After a design is finalized, use this skill to generate a detailed implementation plan, complete with code snippets and testing instructions, ready for an engineer to pick up and execute.

Quick Start

Use the writing-plans skill to create an implementation plan for the new user profile page based on the attached design document.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I break down a complex engineering task into implementation steps?

Implementation plans divide complex work into bite-sized tasks (2-5 minutes each) with exact file paths, code samples, and verification steps. This approach eliminates ambiguity and lets any engineer execute efficiently regardless of codebase familiarity, ensuring all details needed for execution are documented upfront.

What should an implementation plan include for a new feature?

A comprehensive implementation plan includes zero-context guidance with exact file paths, complete code examples, deterministic unit tests based on task complexity, technical documentation, and verification steps. Plans are saved as structured task steps with commit guidance, enforcing DRY and YAGNI principles while supporting test-driven development.

Can I use implementation plans after finalizing a design?

Yes. Once your design is complete, implementation plans provide detailed task-level guidance ready for engineers to execute. They transform design documents into actionable steps with code snippets and testing instructions, bridging the gap between design and development.

How do implementation plans support test-driven development?

Plans automatically integrate testing strategy by deciding when to include deterministic unit tests based on task complexity. This built-in testing structure supports TDD workflows, ensuring verification steps and test examples are part of the implementation guidance from the start.

What's the difference between a design document and an implementation plan?

A design document outlines what to build and why; an implementation plan provides how to build it. Plans add exact file paths, code samples, verification procedures, and task breakdown—everything a developer needs to execute without additional context or guesswork.

Do implementation plans work for unfamiliar codebases?

Yes. Plans assume zero codebase context and include all details needed for execution: file structure, code examples, testing instructions, and documentation. This makes them effective for onboarding developers or handing work across teams without requiring deep domain knowledge.