writing-plans

Creates implementation plans with bite-sized tasks, exact file paths, and complete code examples.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill writing-plans-kaminocorp
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/kaminocorp/hermes-alpha-hunter/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/kaminocorp/hermes-alpha-hunter --skill writing-plans-kaminocorp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step features often fail because implementers lack context, guess at file locations, or receive vague instructions. This Skill turns a spec or requirements document into a comprehensive implementation plan where every task is small, explicit, and verifiable, so execution becomes obvious rather than error-prone. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute tasks, each with one action such as writing a failing test, running it, implementing minimal code, and committing. - Complete Task Specifications: Every task includes exact file paths, copy-pasteable code, exact commands with expected output, and verification steps. - TDD and Git Discipline: Enforces test-driven development cycles, DRY and YAGNI principles, and frequent commits after each task. - Use Case: Given a requirements doc for a new authentication feature, produce a dated plan in docs/plans/ with sequential tasks covering the User model, password hashing utility, and tests, then hand off to subagent-driven-development for execution. ## Quick Start Ask the agent to write an implementation plan for your feature spec, breaking it into small TDD tasks with exact file paths and code.

Frequently Asked Questions about writing-plans

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

FAQPage Schema
How do I write an implementation plan for a multi-step feature?▼

Start from the spec or requirements, explore the codebase to understand structure, then write sequential tasks of 2-5 minutes each. Every task needs exact file paths, complete code, exact commands with expected output, and a commit step.

How to break down a complex coding task into small steps?▼

Split work so each step is one action: write the failing test, run it to confirm failure, write minimal code to pass, run tests again, then commit. Avoid grouping multiple files or behaviors into a single task.

What should a good implementation plan include?▼

A header with goal, architecture, and tech stack, followed by tasks containing objectives, exact file paths, complete copy-pasteable code, test commands with expected output, and verification steps. Apply DRY, YAGNI, and TDD throughout.

Can I skip planning for simple features?▼

No. The Skill explicitly warns against skipping plans even for simple features, because assumptions cause bugs and future maintainers need the documented context. Plans also matter when working alone.

When should I use test-driven development in a plan?▼

Use TDD for every task that produces code: write the failing test first, verify it fails, implement the minimal code, then verify it passes. This cycle is embedded in each task's step structure.