plan-designer

Designs development plans with requirement clarification, impact analysis, and acceptance criteria.

5|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/A158Coke/WotbTools --skill plan-designer-a158coke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-designer
Source: https://github.com/A158Coke/WotbTools/tree/main/.agents/skills/plan-designer
Command: npx skills add https://github.com/A158Coke/WotbTools --skill plan-designer-a158coke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It turns a confirmed requirement into a concrete, evidence-based development plan before any code is written, preventing architecture conflicts, missed cross-layer impacts, and unverifiable deliverables. ## Core Features & Use Cases - Automatic requirement clarification: Runs the grill-me flow first to produce a requirement confirmation sheet, or skips it when requirements are already explicit. - Feasibility and impact scanning: Verifies the plan against existing code and docs using ripgrep, then walks a layer-by-layer checklist covering parsing, models, APIs, frontend locales, exports, tests, docs, and build/deploy. - Structured plan output: Writes a step-by-step development plan with file lists, verification methods, a not-to-do list, acceptance criteria, and open questions into docs/current-plan.md. - Use Case: Before adding a new replay statistic to the WoTB Tools project, invoke this Skill to confirm the requirement, check contract impact across backend and frontend, and produce an approved plan ready for implementation. ## Quick Start Ask the assistant to run plan-designer to design a development plan for your feature before any coding begins.

Frequently Asked Questions about plan-designer

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

FAQPage Schema
How do I create a development plan before writing code?

Invoke plan-designer with your feature idea. It first clarifies requirements through structured questioning, then scans existing code and docs for feasibility, and finally writes a step-by-step plan with acceptance criteria into docs/current-plan.md.

What does a development plan design workflow include?

The workflow covers requirement clarification, feasibility checks against the existing architecture, a layer-by-layer impact scan (parsing, models, API, frontend, export, tests, docs, build), risk and default decisions, and a written plan with a not-to-do list and verification steps.

Can I skip the requirement clarification step?

Yes. If docs/current-plan.md already contains a requirement confirmation sheet, or you have explicitly stated goals, scope, non-goals, and acceptance criteria, the grill-me phase is skipped and noted in the plan.

Does plan-designer write implementation code?

No. It explicitly forbids writing implementation code. The plan must be approved by the user first, and only then does development begin, keeping design and coding as separate phases.

When should I use plan-designer versus a code review skill?

Use plan-designer before development to design the approach and assess impact. Use a review skill like review-with-docs after changes are made to audit the implementation and synchronize documentation.