Our review
Orchestrates a complete pipeline from requirements gathering to release by invoking specialized factory skills sequentially.
Strengths
- Enforces strict sequential execution with gates at each phase.
- Provides a clear audit trail with logging at start and end.
- Delegates each phase to dedicated agents for focused execution.
- Produces a comprehensive final report summarizing all phases and artifacts.
Limitations
- Requires all other factory skills to be available and correctly configured.
- No parallel execution; all phases run sequentially.
- If any gate fails, the entire pipeline stops, which may be too rigid for some workflows.
When you need a structured, end-to-end pipeline for software development from initial requirements through release.
When you need flexibility to skip phases or run them out of order, or when the development process is not well-defined.
Security analysis
SafeThe skill orchestrates other skills sequentially and uses Bash only to run fixed Node.js logging scripts with static arguments, posing no risk of command injection or destructive actions.
No concerns found
Examples
Execute the factory-run pipeline from requirements to release.Start the factory-run pipeline for my project.Run the factory-run skill to orchestrate the full requirements-to-release process.name: factory-run description: "Pipeline complet requirements → release" allowed-tools: Read, Glob, Grep, Bash, Task, Skill
Factory Run - Pipeline Complet
Tu es l'orchestrateur master du pipeline complet requirements → release.
Workflow
Exécuter les 5 phases séquentiellement en invoquant chaque skill directement.
Chaque skill a son propre context: fork et gère sa délégation d'agent.
Initialisation
# Instrumentation (si activée)
node tools/instrumentation/collector.js skill '{"skill":"factory-run"}'
# Log démarrage
node tools/factory-log.js "PIPELINE" "started" "Démarrage du pipeline"
Phase 1 - BREAK
Invoque /factory-intake et attends le résultat.
Si Gate 1 échoue → STOP et rapport d'erreur.
Phase 2 - MODEL
Invoque /factory-spec et attends le résultat.
Si Gate 2 échoue → STOP et rapport d'erreur.
Phase 3 - ACT (planning)
Invoque /factory-plan et attends le résultat.
Si Gate 3 échoue → STOP et rapport d'erreur.
Phase 4 - ACT (build)
Invoque /factory-build et attends le résultat.
Si Gate 4 échoue → STOP et rapport d'erreur.
Phase 5 - DEBRIEF
Invoque /factory-qa et attends le résultat.
Si Gate 5 échoue → STOP et rapport d'erreur.
Finalisation
node tools/factory-log.js "PIPELINE" "completed" "Pipeline terminé avec succès"
Règles critiques
- Séquentiel strict : Chaque phase DOIT réussir (gate OK) avant la suivante
- Si un gate échoue → STOP immédiat, logger l'erreur, retourner rapport
- Pas de nesting : Invoquer les skills directement, ils gèrent leur propre fork
Rapport final
À la fin du pipeline, produire un résumé complet :
- Phases complétées avec statuts
- Artefacts générés (liste des fichiers créés)
- Issues détectées (si applicable)
- Prochaines étapes recommandées
Docker Compose Architect
DevOps
Designs optimized Docker Compose configurations.
Incident Postmortem Writer
DevOps
Writes structured and blameless incident postmortem reports.
Runbook Creator
DevOps
Creates clear operational runbooks for common DevOps procedures.