recipe-fullstack-implement

Orchestrate fullstack implementation from requirements analysis through QA.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Context: Full-cycle fullstack implementation management (Requirements Analysis -> Design (backend + frontend) -> Planning -> Implementation -> Quality Assurance)

Core Features & Use Cases

  • End-to-end orchestration of fullstack tasks across multiple layers with layer-aware routing for subagents.
  • Enforces monorepo-flow guidelines, modular design docs, and vertical slicing to maintain traceability from PRD to QA.
  • Use Case: A complex feature across services and UIs can be decomposed into Requirements, Design Docs, Work Plan, Implementation, and Quality Checks, with automated task registration and progress tracking.

Quick Start

Invoke the recipe-fullstack-implement to start the fullstack implementation workflow from requirements through QA.

Frequently Asked Questions about recipe-fullstack-implement

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

FAQPage Schema
How do I orchestrate fullstack implementation across multiple layers from requirements to QA?

Fullstack implementation is orchestrated end-to-end by decomposing complex features into requirements analysis, design docs, work plans, implementation, and quality assurance. This workflow applies layer-aware routing to coordinate subagents across backend and frontend layers.

What is vertical slicing and how does it maintain traceability in monorepo-flow?

Vertical slicing decomposes features into modular design docs that enforce monorepo-flow guidelines. It maintains traceability from PRD to QA by applying strict quality gates and orchestrating autonomous sub-agent coordination across services and UIs.

How do I coordinate autonomous sub-agents for complex multi-team projects?

Autonomous sub-agents are coordinated through layer-aware routing that distributes tasks across backend and frontend layers. This orchestration satisfies formal design docs, work plans, and strict quality gates defined by subagents orchestration guidance.

Does this fullstack orchestration workflow require formal design docs and work plans?

Yes, formal design docs and work plans are required for this fullstack orchestration workflow. Complex multi-team projects use these documents alongside automated task registration and progress tracking to maintain traceability from PRD through QA.

Can I use this orchestration approach for features spanning both backend services and frontend UIs?

Yes, this orchestration approach applies to features spanning backend services and frontend UIs. It enforces modular design docs and vertical slicing to decompose cross-layer tasks into Requirements, Design, Implementation, and Quality Checks.

What's the best way to automate task registration and progress tracking in a fullstack project?

Automating task registration and progress tracking is best handled by orchestrating end-to-end fullstack implementation with autonomous sub-agent coordination. This workflow registers tasks automatically while enforcing strict quality gates from requirements analysis to QA.