factory-spec

Generate specs, ADRs, and rules for gate-based MODEL phase workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/selossebdc-cell/portail-client-v2 --skill factory-spec-selossebdc-cell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-spec
Source: https://github.com/selossebdc-cell/portail-client-v2/tree/main/.claude/skills/factory-spec
Command: npx skills add https://github.com/selossebdc-cell/portail-client-v2 --skill factory-spec-selossebdc-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates the MODEL phase by automating the generation of specs, ADRs, and architectural rules, reducing manual coordination and drift across artifacts.

Core Features & Use Cases

  • Generates functional specs for the MODEL phase (PM scope) and corresponding ADR entries for architecture decisions.
  • Produces and synchronizes templates-driven artifacts (docs/specs/system.md, docs/specs/domain.md, ADRs) and enforces version deltas.
  • Coordinates a gated workflow (Gate 1, Gate 2) with deterministic agent delegation (PM, Architect, Rules-Memory) to deliver a consistent tech stack reference.

Quick Start

Kick off the MODEL factory-spec process and follow the gates to generate and synchronize specs, ADRs, and rules.

Frequently Asked Questions about factory-spec

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

FAQPage Schema
How do I automate generating specs and ADRs for my project workflow?

Automating spec and ADR generation is handled by orchestrating a gated workflow with deterministic agent delegation. It coordinates PM, Architect, and Rules-Memory agents to produce synchronized functional specs, architectural decision records, and memory rules.

What is a gate-based workflow for architecture decisions and specs?

A gate-based workflow for specs and ADRs uses sequential checkpoints, like Gate 1 and Gate 2, to coordinate deterministic agent delegation. It ensures functional specs and architectural decisions are synchronized and version deltas are enforced across artifacts.

Can I use template-driven artifact generation for both greenfield and brownfield projects?

Template-driven artifact generation works for both greenfield and brownfield project evolutions. The process applies dependency analysis and version deltas to synchronize functional specs and ADRs across system and domain documentation.

How do I synchronize functional specs and domain documentation across version deltas?

Synchronizing functional specs and domain documentation across version deltas is achieved through template-driven outputs. It coordinates agents to generate and update files like docs/specs/system.md and docs/specs/domain.md, reducing manual drift.

What are the limitations of automating architectural rule creation across agents?

Automating architectural rule creation requires strict adherence to the gated workflow structure to prevent coordination drift. It is limited by the need to satisfy specific requirements for PM specs, architect ADRs, and memory rules within the defined MODEL phase.

Does factory-spec coordinate PM and Architect agents for MODEL phase artifacts?

Yes, factory-spec coordinates deterministic agent delegation including PM, Architect, and Rules-Memory agents. This orchestration automates the MODEL phase by generating functional specs, architectural decisions, and memory rules.