cy-execute-task

Executes one PRD task end-to-end from specification through validation and tracking updates.

Updated May 19, 2026
One-click install
npx skills add https://github.com/lucasocosta/reeve --skill cy-execute-task-lucasocosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-execute-task
Source: https://github.com/lucasocosta/reeve/tree/main/skills/cy-execute-task
Command: npx skills add https://github.com/lucasocosta/reeve --skill cy-execute-task-lucasocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Implementing a single task from a PRD often involves juggling the task spec, techspec, ADRs, tests, and tracking files, and it is easy to skip validation or forget to update task status. This Skill enforces a disciplined end-to-end workflow so each PRD task is implemented, verified, and recorded consistently. ## Core Features & Use Cases - Context Grounding: Reads the task specification, PRD documents, techspec, and ADRs, then stops and reports conflicts instead of guessing when requirements contradict. - Checklist-Driven Implementation: Extracts deliverables, acceptance criteria, and validation items into a numbered checklist used as a gate before completion. - Mandatory Verification and Tracking: Runs all task-specified tests, performs self-review, updates memory and task tracking files in a fixed sequence, and optionally creates one local commit. - Use Case: Given a task file, a PRD directory, and master tasks file, implement the feature, run its validation commands, mark subtasks complete, and commit the change automatically. ## Quick Start Execute the task defined in this task specification file using the provided PRD directory and update the task tracking files with auto-commit enabled.

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 a PRD task end-to-end with an AI agent?▼

Provide the task specification file, PRD directory path, task file path, master tasks file path, and auto-commit mode. The workflow reads the spec, techspec, and ADRs, builds a checklist, implements the changes, runs all specified validations, and updates tracking files in sequence.

What inputs are required to run a PRD task execution workflow?▼

Required inputs are the task specification markdown, PRD directory path, task file path, master tasks file path, and auto-commit mode. Optional inputs include workflow memory directory, shared workflow memory, and current task memory paths.

What happens when the task spec conflicts with the techspec or ADRs?▼

The workflow stops and reports the conflict instead of guessing. After reading the task specification, techspec, and ADRs, any contradictory requirements halt execution before implementation begins.

Does the task execution workflow commit changes automatically?▼

Only when auto-commit mode is enabled, and only after clean verification, self-review, and tracking updates. It creates one local commit and never pushes automatically; with auto-commit disabled, the diff is left for manual review.

When should I not use this PRD task execution skill?▼

Do not use it for PR review batches, generic coding tasks without a PRD task file, or standalone verification-only work. It is designed specifically for implementing one tracked PRD task end-to-end.