skills.rest
SylvainChabaud
SylvainChabaudCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

factory

Orchestrate requirements-to-release project pipelines with sequential QA gates.

10|5|Updated Jan 21, 2026
Search Tags:#requirements#qa#release#pipeline#brownfield#greenfield#orchestrate
One-click install
npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: factory
Source: https://github.com/SylvainChabaud/spec-to-code-factory/tree/main/.claude/skills/factory
Command: npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the entire software delivery pipeline from requirements to a release-ready project, coordinating greenfield and brownfield modes to reduce manual handoffs.

Core Features & Use Cases

  • End-to-end pipeline orchestration across intake, specs, planning, build, and QA.
  • Mode-aware execution that detects greenfield (V1) or brownfield (V2+) and adjusts prerequisites and artifacts.
  • Enforced sequential gates with automatic remediation prompts and user-assisted recovery.

Quick Start

Invoke the /factory command to run the complete pipeline from input/requirements.md to release/.

Frequently Asked Questions about factory

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

FAQPage Schema
How do I automate the software delivery pipeline from requirements to release?▼

You can orchestrate the end-to-end software delivery pipeline by running the /factory command, which coordinates intake, specs, planning, build, and QA phases into a release-ready project.

Does this release pipeline support both greenfield and brownfield project scenarios?▼

Yes, the pipeline detects greenfield (V1) and brownfield (V2+) modes, automatically adjusting prerequisites and generated artifacts to suit the specific project scenario being orchestrated.

How do sequential gates handle build failures or QA errors during pipeline orchestration?▼

Sequential gates enforce strict progression by triggering automatic remediation attempts for build or QA errors, providing user-assisted recovery prompts and tracking state via node tools.

What is the entry point for running the complete requirements to release workflow?▼

The workflow begins by invoking the /factory command, which processes the input/requirements.md file and orchestrates the full pipeline through to the generated release/ output directory.

When should I use automated pipeline orchestration instead of manual handoffs for software delivery?▼

Automated pipeline orchestration is ideal for reducing manual handoffs and enforcing strict sequential gates when transforming project requirements into a release-ready state across complex build and QA phases.

Are there external dependencies required to run the end-to-end release pipeline?▼

No external dependencies are required to run the end-to-end release pipeline; the orchestration relies entirely on internal state tracking via node tools and enforced sequential gates.

Related Skills

Explore More Software Engineering Skills→
bvshibvshi

10x-shape

Guide structured discovery to create a Product Requirements Document draft.

Community
Advanced
sun2443sun2443

deploy-checklist

Generate a pre-deployment checklist with deploy, post-deploy, and rollback sections.

Community
Intermediate
LeKayLeKay

smoke-check

Execute automated and manual smoke tests in CI/CD pipelines.

Community
Advanced
dejavoo21dejavoo21

sparc-methodology

Automate structured software development with SPARC methodology phases and multi-agent orchestration.

Community
Advanced