skills.rest
jakubbartnik
jakubbartnikCOMMUNITY
Explore all skills by this author →
GitHub

plan

Writes actionable markdown implementation plans with bite-sized tasks to .hermes/plans/ without executing code.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents vague or incomplete implementation guidance by producing a detailed, step-by-step markdown plan before any code is written, so implementation becomes obvious even for someone with zero codebase context. ## Core Features & Use Cases - Plan-Only Mode: Inspects the repository with read-only commands and writes a plan without editing project files, committing, or running mutating commands. - Structured Task Breakdown: Splits work into 2-5 minute tasks with exact file paths, complete copy-pasteable code, exact commands with expected output, and TDD verification steps. - Timestamped Plan Storage: Saves plans under .hermes/plans/ with a YYYY-MM-DD_HHMMSS-slug filename, then offers handoff to subagent-driven-development for execution. - Use Case: Before building a multi-step feature like user authentication, invoke plan mode to get a sequenced task list covering models, hashing utilities, tests, and commits that a subagent can execute task-by-task. ## Quick Start Ask the agent to plan the implementation of your feature, for example: create a plan for adding user authentication with tests, and it will save a detailed markdown plan under .hermes/plans/.

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 it will inspect the repository read-only, then write a markdown plan to .hermes/plans/ with bite-sized tasks, exact file paths, complete code, and verification commands. No project files are modified during planning.

What should a good implementation plan include?▼

A good plan includes a goal, architecture summary, tech stack, and sequential tasks of 2-5 minutes each. Every task needs exact file paths, complete copy-pasteable code, exact commands with expected output, and TDD verification steps.

Where are plan files saved in the workspace?▼

Plans are saved under .hermes/plans/ relative to the active workspace, using a timestamped filename like YYYY-MM-DD_HHMMSS-slug.md. This path works across local, docker, ssh, modal, and daytona backends.

Can plan mode modify or execute code in my repository?▼

No, plan mode is strictly read-only for the repository. It may inspect files with read-only commands but never edits project files, runs mutating commands, commits, or pushes. The only file written is the plan markdown itself.

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

After the plan is saved, execution is handed off to the subagent-driven-development skill, which dispatches a fresh subagent per task with two-stage review: spec compliance first, then code quality, proceeding only when both approve.

When should I skip writing a full implementation plan?▼

The skill recommends almost never skipping it, even for simple features, since assumptions cause bugs and future maintainers need guidance. It is especially required before multi-step features and subagent delegation.

Related Skills

Explore More Software Engineering Skills→
fray-cloudfray-cloud

write-a-prd

Interview users and analyze codebases to draft structured PRDs for GitHub issues.

Community
Advanced
involvexinvolvex

subagent-driven-development

Dispatch fresh subagents for independent plan tasks with automated two-stage review per task.

Community
Advanced
thisismynewfmail-uithisismynewfmail-ui

subagent-driven-development

Dispatch isolated subagents for implementation tasks with two-stage spec and quality reviews.

Community
Advanced
decninerdecniner

plan

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

Community
Intermediate