skills.rest
davidlee
davidleeCOMMUNITY
Explore all skills by this author →
GitHub

plan-phases

Plan the next executable phase for delta artifacts with design-gated objectives and verification expectations.

26|3|Updated Oct 9, 2025
Search Tags:#workflow automation#agent orchestration#spec-driven development#phase planning#design governance#verification criteria
One-click install
npx skills add https://github.com/davidlee/spec-driver --skill plan-phases-davidlee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-phases
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/plan-phases
Command: npx skills add https://github.com/davidlee/spec-driver --skill plan-phases-davidlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents execution from running ahead of unresolved design by planning the next phase with explicit entry/exit criteria and verification expectations.

Core Features & Use Cases

  • Design-gated planning: Ensures the plan only proceeds when the design revision is present and aligned to the current ask, avoiding speculative phase creation.
  • Execution-ready IP refinement: Converts intent into concrete phase objectives, success criteria, and verification expectations mapped to the work.
  • Next phase sheet creation and setup: Creates the next phase and updates it with tasks, assumptions/constraints, and VT/VA/VH-style verification steps.
  • Policy ambiguity escalation: Routes complex or ambiguous situations to consultation before execution.

Quick Start

Ask your agent to run the plan-phases flow for DE-, DR-, and IP- artifacts so it can produce the next phase sheet with concrete tasks and done criteria.

Frequently Asked Questions about plan-phases

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

FAQPage Schema
How do I prevent execution from running ahead of unresolved design in spec-driven development?▼

Spec-driven design gating prevents execution drift by planning the next phase with explicit entry and exit criteria, ensuring the execution-ready IP only proceeds when the design revision aligns with the current ask.

What's the best way to generate execution-ready phase plans with verification criteria?▼

Generating an execution-ready IP refines design intent into concrete phase objectives, success criteria, and VT/VA/VH verification expectations, creating a next phase sheet populated with tasks and done criteria before handoff.

Do I need design revision artifacts to start phase planning?▼

Phase planning requires DE- and IP- artifacts to exist, while the DR- artifact can optionally be missing or stale, allowing the workflow to proceed by reconciling available inputs and enforcing design-gating rules.

How does agent orchestration handle policy ambiguity during phase planning?▼

Agent orchestration routes complex or ambiguous policy situations to consultation before execution, escalating issues rather than guessing, ensuring the generated phase plan avoids speculative creation against unresolved design.

Can I automate next phase sheet creation and task updates in workflow automation?▼

Workflow automation creates the next phase sheet via the phase creation command, automatically updating it with assumptions, constraints, tasks, and VT/VA/VH-style verification steps to produce an execution-ready handoff.

Related Skills

Explore More Software Engineering Skills→
davidleedavidlee
26

scope-delta

Translate requirements and doctrine constraints into traceable scope delta artifacts.

Community
Intermediate
shaul1991shaul1991

gate-keeper

Verify phase completion against predefined success criteria to issue Go/No-Go decisions.

Community
Advanced
45black-Limited45black-Limited
1

apply-ppf

Apply PPF branding to governance documents in Word, HTML, and presentations.

Official
Advanced
connor-git-yamlconnor-git-yaml
15

speckit-fix

Automates end-to-end issue fixes across Spec Driver workflows with diagnosis, planning, implementation, and verification.

Community
Advanced