Skills Guide

Factory Run - Complete Pipeline

VerifiedCaution

Orchestrates sequential execution of 5 phases (intake, spec, plan, build, QA) for a full requirements-to-release pipeline. Each phase invokes a specialized skill and must pass its gate before proceeding. Helps automate standardized development workflows with mandatory checkpoints.

Sby Skills Guide Bot
DevOpsIntermediate
1006/2/2026
Claude Code
#pipeline#orchestration#release#requirements

Recommended for

Backend developerClaude CodeDevOps engineerGit automation

Our review

Orchestrates a full 5-phase pipeline from requirements to release, invoking sub-skills sequentially.

Strengths

  • End-to-end automation from requirements to release
  • Strict gate checks with immediate stop on failure
  • Direct skill invocation without nested complexity

Limitations

  • Requires all sub-skills to be properly configured
  • Can be lengthy for complex projects with many iterations
When to use it

When you need to run a complete and standardized pipeline from requirement gathering to delivery.

When not to use it

For isolated tasks or micro-changes that do not require the full workflow.

Security analysis

Caution
Quality score85/100

The skill orchestrates a pipeline by invoking other skills and running Node scripts. While not inherently malicious, the use of Bash to execute scripts could be leveraged if those scripts are compromised or if environment variables allow injection. The skill itself does not perform destructive actions, but caution is warranted due to the power of bash execution.

Findings
  • •Uses Bash to execute Node.js scripts for logging and instrumentation; ensure these scripts are trusted and paths are secured.

Examples

Pipeline complet requirements → release
/factory-run
Lancer le pipeline avec instrumentation
Exécute le pipeline complet /factory-run avec instrumentation activée.

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
Related skills

Docker Compose Architect

DevOps

Designs optimized Docker Compose configurations.

Claude CodeCopilotadvanced
430
156
1,482
Admin

Incident Postmortem Writer

DevOps

Writes structured and blameless incident postmortem reports.

claudeCursorWindsurfintermediate
141
43
483
Admin

Runbook Creator

DevOps

Creates clear operational runbooks for common DevOps procedures.

claudeCursorWindsurfintermediate
108
32
405
Admin