Verified:GitHub

plan

Coordinate structured feature planning by gathering context and producing a formal spec.

Updated Apr 23, 2026

Search Tags:#planning #documentation #specification #risk-management #project-management #acceptance-criteria #feature-design

Ready to run

npx skills add https://github.com/WinnerWang971119/my_skills --skill plan-winnerwang971119

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/WinnerWang971119/my_skills/tree/main/plan
Command: npx skills add https://github.com/WinnerWang971119/my_skills --skill plan-winnerwang971119

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning is often the bottleneck between idea and implementation. This skill provides a structured framework to gather context, validate assumptions, and produce a complete, reviewable spec before any code is written.

Core Features & Use Cases

Phase-driven planning that guides context exploration, questions, assumption validation, and decision logging.
Multi-batch questioning to elicit requirements, constraints, risks, and dependencies.
Single, approved spec delivery with traceable decisions, scope boundaries, and handoff artifacts.

Quick Start

Announce the planning process and draft a complete spec for user approval.

Frequently Asked Questions about plan

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

FAQPage Schema

How do I create a structured project plan before starting implementation?▼

Structured project planning involves phase-driven context gathering and multi-batch questioning to validate assumptions. This produces a single, reviewable specification document with traceable decisions, scope boundaries, and handoff artifacts before any code is written.

What is the best way to document feature design and acceptance criteria for a new task?▼

Documenting feature design and acceptance criteria is best achieved through a formal spec generated by structured planning. It logs decisions, defines scope boundaries, and outlines task planning to ensure all requirements are reviewable before development.

How do I identify and manage risks and dependencies during feature planning?▼

Risk management during feature planning is handled through multi-batch questioning workflows that elicit requirements, constraints, and dependencies. This question-driven approach validates assumptions and logs risks into a formal specification document.

Can I use a phase-driven planning workflow for scoping complex multi-phase changes?▼

Yes, phase-driven planning workflows are designed for scoping complex multi-phase changes. They guide context exploration, assumption validation, and decision logging across multiple batches to produce a comprehensive, approved specification document.

Why does project planning bottleneck between idea and implementation?▼

Project planning bottlenecks between idea and implementation due to unstructured context gathering and unvalidated assumptions. A structured planning framework resolves this by producing a complete, reviewable spec with clear scope and acceptance criteria before coding begins.

Do I need to gather context and validate assumptions before drafting a project specification?▼

Yes, gathering context and validating assumptions is required before drafting a project specification. The planning process uses multi-batch questioning to explore constraints and dependencies, ensuring the final spec is complete and traceable.