plan-phase

Generate a detailed technical implementation plan for a project phase.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/vanderleik/greenfiend-project --skill plan-phase-vanderleik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-phase
Source: https://github.com/vanderleik/greenfiend-project/tree/main/.github/skills/plan-phase
Command: npx skills add https://github.com/vanderleik/greenfiend-project --skill plan-phase-vanderleik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan Phase generates a structured blueprint that translates high-level project phase goals into actionable, executable steps for delivery teams, ensuring traceable decisions and clear ownership.

Core Features & Use Cases

  • Provides a repeatable framework to decompose a phase into concrete tasks, dependencies, and acceptance criteria.
  • Aligns phase deliverables with the overarching project plan and testing conventions.
  • Supports variations like plan phase X, detail the phase, or generate phase implementation.

Quick Start

Provide a complete, actionable technical plan for the current project phase.

Frequently Asked Questions about plan-phase

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

FAQPage Schema
How do I generate a technical implementation plan for a project phase?

Plan Phase generates a detailed technical implementation plan for a project phase that connects the general plan to execution. It applies when the user asks to plan, detail, or generate the technical plan for a phase, including variations like 'plan phase X', 'detail the phase', or 'generate phase implementation'. It enforces decisions from docs/project-plan.md and uses decisions and testing conventions to shape step implementations, dependencies, and acceptance criteria.

How do I turn high-level project phase goals into actionable executable steps?

Plan Phase generates a detailed technical implementation plan for a project phase that connects the general plan to execution. It applies when the user asks to plan, detail, or generate the technical plan for a phase, including variations like 'plan phase X', 'detail the phase', or 'generate phase implementation'. It enforces decisions from docs/project-plan.md and uses decisions and testing conventions to shape step implementations, dependencies, and acceptance criteria.

What is the best way to document dependencies and acceptance criteria for a project phase?

Plan Phase generates a detailed technical implementation plan for a project phase that connects the general plan to execution. It applies when the user asks to plan, detail, or generate the technical plan for a phase, including variations like 'plan phase X', 'detail the phase', or 'generate phase implementation'. It enforces decisions from docs/project-plan.md and uses decisions and testing conventions to shape step implementations, dependencies, and acceptance criteria.

Do I need a project plan document before detailing a technical phase implementation?

Plan Phase generates a detailed technical implementation plan for a project phase that connects the general plan to execution. It applies when the user asks to plan, detail, or generate the technical plan for a phase, including variations like 'plan phase X', 'detail the phase', or 'generate phase implementation'. It enforces decisions from docs/project-plan.md and uses decisions and testing conventions to shape step implementations, dependencies, and acceptance criteria.

How does enforcing decisions from project-plan.md improve phase implementation planning?

Plan Phase generates a detailed technical implementation plan for a project phase that connects the general plan to execution. It applies when the user asks to plan, detail, or generate the technical plan for a phase, including variations like 'plan phase X', 'detail the phase', or 'generate phase implementation'. It enforces decisions from docs/project-plan.md and uses decisions and testing conventions to shape step implementations, dependencies, and acceptance criteria.

When should I not use a structured blueprint for project phase planning?

Plan Phase generates a detailed technical implementation plan for a project phase that connects the general plan to execution. It applies when the user asks to plan, detail, or generate the technical plan for a phase, including variations like 'plan phase X', 'detail the phase', or 'generate phase implementation'. It enforces decisions from docs/project-plan.md and uses decisions and testing conventions to shape step implementations, dependencies, and acceptance criteria.