writing-plans

Create detailed implementation plans with file paths and testing steps.

1|Updated Mar 6, 2014
One-click install
npx skills add https://github.com/79yuuki/dotfiles --skill writing-plans-79yuuki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/79yuuki/dotfiles/tree/main/claude/skills/writing-plans
Command: npx skills add https://github.com/79yuuki/dotfiles --skill writing-plans-79yuuki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers turn unclear specifications and requirements into detailed implementation plans before making code changes, reducing missed steps and execution mistakes.

Core Features & Use Cases

  • Structured Planning: Creates comprehensive implementation plans with file mappings, architecture notes, task breakdowns, testing steps, and commit guidance.
  • Execution Readiness: Produces actionable plans designed for engineers with limited project context, including validation and self-review requirements.
  • Use Case: A developer receives a feature specification for an unfamiliar codebase and uses this Skill to create a complete step-by-step plan before implementation begins.

Quick Start

Use the writing-plans skill to create a detailed implementation plan for this feature specification before touching the code.

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 for a feature specification in an unfamiliar codebase?

To create an implementation plan for an unfamiliar codebase, decompose the feature specification into structured tasks with exact file paths, architecture notes, and testing steps. This ensures reliable execution preparation before making any code changes.

What should be included in a software implementation plan before coding begins?

A software implementation plan should include structured task decomposition, exact file paths, architecture notes, testing strategies, and validation steps. These elements ensure execution readiness for engineers with limited project context.

How do I decompose multi-step engineering tasks for reliable code changes?

Decompose multi-step engineering tasks by breaking down the feature specification into exact file mappings, testing strategies, and validation steps. This task decomposition produces actionable plans designed to guide code changes and prevent execution mistakes.

Does writing an implementation plan help with testing strategy and execution guidance?

Writing an implementation plan helps define testing strategy and execution guidance by requiring validation steps and self-review criteria before coding. This structured planning ensures code changes are validated against the feature specification.

When do I need to write an implementation plan for software engineering tasks?

You need an implementation plan for software engineering tasks when working with unfamiliar codebases, handling multi-step engineering tasks, or executing feature specifications. It provides the structured task decomposition and file planning required for reliable preparation.