plan

Generate markdown implementation plans with test-driven development steps.

Updated Jul 6, 2026

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

Ready to run

npx skills add https://github.com/ghufronbagaskara/agent-im --skill plan-ghufronbagaskara

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of vague or overwhelming project requirements by forcing a structured, bite-sized planning phase before any code is written.

Core Features & Use Cases

Structured Planning: Generates detailed, markdown-based implementation plans that include goals, architecture, and step-by-step tasks.
TDD Enforcement: Mandates a test-driven development cycle for every task, ensuring code quality and verification.
Use Case: When tasked with building a new authentication system, use this skill to break the feature down into 2-5 minute tasks, ensuring each step is verified with a failing test before implementation.

Quick Start

Ask the agent to create an implementation plan for the new user authentication feature by invoking the plan skill.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I break down complex software features into actionable implementation plans?▼

Implementation plans break complex software features into actionable roadmaps by generating structured markdown documents with specific goals, architecture, and sequential tasks. This forces a bite-sized planning phase before any code is written.

How do I enforce test-driven development when planning a new software project?▼

Test-driven development is enforced by mandating a TDD cycle for every task within the implementation plan. Each step requires verification with a failing test before actual implementation begins, ensuring consistent project execution and code quality.

What is the best way to structure an implementation plan for a new authentication system?▼

The best way to structure an implementation plan for an authentication system is to break the feature down into 2-5 minute sequential tasks. The plan must specify exact file paths and include test-driven validation steps for each task.

Can I use this planning approach for vague or overwhelming project requirements?▼

Yes, this planning approach is specifically designed to solve vague or overwhelming project requirements. It transforms complex goals into structured, bite-sized markdown roadmaps, requiring exact file path specification and sequential task validation before coding starts.

Does an implementation plan need to include exact file paths for every task?▼

Yes, an implementation plan requires exact file path specification for every task. This ensures precise execution and allows the test-driven development cycle to validate each sequential step accurately across the project architecture.

When should I not use a structured implementation plan for software development?▼

You should not use a structured implementation plan for simple, single-step modifications that require no architectural breakdown. The planning process is designed for complex goals needing sequential task validation and test-driven development enforcement.