cy-execute-task

Execute a PRD task end-to-end with validation and tracking updates.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/MatheusBBarni/symphony-orchestrator --skill cy-execute-task-matheusbbarni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-execute-task
Source: https://github.com/MatheusBBarni/symphony-orchestrator/tree/main/.agents/skills/cy-execute-task
Command: npx skills add https://github.com/MatheusBBarni/symphony-orchestrator --skill cy-execute-task-matheusbbarni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Executes a single PRD task from exploration through tracking updates, ensuring the task specification is implemented, validated, and reflected in task tracking artifacts.

Core Features & Use Cases

  • Ground in repository context and PRD guidance to align with ADRs, tech specs, and tasks.
  • Build and enforce a detailed execution checklist that captures deliverables, validation criteria, and evidence as work progresses.
  • Update memory states and task tracking artifacts, with optional auto-commit support, ensuring consistent state across current task and master task entries.

Quick Start

Provide a PRD task file and its directory, then run cy-execute-task to begin end-to-end task execution.

Frequently Asked Questions about cy-execute-task

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

FAQPage Schema
How do I automate end-to-end PRD task execution from specification to tracking updates?

Automating end-to-end PRD task execution involves reading task specs and ADRs, reconciling conflicts, building a detailed execution checklist, performing workspace edits, validating, and updating memory and master task tracking files.

What is the best way to ensure automated code changes align with existing tech specs and ADRs?

To ensure automated changes align with tech specs and ADRs, the execution process grounds itself in repository context and PRD guidance, reconciling conflicts between new task specifications and existing architectural decisions before applying deterministic edits.

How do I validate workspace changes after automatically executing a PRD task?

Validating workspace changes after PRD task execution is handled by running the cy-final-verify process, which checks the deterministic edits against the validation criteria defined in the generated execution checklist.

Can I use PRD task automation to update memory states and master task tracking files simultaneously?

Yes, PRD task automation can update memory states and master task tracking files simultaneously, offering optional auto-commit support to ensure consistent state across both current task entries and the master task log.

Do I need to provide a specific directory structure to run automated PRD task execution?

You need to provide a PRD task file, its directory path, repository context, and optional workflow memory paths to run automated PRD task execution and induce deterministic edits in your workspace.

Why does PRD task execution require building a detailed checklist before making code changes?

PRD task execution requires building a detailed checklist to capture deliverables, validation criteria, and evidence as work progresses, ensuring the automated implementation strictly satisfies the task specification before tracking updates occur.