writing-plans

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

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill writing-plans-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-plans
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/skills/software-development/writing-plans
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill writing-plans-mlt-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-step features often fail because requirements are vague and implementers lack context. This Skill turns a spec or requirements document into a comprehensive implementation plan where every task is small, explicit, and verifiable, so nothing is left to guesswork. ## Core Features & Use Cases - Bite-Sized Task Breakdown: Splits work into 2-5 minute tasks, each with one clear 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 Best-Practice Enforcement: Applies DRY, YAGNI, test-driven development, and frequent commits throughout the plan. - Use Case: Given a feature request like "add user authentication", produce a plan document saved to docs/plans/ with sequential tasks covering the User model, password hashing utility, and tests, ready for subagent-driven execution. ## Quick Start Ask the agent to write an implementation plan for your feature requirements, breaking the work 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 by reading the requirements and exploring the codebase, then design the approach and write sequential tasks. Each task should take 2-5 minutes and include exact file paths, complete code, commands with expected output, and a commit step.

How granular should tasks be in an implementation plan?

Each task should represent 2-5 minutes of focused work with a single action, such as writing one failing test or adding one small function. Large tasks like "build authentication" should be split into model creation, field additions, and utility functions.

Should I write a plan even for simple features?

Yes. The skill recommends planning even when a feature seems simple, because assumptions cause bugs and future maintainers need context. A written plan documents decisions and makes implementation obvious.

What should each task in an implementation plan include?

Each task needs an objective, exact file paths to create or modify, a failing test, the command to run it with expected output, minimal implementation code, a passing test verification, and a git commit step.

When should I not use a detailed implementation plan?

The skill is designed for multi-step features and complex requirements, so trivial one-line changes may not need a full plan. However, it warns against skipping planning just because work seems simple or is done solo.