cy-execute-task

To execute a PRD task end-to-end, supply a task specification markdown, PRD directory, task file path, and master tasks file path. The workflow reads repository guidance, reconciles ADR conflicts, implements steps, validates with cy-final-verify, and updates tracking files.

PRD task execution is a deterministic workflow that processes task specifications while aligning with repository guidance. It reads ADRs to reconcile architectural conflicts before advancing, ensuring implementation complies with established technical decisions and documentation.

Validate PRD task implementation using cy-final-verify for self-review. The execution workflow builds a checklist, captures pre-change signals, enforces gatekeeping until items complete, implements steps deterministically, and validates against provided specs.

Yes, you can provide optional memory paths to store workflow context during PRD execution. The workflow updates these memory paths alongside task tracking files, including the master tasks file, with proper commit behavior per the auto-commit flag.

Yes, PRD task execution reads PRD documents like _techspec.md and _tasks.md to ground in repository context. These files provide the technical specifications and task definitions needed to reconcile conflicts and implement steps deterministically.

Automate task tracking updates by providing a master tasks file path and enabling the auto-commit flag. After executing PRD steps and validating with cy-final-verify, the workflow records decisions and updates tracking files with proper commit behavior.