dppm-orchestration

Create mandatory DPPM plan documents with impact analysis and execution checkpoints.

Updated Nov 23, 2025

Search Tags:#planning #task breakdown #orchestration #impact analysis #user testing #context compaction #dppm

Ready to run

npx skills add https://github.com/ak-eyther/model-project --skill dppm-orchestration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dppm-orchestration
Source: https://github.com/ak-eyther/model-project/tree/main/codex/skills/dppm-orchestration
Command: npx skills add https://github.com/ak-eyther/model-project --skill dppm-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

DPPM Orchestration turns vague software requests into a controlled plan before implementation, reducing scope drift, missed dependencies, and untracked work.

Core Features & Use Cases

Plan-First Workflow: Forces every feature, fix, or refactor into a named plan document in plans/ before execution.
Impact Analysis and Task Breakdown: Captures touched files, dependencies, risks, ASCII diagrams, and checkbox-based subtasks.
Evidence-Gated Progress: Requires evidence after each major step and supports resume-ready check-ins for context compaction.
Use Case: Use it when coordinating a multi-agent feature build, debugging a risky regression, or organizing a refactor that touches UI, API, tests, and deployment.

Quick Start

Ask the assistant to create a DPPM plan for your feature, fix, or refactor and save it in plans/ before any implementation begins.

Frequently Asked Questions about dppm-orchestration

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

FAQPage Schema

How do I break down complex software features into structured task plans?▼

Task breakdown planning applies to multi-step software work requiring impact analysis, evidence gating, and execution checkpoints to prevent scope drift and missed dependencies.

How do I create a structured plan for a risky regression fix?▼

Create a structured plan for a regression fix by saving a named plan document in plans/ that includes scoped file impact lists, ASCII diagrams, and user test planning before execution.

What is the best way to coordinate a multi-agent feature build without losing context?▼

The best way to coordinate a multi-agent build is enforcing a plan-first workflow with context-compaction handoff and resume-ready check-ins that require evidence after each major step.

Can I use gated progress checkpoints for refactoring work that touches UI, API, and tests?▼

Yes, gated progress checkpoints support refactoring work across UI, API, tests, and deployment by requiring execution evidence before proceeding to the next major action item.

Do I need to perform impact analysis before starting a multi-step software task?▼

Yes, impact analysis is required before starting multi-step tasks to capture touched files, dependencies, and risks, enforcing a plans/ source of truth to prevent untracked work.