writing-plans

Generate step-by-step implementation plans with file modifications, code snippets, and commands.

Updated Mar 3, 2026
One-click install
npx skills add https://github.com/zhou533/UnVault --skill writing-plans-zhou533
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/zhou533/UnVault/tree/main/.claude/skills/writing-plans
Command: npx skills add https://github.com/zhou533/UnVault --skill writing-plans-zhou533

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of creating clear, actionable implementation plans for software development tasks, ensuring developers have all necessary context and instructions.

Core Features & Use Cases

  • Detailed Task Breakdown: Generates bite-sized, actionable steps for development tasks.
  • Contextual Information: Includes file paths, code snippets, testing instructions, and commit messages.
  • Use Case: When starting a new feature, use this Skill to generate a comprehensive plan that guides a developer through writing tests, implementing code, and committing changes, minimizing ambiguity.

Quick Start

Use the writing-plans skill to create an implementation plan for adding user authentication.

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

Generating detailed implementation plans involves creating step-by-step task breakdowns that specify exact file modifications, code snippets, testing instructions, and commit messages. This approach assumes minimal prior context, providing actionable steps and precise execution commands for developers.

How does task breakdown work with TDD and DRY principles?

Task breakdown with TDD and DRY principles works by structuring the development plan to sequentially guide developers through writing tests first, implementing the code, and committing changes. This ensures detailed steps adhere to test-driven and reusable code practices.

What is the best way to document code snippets and testing instructions for a development task?

The best way to document code snippets and testing instructions is to include them directly in the implementation plan alongside file paths and commit messages. This provides comprehensive contextual information that guides a developer through executing the required modifications.

Can I execute an implementation plan in a dedicated worktree or parallel session?

Yes, you can execute an implementation plan in a dedicated worktree or parallel session. The plan's output is specifically intended for this use case, allowing a subagent or parallel session to follow the precise commands and step-by-step instructions without missing context.

Do I need prior project context to follow a generated software development plan?

No, you do not need prior project context to follow a generated software development plan. The plan assumes minimal prior context for the developer by specifying exact file modifications, code snippets, and precise execution commands required to complete the task.