factory-spec

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.

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.

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.

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.

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.

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.