recipe-front-build

Coordinate autonomous frontend tasks with quality gates and commit workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end frontend task work by coordinating sub-agents, enforcing quality gates, and safeguarding commits in complex projects.

Core Features & Use Cases

  • Autonomous orchestration of frontend tasks across task-executor-frontend, escalation check, and quality-fixer-frontend.
  • Enforced 4-step execution cycle with pre-execution checks, work plan gating, and post-implementation verification.
  • Supports task decomposition from work plans, dependency tracking, and safe commit workflows.

Quick Start

Initiate autonomous frontend task execution by invoking the recipe-front-build skill to run the 4-step cycle and emit committed changes after quality validation.

Frequently Asked Questions about recipe-front-build

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

FAQPage Schema
How do I automate frontend tasks with quality checks before committing?

Frontend task orchestration coordinates multiple subagents to handle planning, execution, and validation, enforcing strict quality gates and pre-execution checks before allowing any code commits.

Can I use task decomposition for complex frontend projects across multiple subagents?

Task decomposition splits work plans into manageable units with dependency tracking, allowing multiple subagents to execute frontend tasks autonomously while maintaining cross-step validation.

What is the 4-step execution cycle for autonomous frontend workflows?

The 4-step cycle is a structured execution mechanism that applies pre-execution checks, gates work plans, executes frontend tasks, and performs post-implementation verification before committing changes.

Does this frontend orchestration approach work without external dependencies?

Yes, this frontend orchestration operates with no external dependencies, relying entirely on internal subagent coordination, quality gates, and automated verification to safeguard commit workflows.

Why do I need quality gates for frontend commit workflows?

Quality gates prevent unverified code from entering the repository by enforcing pre-execution checks and post-implementation validation, ensuring autonomous frontend tasks meet standards before committing.

What's the best way to handle escalation checks in frontend task automation?

Handle escalation checks by integrating them into the orchestration workflow, routing failed quality checks to a quality-fixer-frontend subagent before retrying the commit workflow.