writing-plans

Generate implementation plans with goals, architecture, tasks, and file paths.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating ambiguous product requirements into a clear, executable sequence of tasks is time-consuming and error-prone. This skill provides a structured approach to planning software work, ensuring every step is well-scoped, testable, and ready for handoff to subagents or teammates.

Core Features & Use Cases

  • Structured plan templates: Defines a consistent header and task format to guide implementation.
  • Bite-sized tasks: Breaks work into 2-5 minute steps with precise file changes and tests.
  • TDD-driven workflow: Emphasizes writing failing tests first, then minimal code to pass, followed by verification.
  • Delegation to subagents: Facilitates task distribution and progress tracking across agents, teams, or copilots.
  • Documentation and commits: Encourages frequent commits and thorough documentation as tasks are completed.

Use Case: A team is adding a new feature and wants a plan that details which files to touch, what tests to write, and how to verify each step.

Quick Start

Create a new feature plan by breaking the work into bite-sized tasks, each with clear steps and a minimal code change.

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 complex software features into bite-sized tasks?

To break down complex software features into bite-sized tasks, generate a structured implementation plan that specifies goals, architecture, and a ready-to-execute sequence including specific file paths, tests, and commit notes. This approach scopes each step into 2-5 minute increments for reliable delivery.

What is a TDD-driven implementation plan and when do I need it?

A TDD-driven implementation plan is a structured document that sequences software work by emphasizing failing tests first, then minimal code to pass, followed by verification. You need this approach when translating ambiguous product requirements into a clear, executable, and testable task sequence.

How do I create an implementation plan for delegating tasks to subagents?

Create an implementation plan for subagent delegation by defining a consistent header and task format that breaks work into 2-5 minute steps with precise file changes. This structure facilitates task distribution and progress tracking across agents, teams, or copilots.

Can I use structured plan templates for design handoffs in software projects?

Yes, structured plan templates can be applied to design handoffs in software projects. They translate product requirements into a well-scoped, testable sequence of tasks, detailing which files to touch, what tests to write, and how to verify each step for reliable delivery.

What is the best way to translate product requirements into executable code changes?

The best way to translate product requirements into executable code changes is using a structured planning approach that breaks work into 2-5 minute steps. This ensures every step includes precise file modifications, required tests, and frequent commit documentation.

Does this approach to task breakdown work without specific external dependencies?

Yes, this task breakdown approach operates without external dependencies. It provides a structured methodology and plan template for scoping work into bite-sized, testable tasks, making it adaptable to various software project environments.