recipe-fullstack-build

Coordinate decomposed fullstack tasks across backend and frontend executors.

Updated Jun 8, 2026

Search Tags:#subagents #orchestration #monorepo #fullstack #quality-assurance #task-decomposition

Ready to run

npx skills add https://github.com/darsoohoo/intake-bot --skill recipe-fullstack-build

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: recipe-fullstack-build
Source: https://github.com/darsoohoo/intake-bot/tree/main/.agents/skills/recipe-fullstack-build
Command: npx skills add https://github.com/darsoohoo/intake-bot --skill recipe-fullstack-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decomposed fullstack task coordination across backend and frontend executors to ensure consistent, auditable delivery in complex projects.

Core Features & Use Cases

Layer-aware routing of tasks to appropriate executors (backend and frontend) with quality-fixer validation.
Enforced spawn and isolation rules to ensure context integrity across task cycles.
End-to-end execution flow including task decomposition, reference reads, and post-commit verification for multi-service apps.

Quick Start

Invoke the recipe-fullstack-build workflow to begin decomposing and executing the current work plan and commit the results.

Frequently Asked Questions about recipe-fullstack-build

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

FAQPage Schema

How do I coordinate fullstack task decomposition across backend and frontend executors in a monorepo?▼

Layer-aware fullstack task orchestration coordinates decomposed backend and frontend tasks by routing them to appropriate executors within a monorepo. This enforces context isolation and quality-fixer validation to deliver a ready-to-commit code base.

What is the best way to maintain context isolation when orchestrating sub-agents for complex project tasks?▼

Enforcing mandatory spawn_agent constraints and a strict four-step task cycle maintains context isolation during sub-agent orchestration. This governance prevents context bleed across backend and frontend executors during fullstack task execution.

How does cross-service verification work when executing fullstack tasks autonomously?▼

Cross-service verification applies an end-to-end execution flow featuring task decomposition, reference reads, and post-commit verification. This validates routed backend and frontend executor outputs across multi-service applications.

Does this fullstack task orchestration workflow require a specific monorepo project structure?▼

Yes, this fullstack task orchestration workflow applies specifically to monorepo-style projects. It requires a structured work plan capable of task planning and cross-layer routing to execute autonomous backend and frontend task cycles.

Why use layer-aware routing for fullstack task execution instead of standard sequential execution?▼

Layer-aware routing directs tasks to specialized backend and frontend executors with quality-fixer validation, unlike standard sequential execution. This ensures consistent, auditable delivery and maintains context integrity across complex fullstack projects.