recipe-build

Coordinate autonomous backend task execution with strict quality gates.

29|4|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/shinpr/codex-workflows --skill recipe-build-shinpr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recipe-build
Source: https://github.com/shinpr/codex-workflows/tree/main/.agents/skills/recipe-build
Command: npx skills add https://github.com/shinpr/codex-workflows --skill recipe-build-shinpr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates autonomous backend task execution with strict quality gates to ensure reliable delivery of decomposed work.

Core Features & Use Cases

  • End-to-end orchestration across task-executor, escalation check, quality-fixer, and commit.
  • Enforces readiness checks, pre-execution prerequisites, and spawn rules for context isolation.
  • Supports plan-driven task decomposition, on-demand subagent coordination, and integrated quality assurance before commits.

Quick Start

Deploy recipe-build to orchestrate backend tasks from plan to commit with built-in quality checks.

Frequently Asked Questions about recipe-build

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

FAQPage Schema
How do I automate backend task execution with quality checks before git commit?

Autonomous subagent orchestration coordinates multi-file changes through a four-step cycle: task-executor, escalation check, quality-fixer, and commit. This enforces pre-execution readiness and strict spawn rules for large refactors.

What is the best way to orchestrate autonomous subagents for large refactors?

Orchestrating autonomous subagents for large refactors requires a plan-driven task decomposition cycle. This coordinates work across subagents with integrated quality assurance and strict context isolation before committing.

How does task decomposition work for autonomous multi-file changes?

Task decomposition for autonomous multi-file changes works by breaking down large refactors into a plan-driven cycle. It applies pre-execution prerequisites and strict spawn rules to isolate context across coordinated subagents before a commit.

Do I need a plan to coordinate autonomous tasks with quality gates?

Yes, you need a plan to coordinate autonomous tasks with quality gates. Plan-driven task decomposition is required to orchestrate work across subagents, enforce pre-execution readiness, and ensure integrated quality assurance before commits.

Why enforce strict spawn rules and escalation checks during backend orchestration?

Enforce strict spawn rules and escalation checks during backend orchestration to achieve context isolation and handle task execution failures. This ensures integrated quality assurance is applied before any auditable commits are made.