Pipeline orchestration
Skill IrfanSadiqRahat/constellation/methodology/pipeline-orchestration
Run a team formation's multi-stage pipeline end-to-end with role switching, handoffs, validation, and rollback.From its SKILL.md
npx -y skills add IrfanSadiqRahat/constellation --skill pipeline-orchestrationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.1 KB, 432 tokens by cl100k_base, as published. Nobody here has run it
pipeline-orchestration
When activated
The user says "run the saas-mvp pipeline for X" or invokes constellation run <formation> "<goal>". The agent becomes the orchestrator.
Pipeline execution loop
For each phase P in the formation:
1. Identify phase consumers (P.uses)
2. Materialize input artifact from prior phases' outputs
3. role-switching: become the role(s) in P.uses
4. brainstorm: refine the inputs into a ScopedBrief for THIS phase
5. planning-with-artifacts: produce a Plan for THIS phase
6. tdd-discipline: write tests for the phase output
7. subagent-dispatch: execute the plan
8. parallel-execution: if phase is fan-out, run agents concurrently
9. artifact-validation: mechanical check on output
10. verify-before-done: acceptance + downstream readiness
11. handoff-protocol: produce HandoffPacket for next phase
12. checkpoint: emit progress event; await human if gate set
13. Next phase
Failure handling
| failure | response |
|---|---|
| validation fail | revise (dispatch back to role) |
| acceptance fail × 3 | escalate to human |
| downstream-readiness fail | reopen prior phase |
| catastrophic (no roles fit, schema missing) | abort + write AbortReport |
Checkpointing
Every phase boundary writes a checkpoint to .constellation/checkpoints/<run-id>/:
- Input artifacts
- Output artifacts
- Validation results
- Decisions taken
Pipeline runs are resumable, replayable, and forkable.
Why not just "tell the agent to do it"
Unstructured prompts produce drift. The orchestrator wraps every phase in the same envelope: role-switch → plan → dispatch → validate → handoff. The user sees a clean progression; the agent stays disciplined.
Why this matters
Formalizing multi-phase pipelines with typed artifacts as the bus is what makes a 200-agent system actually executable end-to-end.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.