plan

Writes actionable markdown implementation plans with bite-sized tasks and exact file paths.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing a multi-step feature or complex requirement, jumping straight into code leads to missed edge cases, vague assumptions, and rework. This Skill produces a concrete, step-by-step implementation plan saved as a markdown file, so execution becomes mechanical and reviewable before any code is written. ## Core Features & Use Cases - Plan-only mode: Inspects the repository with read-only commands and writes a plan without modifying project code, running mutating commands, or committing. - Structured plan format: Generates a markdown document with goal, architecture, tech stack, and bite-sized tasks (2-5 minutes each) containing exact file paths, complete copy-pasteable code, exact test commands with expected output, and commit steps. - TDD and execution handoff: Embeds test-driven development steps (failing test, minimal implementation, verification) in every coding task and hands off to subagent-driven-development for task-by-task execution with two-stage review. - Use Case: You ask for a plan to add user authentication. The Skill explores the codebase, then saves plans/2024-01-15_103000-add-auth.md with sequential tasks covering the User model, password hashing utility, failing tests, and verification commands. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan under the plans directory without writing any code.

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 before writing code?

Invoke plan mode with your feature request and the Skill explores the repository read-only, then writes a markdown plan under plans/ with sequential tasks, exact file paths, complete code, and test commands. No project files are modified during planning.

What should a good implementation plan include?

A good plan includes a goal statement, architecture summary, tech stack, and bite-sized tasks of 2-5 minutes each. Every task needs exact file paths, complete copy-pasteable code, exact commands with expected output, and a commit step.

How does plan mode work with test-driven development?

Each coding task in the plan follows the full TDD cycle: write a failing test, run it to verify failure, write minimal implementation code, then run the test to verify it passes. This ensures every task is verifiable before moving on.

Can the plan be executed automatically after it is written?

Yes, the plan hands off to the subagent-driven-development skill, which dispatches a fresh subagent per task with full context. Each task passes a spec compliance review and a code quality review before proceeding to the next.

When should I not use plan mode?

Plan mode is unnecessary for trivial single-line changes or pure questions, since it only produces a markdown document and never implements code. Use it before multi-step features, complex requirements, or subagent delegation where assumptions cause bugs.