skills.rest
7757
7757COMMUNITY
Explore all skills by this author →
GitHub

plan

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

38|6|Updated Aug 14, 2026
Search Tags:#workflow#planning#tdd#documentation#markdown#task breakdown#implementation plan
One-click install
npx skills add https://github.com/7757/Fan-Browser-Agent --skill plan-7757
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/7757/Fan-Browser-Agent/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/7757/Fan-Browser-Agent --skill plan-7757

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When you want a concrete, reviewable implementation plan before any code changes happen, this Skill produces a detailed markdown plan saved to your workspace instead of executing anything, keeping you in control of the decision to proceed. ## Core Features & Use Cases - Plan-Only Mode: Inspects the repository with read-only operations and writes a plan file without editing project code, running mutating commands, or committing. - Structured Plan Format: Produces plans 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 task and offers handoff to subagent-driven-development for task-by-task execution. - Use Case: Before refactoring an authentication module, invoke plan mode to receive a timestamped markdown file under .fan/plans/ detailing every file to change, the tests to write, and the verification commands to run. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to .fan/plans/ without making any code changes.

Frequently Asked Questions about plan

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

FAQPage Schema
How do I get an implementation plan before writing code?▼

Invoke plan mode with your feature request and the agent writes a markdown plan to .fan/plans/ containing goal, architecture, and bite-sized tasks. It performs only read-only repository inspection and never edits project files or runs mutating commands.

What should a good implementation plan include?▼

A good plan includes exact file paths, complete copy-pasteable code, exact test commands with expected output, and verification steps for each task. Tasks should be bite-sized at 2-5 minutes each, following TDD with frequent commits.

Where are plan files saved in the workspace?▼

Plans are saved under .fan/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 my code or run commands?▼

No, plan mode is strictly read-only for inspection. It does not edit project files, run mutating terminal commands, commit, push, or perform external actions; the only file written is the plan markdown itself.

When should I not use plan mode?▼

Skip plan mode when you want immediate execution of a trivial change or quick fix. Plan mode is designed for multi-step features, complex requirements, and work you intend to delegate to subagents task-by-task.

Related Skills

Explore More Software Engineering Skills→
vessuxvessux
1

to-prd

Generate a formal PRD from conversation context and codebase exploration.

Community
Advanced
heidsoftheidsoft

subagent-driven-development

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

Community
Advanced
nachopalmerinachopalmeri

requesting-code-review

Route code changes to a specialized subagent for structured review.

Community
Intermediate
sjoerdbeentjessjoerdbeentjes

plan-mode

Explore codebases and create structured PLAN.md plans before implementation.

Community
Advanced