execute-task

Execute a PRD story through a Ralph-pattern workflow with worker handoffs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/indigoai-us/hq --skill execute-task-indigoai-us
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-task
Source: https://github.com/indigoai-us/hq/tree/main/template/.claude/skills/execute-task
Command: npx skills add https://github.com/indigoai-us/hq --skill execute-task-indigoai-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute a PRD-driven story through coordinated worker phases, ensuring domain-specific handoffs and back-pressure controls to keep code and tasks on rails.

Core Features & Use Cases

  • End-to-end PRD story execution: Orchestrates multiple specialized workers to complete a user story from planning to validation.
  • Back-pressure and handoffs: Enforces context transfer between workers and validation gates (lint, tests, typecheck) to maintain quality.
  • Configurable workflow: Supports task selection, dependency checks, and optional Codex-assisted steps.

Quick Start

Run execute-task {project}/{task-id} to begin processing a PRD story.

Frequently Asked Questions about execute-task

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

FAQPage Schema
How do I orchestrate PRD story execution with coordinated workers?

PRD story execution is orchestrated by coordinating specialized workers through a Ralph-pattern workflow, enforcing deterministic task flow, dependency checks, and structured handoffs to keep code and tasks on rails.

What is back-pressure in task execution workflows and when do I need it?

Back-pressure in task execution workflows enforces validation gates like lint, tests, and typecheck before context transfer between workers. It is needed to maintain quality and prevent downstream processing failures during PRD story execution.

How do I enforce deterministic task flow and dependency checks for user stories?

Deterministic task flow is enforced by loading task specs, validating dependencies, and producing structured handoffs for downstream workers. This ensures each phase produces a consistent, machine-readable outcome for the next worker.

Can I configure task selection and optional Codex-assisted steps in a worker pattern workflow?

Task selection and optional Codex-assisted steps can be configured within the workflow. The system supports selecting specific PRD stories and applying configurable processing phases to execute the coordinated worker pattern.

Does execute-task work without external component dependencies?

Execute-task runs without external component dependencies. It relies entirely on its internal Ralph-pattern workflow logic to coordinate domain-specific handoffs, back-pressure controls, and task execution phases.

What's the best way to start running a PRD story through coordinated workers?

To start running a PRD story, execute the command format execute-task {project}/{task-id}. This loads the task spec and begins the phase-by-phase orchestration of specialized workers.