prp-implement

To execute a plan file with continuous validation, provide a path to a .plan.md file and the skill processes it with per-task type-checks and tests to prevent accumulating broken state. It handles sequential and parallel modes while validating after every change.

PRP plan execution applies continuous validation loops by running phase-based checks like type-checking, unit tests, builds, and integration tests after every task. This mechanism immediately catches broken state across multiple tasks and batches during feature implementation.

Yes, you can use parallel execution and worktrees for multi-task feature implementation. The skill supports parallel and sequential execution modes, worktree handling, and agent or team dispatch while maintaining per-task validation across batches.

The best way to automate workflow validation across batches is using a skill that parses plan flags, loads the plan, and applies comprehensive phase-based validation. It reports results after validating type-checks, tests, builds, and edge cases sequentially or in parallel.

You need a .plan.md file to run automated task dispatch and reporting. The skill loads this plan file, parses execution flags for sequential or parallel modes, and generates a comprehensive final report after completing all validation phases.

Multi-task feature implementation accumulates broken state when validation is deferred until the end. Running continuous validation loops after every individual change prevents this by catching type errors, test failures, and build issues immediately during execution.