skills.rest
alexanderop
alexanderopCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

writing-plans

Generate zero-context implementation plans with exact file paths, code samples, tests, and verification steps.

4|1|Updated Jun 7, 2025
Search Tags:#planning#documentation#task management#software development#technical writing#implementation#engineering
One-click install
npx skills add https://github.com/alexanderop/MarkVim --skill writing-plans-alexanderop
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/alexanderop/MarkVim/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/alexanderop/MarkVim --skill writing-plans-alexanderop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the creation of highly detailed implementation plans, breaking down complex designs into bite-sized, actionable tasks for engineers. It ensures clarity, reduces ambiguity, and accelerates development by providing exact file paths, complete code examples, and verification steps, even for engineers with zero codebase context.

Core Features & Use Cases

  • Granular Task Breakdown: Divides implementation into small, manageable steps (2-5 minutes each) like 'Write failing test' and 'Commit'.
  • Zero-Context Guidance: Assumes minimal domain knowledge, providing all necessary information including exact file paths and full code snippets.
  • TDD Integration: Incorporates Test-Driven Development principles into each task, ensuring robust and verified implementations.
  • Structured Output: Generates plans with a consistent header and task structure, making them easy to follow and execute.
  • Use Case: After a design is finalized, use this skill to automatically generate a step-by-step implementation plan, complete with code examples and verification commands, ready for an engineer to execute without further clarification.

Quick Start

I have a design for a new API endpoint. Use the writing-plans skill to create a detailed implementation plan for an engineer with no prior knowledge of our codebase.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I create an implementation plan from a software design?▼

Implementation plans translate designs into bite-sized, actionable tasks with exact file paths, code snippets, and verification steps. Break down features into 2–5 minute steps—write tests, implement code, commit—so engineers can execute without clarification, even with zero codebase context.

What should an implementation plan include for an engineer new to the codebase?▼

Comprehensive plans provide exact file paths, complete code examples, test cases, documentation artifacts, and explicit verification commands. This eliminates ambiguity and enables engineers unfamiliar with the codebase to complete tasks independently while following TDD and DRY principles.

When should I use implementation plans in software development?▼

Use implementation plans after a design is finalized and ready for development. They're especially valuable when engineers have minimal domain knowledge or when multiple team members execute tasks in parallel, reducing back-and-forth and accelerating feature delivery.

Can implementation plans enforce development practices like testing and DRY?▼

Yes. Detailed plans integrate Test-Driven Development, DRY (Don't Repeat Yourself), and YAGNI (You Aren't Gonna Need It) principles into each task, ensuring code quality and reducing technical debt from the start of implementation.

How do implementation plans reduce ambiguity in task execution?▼

By providing granular breakdowns with explicit file modifications, code samples, and verification steps, plans eliminate guesswork. Engineers know exactly what to change, where to change it, and how to verify correctness without requesting clarification.

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

Designs specify what to build and why; implementation plans specify exactly how to build it—file paths, code lines, test assertions, and commit boundaries. Plans transform high-level designs into executable, bite-sized tasks ready for immediate development.

Related Skills

Explore More Software Engineering Skills→
sfinessfines

bmad-create-epics-and-stories

Transform requirements and architectural designs into structured epics and user stories.

Community
Intermediate
jnealey88jnealey88
12

verification-before-completion

Execute verification commands and document outputs as completion evidence.

Community
Advanced
zMynxxzMynxx

sdd-verify

Verify software changes against specifications, tasks, designs, and runtime test evidence.

Community
Advanced
hmpshmps

writing-plans

Generate implementation plans with exact file paths, commands, and verification steps.

Community
Intermediate