plan-first-development

Plan complex projects with multi-phase implementation plans before coding.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/maschad/my-claude --skill plan-first-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-first-development
Source: https://github.com/maschad/my-claude/tree/main/skills/plan-first-development
Command: npx skills add https://github.com/maschad/my-claude --skill plan-first-development

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Break complex projects into detailed multi-phase plans before writing any code. Prevents scope creep, refactoring waste, and missed requirements.

Core Features & Use Cases

  • Define project scope with structured templates.
  • Break work into independent, testable phases.
  • Create data structures, critical paths, and verification checklists.
  • Facilitate stakeholder alignment and approvals.

Quick Start

Draft a one-page project brief and complete Phase 1 artifacts using the templates in this guide.

Frequently Asked Questions about plan-first-development

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

FAQPage Schema
How do I break down complex projects into phased implementation plans?

Break complex projects into phased implementation plans by defining project scope with structured templates, decomposing work into independent testable phases, and identifying critical paths before coding begins.

What templates are available for project scope definition and stakeholder sign-off?

Templates for project scope definition and stakeholder sign-off include structured documents for scope boundaries, data-structure specifications, verification checklists, and formal stakeholder approval forms to ensure alignment.

When do I need multi-phase project planning instead of starting to code immediately?

You need multi-phase project planning when initiatives involve multiple interacting components, tight timelines, and integration or performance constraints, requiring critical-path identification before development to prevent refactoring waste.

How do I prevent scope creep and missed requirements when managing complex initiatives?

Prevent scope creep and missed requirements by producing detailed multi-phase plans that define scope, specify data structures, create verification checklists, and facilitate stakeholder alignment prior to writing any code.

Can I use phased planning for projects with tight timelines and integration constraints?

Yes, phased planning is specifically designed for projects with tight timelines and integration or performance constraints, guiding teams from initial scope definition through to final verification checklists.

What is the best way to get stakeholder approval before starting development on a complex project?

The best way to get stakeholder approval is by drafting a one-page project brief and completing Phase 1 artifacts using structured templates that define scope, critical paths, and verification checklists for sign-off.