build-full-stack

Name: build-full-stack
Availability: InStock
Author: Endaoment

Coordinate AI workers to implement features across multiple repositories and open PRs.

Updated Feb 10, 2026

Search Tags:#multi-repo #ci-cd #pull-requests #feature-delivery #orchestrate #task-decomposition #ai-workers

Ready to run

npx skills add https://github.com/endaoment/fellowship-code --skill build-full-stack

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-full-stack
Source: https://github.com/endaoment/fellowship-code/tree/main/skills/build-full-stack
Command: npx skills add https://github.com/endaoment/fellowship-code --skill build-full-stack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates multi-repo feature delivery by coordinating domain-specific AI workers, eliminating manual coordination and ensuring consistent PRs across repositories.

Core Features & Use Cases

Spawn domain-specific workers (frontend, backend, specialist, ops) to implement features across multiple repositories.
Enforce CI/testing before PRs and group changes into coherent, review-ready PRs.
Respect dependency order (backend before frontend, specialized domains before integration) and iterate in cycles.
Generate centralized progress reports and status updates across all affected repos.
Accept a feature spec and/or tracking issues as input to guide the workflow.

Quick Start

Provide a feature spec and let Gandalf orchestrate domain workers to implement across repositories and open PRs.

Frequently Asked Questions about build-full-stack

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

FAQPage Schema

How do I coordinate feature delivery across multiple repositories?▼

Multi-repo feature delivery is coordinated by orchestrating specialized AI workers that decompose tasks, implement changes, and group coherent pull requests across repositories. The workflow respects dependency sequencing and enforces CI testing before opening review-ready PRs.

What is the best way to automate multi-repo pull requests and CI testing?▼

Automating multi-repo pull requests requires an orchestration workflow that enforces CI testing before PR creation and groups changes into coherent, review-ready PRs. It spawns specialized AI workers to implement features while respecting strict dependency order like backend before frontend.

Can I use AI workers to decompose tasks for multi-repo features?▼

AI workers can be spawned to decompose and implement tasks for multi-repo features by delegating work to specialized domains such as frontend, backend, specialist, and ops. This eliminates manual coordination and ensures consistent PRs across all affected repositories.

Do I need a feature spec to orchestrate end-to-end feature delivery?▼

A feature spec is accepted as input to guide the end-to-end feature delivery workflow, though tracking issues can also be provided. The orchestrator uses these inputs to guide domain-specific AI workers through implementation, testing, and PR creation cycles.

How does dependency sequencing work for multi-repo CI and PR lifecycle management?▼

Dependency sequencing for multi-repo PR lifecycle management enforces strict ordering, such as backend before frontend or specialized domains before integration. The orchestrator iterates in cycles, ensuring CI passes and grouping changes into coherent PRs only after dependencies are satisfied.

When should I not use AI workers for multi-repo feature orchestration?▼

AI workers for multi-repo feature orchestration are not suited for single-repo changes or features without clear dependency sequencing requirements. If your workflow lacks strict CI/PR lifecycle needs or does not require cross-repository coordination, manual implementation is more appropriate.