Our review
Orchestrates a complete pipeline from requirements to release by sequentially executing five phases (intake, spec, plan, build, QA) with validation gates at each step.
Strengths
- Automates the entire end-to-end development cycle
- Ensures rigorous quality control through validation gates
- Produces a detailed final report with artifacts and issues
- Strict sequential execution prevents unresolved dependencies
Limitations
- Requires all sub-skills (factory-*) to be available and operational
- No tolerance for intermediate failures: a failing gate stops the entire pipeline
- No parallelization possible between phases
Use this skill when you need to run a complete software development pipeline from requirements to release, with validation at each stage.
Do not use it for isolated tasks or if you need to execute only part of the pipeline; prefer the individual skills (factory-intake, etc.) instead.
Security analysis
CautionThe skill uses Bash to run Node.js instrumentation and logging scripts. While no destructive commands are apparent, the use of shell execution for automation introduces risk if the scripts are compromised or handle untrusted input.
- •Executes Bash commands via Node.js scripts; ensure these scripts are safe and not subject to injection.
Examples
Run the complete factory pipeline from requirements to release.Start the factory pipeline and show detailed logs for each phase.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.