factory-spec

Generates specs, ADRs, and rules coordinating MODEL phase workflows for greenfield or brownfield projects.

10|5|Updated Jan 21, 2026

Search Tags:#architecture #orchestration #governance #ADR #specs

Ready to run

npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: factory-spec
Source: https://github.com/SylvainChabaud/spec-to-code-factory/tree/main/.claude/skills/factory-spec
Command: npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It acts as the orchestrator for the MODEL phase, automatically generating functional specs, ADRs, and technical rules to drive early architecture decisions.

Core Features & Use Cases

Automated MODEL orchestration: coordinates PM specs, ADRs, and rules memory to deliver consistent, versioned documentation.
Brownfield and Greenfield support: handles evolution modes, delta extraction, and template-driven outputs across gates.
Governance and validation: ensures templates, ADRs, and stack references are produced in a reproducible, auditable manner.

Quick Start

Provide your project brief and run the initial gate checks to trigger the MODEL phase.

Frequently Asked Questions about factory-spec

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

FAQPage Schema

What is automated spec generation for the MODEL phase?▼

Automated spec generation for the MODEL phase coordinates PM, architect, and rules-memory agents to produce functional specs, ADRs, and governance rules in a reproducible, auditable manner. It uses version deltas and templates to ensure deterministic outputs.

How do I generate ADRs and functional specs for a brownfield project?▼

To generate ADRs and functional specs for a brownfield project, provide your project brief to trigger the MODEL phase. The system handles brownfield evolution modes by extracting version deltas and applying template-driven outputs across strict gate-based workflow checks.

Can I use this orchestration workflow for greenfield architecture decisions?▼

Yes, you can use this orchestration workflow for greenfield architecture decisions. It supports greenfield modes to generate initial system and domain specs, ADRs, and technical rules guided by policy templates and a stack reference.

When do I need governance rules and ADRs in software architecture?▼

You need governance rules and ADRs in software architecture when driving early technical decisions that require reproducible, auditable documentation. Generating these artifacts ensures consistent, versioned documentation across project evolution.

What's the best way to orchestrate PM specs and rules memory for early architecture?▼

The best way to orchestrate PM specs and rules memory for early architecture is using a gate-based workflow that relies on policy templates and a stack reference. This coordinates agents to deliver consistent, versioned documentation deterministically.

Do I need policy templates and a stack reference to produce deterministic architecture specs?▼

Yes, you need policy templates and a stack reference to produce deterministic architecture specs. The orchestrator relies on these inputs to ensure that generated system and domain specs, ADRs, and governance rules are reproducible and auditable.