writing-plans

Create detailed implementation plans with exact file paths and verification steps.

Updated May 24, 2026
One-click install
npx skills add https://github.com/anxiety135790/hermes-skills --skill writing-plans-anxiety135790
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/anxiety135790/hermes-skills/tree/main/software-development/writing-plans
Command: npx skills add https://github.com/anxiety135790/hermes-skills --skill writing-plans-anxiety135790

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you convert a feature idea or requirement into a clear, implementation-ready plan so developers can work without guessing.

Core Features & Use Cases

  • Task Breakdown: Splits complex work into small, sequential steps that are easy to execute and verify.
  • Implementation Detail: Specifies exact files to change, code to write, tests to run, and how to confirm success.
  • Workflow Guidance: Encourages disciplined planning practices such as DRY, YAGNI, TDD, and frequent commits for safer delivery.
  • Use Case: Use it when you need a detailed plan for a multi-step software feature before handing work to yourself, a teammate, or a subagent.

Quick Start

Ask for an implementation plan for your feature and include the requirements, constraints, and expected outcome.

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 software feature into implementation tasks?

Breaking down a complex software feature involves splitting requirements into bite-sized, sequential steps with exact file paths, commands, and testable verification steps for reliable execution.

What is the best way to write an implementation plan for a subagent with no context?

The best way to write an implementation plan for a subagent is to provide explicit task sequencing, copy-pasteable code examples, and TDD-oriented validation to ensure reliable execution without guessing.

How do I create a TDD-oriented workflow plan for a multi-step development task?

To create a TDD-oriented workflow plan, specify exact files to change, tests to run, and apply disciplined practices like DRY, YAGNI, and frequent commits for safer delivery.

Does this implementation planning method work for vague feature ideas?

Yes, this implementation planning method works for vague feature ideas by converting them into clear, implementation-ready plans where developers can work without guessing.

When do I need detailed task sequencing with exact file paths and commands?

You need detailed task sequencing with exact file paths and commands when delegating multi-step development work to an implementer who has little context, ensuring reliable execution.