Coordinate structured feature planning by gathering context and producing a formal spec.
npx skills add https://github.com/WinnerWang971119/my_skills --skill plan-winnerwang971119
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
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.
Announce the planning process and draft a complete spec for user approval.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
hohai99Normalize raw project ideas into a consistent vision document.
AmiraultExecutes validated software specifications with automated build and test cycles.
orekyuuOrchestrate specification-driven development workflows from requirements to code implementation.
kgadekCoordinate subagent feedback to produce a structured SPEC document.
