create-plan

Interview stakeholders and generate a structured PLAN.md for coding tasks.

19|4|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/wunki/amplify --skill create-plan-wunki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plan
Source: https://github.com/wunki/amplify/tree/main/skills/create-plan
Command: npx skills add https://github.com/wunki/amplify --skill create-plan-wunki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill transforms vague user requests or requirements into clear, structured, and actionable implementation plans, preventing scope creep and ensuring a solid foundation before development begins.

Core Features & Use Cases

  • Deep Interviewing: Asks targeted questions to fully understand the user's goal, context, and constraints.
  • Structured Planning: Generates plans with defined scope, success criteria, assumptions, and atomic action items.
  • Use Case: When tasked with building a new authentication module, this Skill will interview you about security requirements, user flows, and existing systems, then output a PLAN.md detailing steps like "Implement OAuth 2.0 flow," "Write unit tests for token generation," and "Add integration tests for login endpoint."

Quick Start

Use the create plan skill to generate a plan for implementing a user profile editing feature.

Frequently Asked Questions about create-plan

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

FAQPage Schema
How do I create an implementation plan from vague project requirements?

To create an implementation plan from vague requirements, this Skill interviews stakeholders to extract intent, context, and constraints, then generates a structured PLAN.md file decomposing the work into atomic, verifiable tasks.

What is the best way to scope a coding task and prevent scope creep before development?

Scoping a coding task and preventing scope creep involves deep interviewing to understand goals and constraints, then outputting a structured plan with defined success criteria, assumptions, and atomic action items.

How does task decomposition work for complex software engineering modules?

Task decomposition for complex software engineering works by thinking deeply about the goal and context, then breaking down the implementation into atomic tasks like writing unit tests and adding integration tests within a PLAN.md file.

Can I generate a step-by-step project management plan for a new authentication module?

Yes, you can generate a step-by-step project management plan for an authentication module by defining security requirements and user flows during the interview phase to produce verifiable action items.

What format does the generated project plan use for step-by-step execution?

The generated project plan uses a PLAN.md file format containing defined scope, assumptions, and atomic action items that can be executed step-by-step with a compatible execution skill.

Does this planning approach require existing documentation to start?

No, this planning approach does not require existing documentation to start, as it extracts intent, context, and constraints directly through targeted stakeholder interviewing before generating the structured plan.