writing-plans

Create structured implementation plans for software development tasks before code changes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers transform feature specifications and requirements into structured implementation plans before modifying code, reducing uncertainty and preventing incomplete execution.

Core Features & Use Cases

  • Implementation Planning: Creates detailed, file-specific plans with architecture notes, task breakdowns, testing steps, and commit guidance.
  • Engineering Workflow Guidance: Applies TDD-oriented decomposition, scope checks, and execution handoff patterns for software changes.
  • Use Case: When a developer receives a complex feature request, use this Skill to produce a step-by-step plan that another engineer can follow without prior project context.

Quick Start

Use the writing-plans skill to create a complete implementation plan for the provided feature 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 an implementation plan for software features before coding?

An implementation plan structures software development tasks using detailed task decomposition, explicit file paths, and validation steps. It transforms feature specifications into step-by-step workflows that guide reliable code changes and prevent incomplete execution.

What does TDD-oriented task decomposition mean for feature planning?

TDD-oriented task decomposition breaks feature specifications into structured, multi-step implementation workflows that include testing strategies and validation steps. It ensures code changes are planned with testability in mind, producing execution handoff instructions for reliable development.

How do I break down complex engineering requirements into execution handoff instructions?

Breaking down engineering requirements involves structured task decomposition with file-specific plans, architecture notes, and commit guidance. This produces step-by-step execution handoff instructions that another engineer can follow without prior project context, ensuring reliable development planning.

Can I use feature specifications to generate file-specific implementation plans?

Yes, feature specifications can be transformed into file-specific implementation plans that include explicit file paths, architecture notes, testing steps, and commit guidance. This structured planning approach reduces uncertainty and prevents incomplete execution of code changes.

What's the best way to plan multi-step implementation workflows for software development?

The best way to plan multi-step implementation workflows is through detailed task decomposition with explicit file paths, scope checks, and validation steps. This creates structured execution handoff patterns that ensure reliable development planning and prevent incomplete code changes.