skills.rest
Chensihakniroth
ChensihaknirothCOMMUNITY
Explore all skills by this author →
GitHub

plan

Writes actionable markdown implementation plans to .anakot/plans/ without executing code.

Updated Jun 7, 2026
Search Tags:#workflow#planning#tdd#markdown#task breakdown#implementation plan#plan mode
One-click install
npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill plan-chensihakniroth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/Chensihakniroth/ANAKOT-AGENT/tree/main/skills/software-development/plan
Command: npx skills add https://github.com/Chensihakniroth/ANAKOT-AGENT --skill plan-chensihakniroth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping straight into coding complex features without a plan leads to missed requirements, vague tasks, and rework. This Skill enforces a plan-only mode that produces a concrete, step-by-step implementation plan saved as a markdown file before any code is written. ## Core Features & Use Cases - Plan-Only Mode: Restricts the agent to read-only inspection and writing a single plan file, with no code edits, commits, or mutating commands. - Structured Plan Format: Generates plans with goal, architecture, bite-sized tasks (2-5 minutes each), exact file paths, complete copy-pasteable code, test commands, and verification steps. - TDD and Execution Handoff: Embeds test-driven development cycles and frequent commits into every task, then hands off to subagent-driven-development for task-by-task execution. - Use Case: Before building a multi-file authentication feature, invoke plan mode to get a timestamped markdown plan under .anakot/plans/ detailing every file to create, failing tests to write, and commit steps. ## Quick Start Ask the agent to plan the implementation of your feature instead of executing it, and it will save a detailed markdown plan under .anakot/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 the agent inspects the repository with read-only commands, then writes a markdown plan to .anakot/plans/ containing goal, architecture, bite-sized tasks, exact file paths, and complete code.

What should a good software implementation plan include?▼

A good plan includes the goal, current context, step-by-step tasks of 2-5 minutes each, exact file paths, complete copy-pasteable code, test commands with expected output, verification steps, and risks. Each coding task follows a full TDD cycle.

Where are plan files saved in the workspace?▼

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

Does plan mode modify or execute any project code?▼

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 a full implementation plan?▼

The skill recommends planning before any multi-step feature, but trivial single-line fixes may not need one. However, it warns against skipping plans even for seemingly simple features, since unstated assumptions commonly cause bugs.

How is a saved plan executed after planning?▼

After saving, the plan is executed using 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.

Related Skills

Explore More Software Engineering Skills→
WirasmWirasm
2.2k

prp-plan

Creates implementation-ready plans from PRDs, issues, or descriptions using codebase evidence.

Community
Advanced
heidsoftheidsoft

subagent-driven-development

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

Community
Advanced
pageelpageel
48

TDD Guidelines

Enforce Red-Green-Refactor cycles with evidence-logged FAIL→PASS test validation.

Official
Advanced
metalspawnmetalspawn

plan

Develop structured implementation plans for code changes through codebase exploration and critical review.

Community
Advanced