skills.rest
luckybbjason1
luckybbjason1COMMUNITY
Explore all skills by this author →
GitHub

plan

Writes actionable markdown implementation plans with bite-sized tasks, exact paths, and complete code.

Updated Sep 9, 2026
Search Tags:#workflow#planning#tdd#markdown#task breakdown#implementation plan#subagent
One-click install
npx skills add https://github.com/luckybbjason1/trading --skill plan-luckybbjason1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/luckybbjason1/trading/tree/main/.hermes/skills/software-development/plan
Command: npx skills add https://github.com/luckybbjason1/trading --skill plan-luckybbjason1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns vague feature requests into concrete, step-by-step implementation plans that any developer or subagent can execute without guessing, eliminating ambiguity before any code is written. ## Core Features & Use Cases - Plan-Only Mode: Produces a markdown plan saved to .hermes/plans/ without modifying project code, running mutating commands, or committing changes. - Bite-Sized Task Breakdown: Decomposes work into 2-5 minute tasks with exact file paths, complete copy-pasteable code, exact commands with expected output, and TDD verification steps. - Execution Handoff: Structures plans for direct handoff to subagent-driven-development with spec compliance and code quality reviews. - Use Case: Before building a multi-step feature like user authentication, invoke plan mode to generate a timestamped plan covering the User model, password hashing utility, failing tests, and commit steps, then execute it task-by-task. ## Quick Start Ask the agent to plan the implementation of your feature in plan mode and save the resulting markdown plan under .hermes/plans/ 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 write an implementation plan before coding a feature?▼

Invoke plan mode with your feature request and it produces a markdown plan saved under .hermes/plans/ with a timestamped filename. The plan includes the goal, architecture, step-by-step tasks with exact file paths, complete code, and test verification commands.

What makes a good implementation plan for AI agents?▼

A good plan uses bite-sized tasks of 2-5 minutes each, exact file paths, complete copy-pasteable code, exact commands with expected output, and TDD cycles. If the implementer has to guess anything, the plan is incomplete.

Does plan mode modify my project files or run commands?▼

No. Plan mode only writes the plan markdown file under .hermes/plans/. It does not edit project code, run mutating terminal commands, commit, push, or perform external actions, though it may use read-only inspection.

How do I execute a plan after it is saved?▼

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

When should I skip writing a full implementation plan?▼

The skill recommends almost never skipping it, even for simple features, since assumptions cause bugs. It is especially required before multi-step features, complex requirement breakdowns, and delegating work to subagents.

Related Skills

Explore More Software Engineering Skills→
asarchamiasarchami
1

to-specs

Converts requirements and conversation context into structured specification documents.

Community
Intermediate
heidsoftheidsoft

subagent-driven-development

Dispatch fresh subagents per task with two-stage spec and code-quality reviews.

Community
Advanced
80portisfound80portisfound

writing-plans

Write implementation plans with bite-sized tasks, exact file paths, and complete code.

Community
Intermediate
FerroxLabsFerroxLabs
21

ferrox-fast

Apply trivial low-risk code changes directly without planning.

Community
Basic