p:implement

Execute YAML-planned tasks in dependency order via specialized minions.

1|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/pontscho/prompt-heaven --skill p-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: p:implement
Source: https://github.com/pontscho/prompt-heaven/tree/main/ClaudeCode/skills/p%3Aimplement
Command: npx skills add https://github.com/pontscho/prompt-heaven --skill p-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes end-to-end, task-planned implementations by consuming a YAML requirements file produced by /p:task-plan, coordinating dependency-aware execution, layered validation, and automatic progress updates.

Core Features & Use Cases

  • Orchestrates plan → code execution using p:minion-builder, p:minion-watson, p:minion-impl-inspector, and p:minion-security-officer for a complete lifecycle from plan to validated completion.
  • Executes tasks in dependency order, delegating builds/tests, failure investigation, and security review to specialized minions while preserving a clean main-context.
  • Performs two-phase validation loops after implementation and updates requirements.yaml with implementation_complete status, dates, and open-items when needed.

Quick Start

Run /p:implement in the project root to execute the planned tasks using the generated requirements.yaml.

Frequently Asked Questions about p:implement

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

FAQPage Schema
How do I automate task-planned implementation from a YAML file?

Automating task-planned implementation requires parsing a YAML-based requirements file, identifying required tasks, and coordinating dependency-ordered execution. The process delegates builds, tests, and validation to specialized minions before marking implementation complete.

What is dependency-ordered execution for software implementation?

Dependency-ordered execution is a coordination mechanism that sequences software implementation tasks based on their interdependencies. It ensures prerequisite builds and tests finish successfully before downstream tasks are executed, preserving a clean main-context throughout the lifecycle.

How does post-implementation validation work for automated builds?

Post-implementation validation works by running two-phase validation loops after code execution. It performs automated failure investigation and security review using specialized inspectors, updating the requirements.yaml with completion status, dates, and any open items.

Can I use YAML task plans for automated failure investigation?

Yes, YAML task plans support automated failure investigation by routing build or test failures to specialized minions. These minions analyze the errors, provide retry guidance, and maintain structured audit trails while keeping the main context clean.

What are the limitations of dependency-aware task execution?

Limitations of dependency-aware task execution include the strict requirement for a pre-existing YAML requirements file generated by a task planner. Without this structured input, the automated execution and minion coordination cannot identify or sequence the required tasks.