Dppm Orchestration

Execution rules

• Do not start the next major action item until the previous one is completed and recorded with evidence in the plan.
• Keep the plan document as the source of truth and update it after each completed task.

Impact analysis rules

• List impacted files grouped by area (UI, API, DB, infra, tests).
• Include an ASCII diagram showing components and file impact.
• Keep diagrams ASCII only.

DPPM phases

1. DISCOVER

• Analyze requirements.
• Read project context.
• Identify constraints.
• Assess risks.

2. PLAN

• Break down into major action items and smaller tasks.
• Assign specialists when helpful.
• Define dependencies and mitigation steps.
• Create the plan document in plans/.

3. PROTOTYPE

• Execute tasks in the plan order.
• Update the plan document with evidence after each major item.
• Stop and request clarification when blockers appear.

4. MONITOR

• Track progress and blockers.
• Validate scope and quality gates.
• Keep the plan document current.

Delegation defaults

• Design: @design-owner
• Architecture: @architecture-owner
• Backend: @backend-owner
• Frontend: @frontend-owner
• Testing: @test-owner
• Bug Fix Orchestration: @bugfix-owner
• Deployment: @deploy-owner

References

• Use references/plan-template.md for the standard plan layout.
• Use references/impact-analysis.md for file impact analysis and ASCII diagram guidance.
• Use references/user-test-template.md to write the user test section.

Scripts

• From repo root, run python3 codex/skills/dppm-orchestration/scripts/print_plan_template.py --feature "<Feature Name>" --type feature to print a plan template.
• From repo root, run python3 codex/skills/dppm-orchestration/scripts/print_impact_diagram_template.py to print an ASCII diagram template.
• From repo root, run python3 codex/skills/dppm-orchestration/scripts/skill_info.py to show skill metadata.