plan

Generate structured markdown implementation plans for software development tasks.

Updated Jun 17, 2026

Search Tags:#workflow #design #planning #tdd #documentation #implementation

Ready to run

npx skills add https://github.com/cxnaive/hermes-agent-llbot --skill plan-cxnaive

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/cxnaive/hermes-agent-llbot/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/cxnaive/hermes-agent-llbot --skill plan-cxnaive

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of disorganized or incomplete project execution by forcing the creation of a concrete, step-by-step roadmap before any code is written.

Core Features & Use Cases

Structured Planning: Generates markdown-based implementation plans with clear goals, architecture, and tech stacks.
Task Granularity: Breaks complex features into bite-sized, 2-5 minute tasks following TDD principles.
Use Case: When starting a new feature like an authentication system, use this Skill to generate a detailed plan that includes specific file paths, test cases, and verification steps to ensure the implementation is predictable and error-free.

Quick Start

Use the plan skill to create a detailed implementation roadmap for adding a new user authentication module to the current project.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I create a structured implementation plan for a new software feature?▼

To generate an implementation plan, break complex features into bite-sized tasks following TDD principles. This approach produces a markdown roadmap with defined file paths, test cases, and verification steps for predictable execution.

What is test-driven development planning for software projects?▼

Test-driven development planning is structuring tasks so that verification and test cases are defined before code implementation. This ensures each step in the feature roadmap is granular, verifiable, and adheres to TDD principles within a workspace-aware environment.

How do I break down a complex authentication module into actionable coding tasks?▼

To break down complex features, generate a markdown plan that splits the work into 2-5 minute tasks. Each task specifies exact file paths, architecture details, and test cases to ensure error-free, predictable execution.

Does implementation planning require specific file paths and tech stack documentation?▼

Yes, structured implementation planning requires documenting specific file paths for all proposed changes. It also mandates documenting the tech stack and architecture to ensure the roadmap is actionable and verifiable.

When should I use a markdown implementation plan instead of just writing code?▼

Use a markdown implementation plan when starting new features to prevent disorganized project execution. It forces a concrete, step-by-step roadmap with test-driven verification before coding begins, preventing incomplete execution.