skills.rest
TylerSimons1127
TylerSimons1127COMMUNITY
Explore all skills by this author →
GitHub

plan

Writes timestamped markdown implementation plans to .hermes/plans/ without executing code.

Updated Aug 21, 2026
Search Tags:#workflow#planning#tdd#documentation#markdown#implementation plan#task decomposition
One-click install
npx skills add https://github.com/TylerSimons1127/vibe --skill plan-tylersimons1127
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/TylerSimons1127/vibe/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/TylerSimons1127/vibe --skill plan-tylersimons1127

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you want a concrete, actionable implementation plan before any code is written, this Skill enforces a planning-only mode: it inspects the repository read-only and produces a detailed markdown plan saved under .hermes/plans/, preventing premature or accidental changes to your project. ## Core Features & Use Cases - Plan-Only Mode: Guarantees no code edits, commits, or mutating commands during the turn; the only file written is the plan markdown. - Structured Plan Craft: Enforces a proven plan format with goal, architecture, exact file paths, complete copy-pasteable code, TDD steps, verification commands, and bite-sized 2-5 minute tasks. - Execution Handoff: Plans are designed to be executed task-by-task via subagent-driven-development with two-stage review. - Use Case: Before building a multi-step feature like user authentication, invoke plan mode to get a saved, timestamped markdown document listing every file to change, failing tests to write first, and exact commit commands. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to .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 create an implementation plan before writing code?▼

Invoke plan mode with your feature request; the agent inspects the repo read-only and writes a markdown plan to .hermes/plans/ with a timestamped filename. The plan includes goal, approach, step-by-step tasks, exact file paths, and verification steps.

What should a good software implementation plan include?▼

A good plan includes the goal, architecture, tech stack, bite-sized tasks of 2-5 minutes each, exact file paths, complete copy-pasteable code, exact test commands with expected output, and commit steps. It follows DRY, YAGNI, and TDD principles.

Does plan mode modify or execute any project files?▼

No, plan mode is strictly read-only for the repository. It never edits project files, runs mutating commands, commits, or pushes; the only file written is the plan markdown saved under .hermes/plans/.

How are saved plans executed after planning?▼

Plans are executed using 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 not skipping even for simple features, since assumptions cause bugs. Full plans are most valuable before multi-step features, complex requirements, or delegating work to subagents.

Related Skills

Explore More Software Engineering Skills→
hughdbrownhughdbrown
1

hdb:design

Generate PRDs and staged task lists for software feature designs.

Community
Advanced
PlazaCCPlazaCC
2

subagent-driven-development

Execute implementation plan tasks with fresh subagents and two-stage reviews.

Official
Advanced
datasciencemonkeydatasciencemonkey
27

test-driven-development

Guide write-test-first cycles with a Red-Green-Refactor workflow.

Community
Basic
SkogAISkogAI
1

requesting-code-review

Dispatch the code-reviewer subagent to review code changes against plan and requirements.

Official
Basic