Generate a structured implementation plan with goals, scope, and success criteria.
npx skills add https://github.com/junkijin/my-pi --skill plan-mode-junkijin
Please help me install this Agent Skill. Skill: plan-mode Source: https://github.com/junkijin/my-pi/tree/main/skills/plan-mode Command: npx skills add https://github.com/junkijin/my-pi --skill plan-mode-junkijin
Plan Mode helps teams avoid premature implementation by generating a decision-complete plan before any coding or integration work.
Describe the task, constraints, and success criteria to have Plan Mode generate a complete, decision-ready plan before execution.
High-intent search queries and answers about installing and using this skill.
To create an implementation-ready project plan, define your task, constraints, and success criteria upfront. Plan Mode generates a structured outline capturing goals, scope, assumptions, and open questions to clarify ambiguous, multi-system requests before any coding work starts.
Upfront planning is essential for multi-system integration when requests are large, ambiguous, or high-risk. Generating a decision-complete plan clarifies goals, maps requirements to concrete resources, and addresses data flow, state transitions, failure handling, and rollout before execution.
A decision-ready plan for high-risk software projects should include defined goals, scope, constraints, assumptions, and material open questions. It must map requirements to concrete implementation areas, specify success criteria, and cover data flow, migrations, privacy, and monitoring when relevant.
Mapping project requirements to concrete implementation areas requires a structured plan outline that connects each requirement to specific decisions, named resources, and actions. This ensures stakeholder communication aligns with defined success criteria before integration begins.
Yes, structured planning handles ambiguous feature requests spanning multiple systems by generating a decision-complete plan. It captures goals, scope, and constraints while defining data flow, state transitions, failure handling, and rollout strategies to eliminate ambiguity before coding.
A plan-only pass produces a decision-ready strategy but does not execute coding or integration. It requires clearly defined success criteria and task descriptions upfront, meaning teams must separately handle the actual implementation, resource allocation, and execution monitoring afterward.
mwayDefine analysis scope, objectives, constraints, and success criteria with evidence and risk assessment.
lhohanGenerate an ordered implementation plan with goals, steps, files, and risks.
jamestorrevillasTranslate vague business requests into technical plans with acceptance criteria.
DevelopersGlobalBreak down complex project features into smaller, independently executable tasks.
