manager

Orchestrate MVP pipeline stages by coordinating sub-skills and enforcing transitions.

1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Invariants0/Eido --skill manager-invariants0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manager
Source: https://github.com/Invariants0/Eido/tree/main/backend/app/skills/manager
Command: npx skills add https://github.com/Invariants0/Eido --skill manager-invariants0

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the EIDO autonomous startup pipeline by coordinating sub-skills, automating transitions, and preventing stalled MVP cycles.

Core Features & Use Cases

  • Centralized orchestration of MVP lifecycle stages: ideation, architecture, builder, devops, business, and feedback.
  • Real-time monitoring, deterministic stage transitions, and retry guards to recover from interruptions.
  • Seamless spawning and management of subordinate skills to ensure end-to-end delivery with auditable progress.

Quick Start

Initiate a new MVP cycle or resume an interrupted pipeline using the backend API.

Frequently Asked Questions about manager

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

FAQPage Schema
How do I automate MVP pipeline orchestration across ideation and architecture stages?

MVP pipeline orchestration automates stage transitions across ideation, architecture, building, devops, business, and feedback by coordinating sub-skills and triggering backend API calls for deterministic sequencing.

What is end-to-end MVP pipeline automation and how does it handle state monitoring?

End-to-end MVP pipeline automation coordinates subordinate skills through reliable stage transitions while applying state monitoring and retry guards to prevent stalled cycles and recover from interruptions.

Can I resume an interrupted MVP pipeline without restarting the entire backend workflow?

You can resume interrupted MVP pipelines using backend API triggers, which apply state monitoring and retry guards to recover stalled cycles and continue stage sequencing without restarting.

What's the best way to prevent stalled MVP cycles during backend orchestration?

Preventing stalled MVP cycles requires centralized orchestration that enforces deterministic stage transitions, applies retry guards, and monitors state in real-time to recover from interruptions automatically.

Do I need backend API triggers to start a new MVP pipeline cycle?

Yes, initiating a new MVP cycle or resuming an interrupted pipeline requires backend API triggers to spawn subordinate skills, enforce stage transitions, and monitor progress for auditable delivery.