recipe-build

Orchestrate decomposed backend tasks through a four-step execution cycle with quality gates.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/darsoohoo/intake-bot --skill recipe-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: recipe-build
Source: https://github.com/darsoohoo/intake-bot/tree/main/.agents/skills/recipe-build
Command: npx skills add https://github.com/darsoohoo/intake-bot --skill recipe-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables autonomous orchestration of decomposed backend tasks using a task-executor and a quality-fixer, ensuring predictable execution while enforcing safety and governance during the commit cycle.

Core Features & Use Cases

  • Spawns sub-agents to execute tasks, route data, and report results.
  • Enforces a mandatory four-step execution cycle: task-executor -> escalation check -> quality-fixer -> commit.
  • Provides pre-execution readiness checks, consumed task set validation, and strict governance over commits.

Quick Start

Initialize the recipe-build skill and start autonomous task execution using the 4-step cycle to process tasks from docs/plans.

Frequently Asked Questions about recipe-build

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

FAQPage Schema
How do I orchestrate autonomous backend agents to commit code only after passing quality checks?

You can orchestrate decomposed backend workflows by spawning sub-agents to execute tasks and route data. Autonomous agents report results back through a structured cycle for centralized management.

How does a quality-fixer sub-agent work in decomposed backend workflows?

Pre-execution readiness checks validate the consumed task set and environment before spawning sub-agents. This ensures decomposed backend workflows have strict governance over commits and auditable task execution.

Can I use autonomous task execution for decomposed backend workflows with no external dependencies?

Strict governance over commits is enforced through pre-execution prerequisites and a mandatory four-step cycle. This ensures all autonomous agent task execution produces traceable, auditable results before committing.

What is the best way to prevent bad commits when spawning autonomous sub-agents?

Post-implementation verification applies strict governance over commits by validating the output of the task-executor and quality-fixer. This ensures autonomous agent results are traceable and auditable.