plan

Generate structured markdown implementation plans for software development tasks.

1|Updated Jul 31, 2026
One-click install
npx skills add https://github.com/icyzh/hermes-web --skill plan-icyzh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/icyzh/hermes-web/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/icyzh/hermes-web --skill plan-icyzh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of disorganized or poorly defined development tasks by enforcing a rigorous, test-driven planning process before any code is written.

Core Features & Use Cases

  • Standardized Planning: Generates consistent, markdown-based implementation plans saved to the project workspace.
  • TDD Enforcement: Mandates a test-driven development approach, ensuring every task includes a failing test, minimal implementation, and verification.
  • Use Case: When starting a complex feature, use this skill to break the work into bite-sized, 2-5 minute tasks that include exact file paths, code snippets, and verification commands.

Quick Start

Use the plan skill to generate an implementation plan for the new user authentication module based on the current project requirements.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I create an implementation plan for complex feature development?

To create an implementation plan for complex feature development, use a structured markdown planning process that breaks work into bite-sized, 2-5 minute tasks with exact file paths, code snippets, and verification commands. This ensures logical, test-driven execution before any code is written.

What is test-driven development planning and when do I need it?

Test-driven development planning is a rigorous process that mandates every task includes a failing test, minimal implementation, and verification. You need it when starting complex features or refactoring to prevent disorganized tasks and ensure clear, actionable execution.

How do I break down a refactoring task into bite-sized steps?

To break down a refactoring task into bite-sized steps, generate a standardized markdown implementation plan that defines 2-5 minute tasks. Each step must specify exact file paths, include code snippets, and provide verification commands for test-driven execution.

Can I generate implementation plans for subagent-driven workflows?

Yes, you can generate implementation plans for subagent-driven workflows. The planning process applies to workflows requiring clear, bite-sized task definitions by enforcing test-driven principles and exact file path specification for logical execution.

What's the best way to enforce TDD principles before writing code?

The best way to enforce TDD principles before writing code is to generate a structured markdown implementation plan that mandates every task includes a failing test, minimal implementation, and verification. This ensures logical, test-driven execution across the development workflow.