cy-execute-task

Execute PRD tasks end-to-end with checklist validation and tracking updates.

2.5k|134|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill cy-execute-task-compozy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-execute-task
Source: https://github.com/compozy/compozy/tree/main/.agents/skills/cy-execute-task
Command: npx skills add https://github.com/compozy/compozy --skill cy-execute-task-compozy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the end-to-end execution of a PRD task from specification through updates to task tracking files, reducing manual handoffs and drift.

Core Features & Use Cases

  • Ground the task execution in repository context by reading the provided task specification, PRD documents (especially _techspec.md and _tasks.md), and ADRs.
  • Build a concrete execution checklist from explicit deliverables, acceptance criteria, and validation/testing items, then use it as a gate during implementation.
  • Execute the task following repository patterns and real dependency APIs, and optionally auto-commit changes while updating memory and task tracking state.

Quick Start

Provide a PRD task file and its PRD directory to run the task from exploration to tracking updates.

Frequently Asked Questions about cy-execute-task

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

FAQPage Schema
How do I execute PRD tasks end-to-end with automated tracking?

Executing PRD tasks end-to-end involves grounding in repository context, reconciling the workspace against the task specification and techspec, building a deterministic execution checklist, and validating with tests before updating task tracking files.

What is the best way to prevent drift when implementing task specifications from a PRD?

Preventing drift during task specification implementation requires reconciling the current workspace against the PRD guidance, techspec, and ADRs to identify conflicts before building a deterministic execution checklist from deliverables and acceptance criteria.

How do I build a deterministic execution checklist from PRD deliverables and acceptance criteria?

Building a deterministic execution checklist from PRD deliverables involves extracting explicit deliverables, acceptance criteria, and validation items, then using that checklist as a required gate during task implementation to ensure completion evidence before proceeding.

Can I auto-commit changes when running task execution workflows against a PRD?

Yes, task execution workflows support optional auto-commit behavior when running tasks end-to-end, allowing changes to be committed automatically while validating with tests and updating memory and task tracking state.

Do I need ADRs and techspec files to automate task execution from a PRD?

ADRs and techspec files are needed to ground task execution in repository context, as the execution process reconciles the current workspace against the task specification, techspec, and ADRs to identify conflicts before building the execution checklist.

Why does task execution require completion evidence before proceeding to the next checklist item?

Task execution requires completion evidence before proceeding to ensure each deliverable and acceptance criteria item is validated, preventing drift and maintaining deterministic execution standards throughout the PRD task implementation.