plan-maker

Generate structured implementation plans with acceptance criteria and validation strategies.

36|6|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/KjellKod/quest --skill plan-maker
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-maker
Source: https://github.com/KjellKod/quest/tree/main/.skills/plan-maker
Command: npx skills add https://github.com/KjellKod/quest --skill plan-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Maker helps teams generate structured, review-ready implementation plans that define what to build, how to validate it, who is involved, and what risks to consider before coding starts.

Core Features & Use Cases

  • Standardized planning templates capturing Overview, Acceptance Criteria, Validation Plans, Integration Touchpoints, and Risks
  • Support for both Small Plans (1 doc) and Large Plans (phase-based planning) to match project scope
  • Clear guidance for Implementation Approach, Open Questions, and risk mitigation to reduce rework
  • Improves cross-team collaboration by mapping touchpoints to APIs, databases, UI components, and deployment steps

Quick Start

Create a new plan using the Small Plan template with an Overview, at least two Acceptance Criteria, a Validation section (automated and manual tests), and an Integration Touchpoints list. If your project requires multiple phases, switch to a Large Plan and define Phase 1, Phase 2, and their dependencies.

Frequently Asked Questions about plan-maker

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

FAQPage Schema
How do I create structured implementation plans with acceptance criteria before coding begins?▼

Implementation plans need an Overview, Acceptance Criteria, Validation Plans, Integration Touchpoints, Implementation Approach, Risks, and Open Questions. Plan Maker enforces these explicit requirements to guide teams through a plan-driven workflow for features, refactors, and architectural updates.

What is plan-driven engineering and when do I need it for software projects?▼

Plan-driven engineering generates structured implementation plans defining acceptance criteria, validation strategies, and risk analysis before coding begins. It applies to features, refactors, infrastructure changes, and architectural updates across multi-file projects.

How do I plan multi-phase infrastructure changes and track dependencies?▼

For multi-phase projects, switch to a Large Plan template to define Phase 1, Phase 2, and their dependencies. This phase-based planning approach matches larger project scopes and maps integration touchpoints to APIs, databases, UI components, and deployment steps.

Does this planning template support both automated and manual validation strategies?▼

Yes, the planning template requires a Validation section that includes both automated and manual tests. It enforces explicit validation strategies alongside acceptance criteria, integration touchpoints, and risk mitigation to ensure comprehensive review-ready plans.

Can I use this plan maker for small refactors or is it only for large architectural updates?▼

The Small Plan template handles small refactors using a single document with an Overview, at least two Acceptance Criteria, a Validation section, and Integration Touchpoints. Large Plans support phase-based planning for bigger architectural updates.

What are the limitations of using standardized planning templates for software engineering?▼

Standardized planning templates enforce strict sections for Overview, Acceptance Criteria, Validation, Integration Touchpoints, Risks, and Open Questions. This plan-driven approach may introduce overhead for trivial changes but effectively reduces rework for complex multi-file projects.