plan

Writes lightweight plan documents and reviews them for readiness to start work.

1|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/psw7205/skills --skill plan-psw7205
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/psw7205/skills/tree/main/skills/plan
Command: npx skills add https://github.com/psw7205/skills --skill plan-psw7205

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning documents often bloat into implementation contracts full of code details, or get reviewed for perfection instead of actual feasibility. This Skill keeps plans lightweight and direction-focused, and reviews them against a single question: will starting now hit a blocker? ## Core Features & Use Cases - Write Mode: Creates a plan file at docs/plans/YYYY-MM-DD-<topic>-plan.md covering goal, scope, ordered steps, risks, and open items, while hard-blocking code blocks, function signatures, and pinned file paths. - Automatic Independent Review: After saving, dispatches a general-purpose subagent that reads only the plan file and reports doubts with a verdict (green/yellow/red), with a local fallback review when no agent tool exists. - Review Mode: On user request, reviews a specified plan file or the most recent one in docs/plans/ using the same stateless checklist and verdict rules. - Use Case: Before starting a multi-step refactor, ask for a plan; the Skill drafts a one-page direction document, then an independent reviewer flags a missing dependency in step order so you fix it before writing any code. ## Quick Start Ask the assistant to write a plan for your upcoming task, for example by saying "plan 써줘" or "write a plan for migrating the auth module".

Frequently Asked Questions about plan

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

FAQPage Schema
How do I write a lightweight implementation plan before coding?▼

Ask for a plan with a phrase like "write a plan" or "plan 써줘". The Skill saves a Markdown file to docs/plans/ with goal, scope, ordered steps, risks, and open items, keeping it under one page and free of implementation details.

How do I check if a plan is ready to start?▼

Trigger Review mode with "is this plan ready?" or "plan 리뷰해줘". The Skill reviews the specified file or the latest one in docs/plans/ and returns only doubts plus a verdict: green to proceed, yellow conditional, or red needing rework.

What content is not allowed in the plan document?▼

Code blocks, function signatures, class structures, type definitions, pinned file paths with line numbers, error handling details, and future-improvement sections are hard-blocked. Conceptual mentions are fine; only decision-locking forms are rejected.

Does the plan review work without a subagent tool?▼

Yes. When no Agent or subagent tool is available, the Skill applies the same checklist locally, labels the result with "Fallback: local plan review", and re-reads the plan as a first-time reviewer before reporting doubts.

When should I skip writing a plan document?▼

Skip it for tasks taking only a few minutes. The Skill itself advises that a one-or-two-line summary plus immediate start is better than forcing a plan onto trivial work.