skills.rest
ewtodd
ewtoddCOMMUNITY
Explore all skills by this author →
GitHub

plan

Writes structured markdown implementation plans to .son-of-anton/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/ewtodd/son-of-anton --skill plan-ewtodd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/ewtodd/son-of-anton/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/ewtodd/son-of-anton --skill plan-ewtodd

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: no code edits, no mutating commands, just a well-structured markdown plan saved to your workspace. ## Core Features & Use Cases - Planning-Only Mode: Guarantees no implementation, file edits, commits, or external actions during the turn—only read-only inspection and plan authoring. - Structured Plan Format: Produces plans with goal, architecture, tech stack, bite-sized TDD tasks (2-5 minutes each), exact file paths, complete code snippets, and verification commands. - Workspace-Aware Saving: Saves plans as timestamped markdown files under .son-of-anton/plans/, compatible with local, docker, ssh, modal, and daytona backends. - Use Case: Before building a multi-step feature like user authentication, invoke plan mode to get a task-by-task breakdown with failing-test-first steps and commit points, then hand it off for subagent-driven execution. ## Quick Start Ask the agent to plan the implementation of your feature and save the plan to .son-of-anton/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, and the agent inspects the repository read-only, then writes a markdown plan with goal, architecture, bite-sized tasks, exact file paths, and test commands to .son-of-anton/plans/.

How to break a feature into small TDD tasks?▼

Structure each task as 2-5 minutes of work: write a failing test, run it to verify failure, write minimal implementation, run tests to verify pass, then commit. Each task targets one file with complete copy-pasteable code.

Does plan mode modify my project files?▼

No. Plan mode only writes the plan markdown file under .son-of-anton/plans/ and uses read-only commands for inspection. It never edits project code, runs mutating commands, commits, or performs external actions.

Where are plan files saved in the workspace?▼

Plans are saved as timestamped markdown files under .son-of-anton/plans/ relative to the active workspace, using the format YYYY-MM-DD_HHMMSS-slug.md. This works across local, docker, ssh, modal, and daytona backends.

When should I not use a full implementation plan?▼

Skip detailed planning only for trivial single-step changes. For multi-step features, complex requirements, or subagent delegation, a written plan prevents assumption-driven bugs and gives future implementers full context.

Related Skills

Explore More Software Engineering Skills→
eai-toolseai-tools

gofer_hydrate

Reverse-engineer specifications from existing codebases into research documents.

Official
Advanced
heidsoftheidsoft

subagent-driven-development

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

Community
Advanced
HanHan666666HanHan666666
10

subagent-driven-development

Delegate each plan task to isolated subagents with two-stage spec and quality reviews.

Community
Advanced
rmansrmans

scaffold-new-prototype

Create prototype documents with unique PROTO-### IDs and index registration.

Community
Intermediate