factory-intake

Orchestrate the BREAK phase to normalize requirements into brief, scope, and acceptance criteria.

10|5|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-intake
Source: https://github.com/SylvainChabaud/spec-to-code-factory/tree/main/.claude/skills/factory-intake
Command: npx skills add https://github.com/SylvainChabaud/spec-to-code-factory --skill factory-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and orchestrates the BREAK phase to convert ambiguous requirements into a concrete brief, scope, and acceptance criteria, enabling a deterministic start for the project.

Core Features & Use Cases

  • Orchestrates Gate 0 validation and Gate 1 remediation, guiding the user through the intake workflow.
  • Delegates analysis and generation tasks to an analyst, including generating and updating questions, briefs, scopes, and acceptance criteria.
  • Manages an interactive questioning flow, records responses, and ensures alignment before moving to model and design phases.

Quick Start

Trigger the /factory-intake workflow with your current requirements file and follow the clarifying prompts.

Frequently Asked Questions about factory-intake

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

FAQPage Schema
How do I turn ambiguous project requirements into a structured brief and acceptance criteria?

To turn ambiguous requirements into a structured brief, you can trigger an automated intake workflow that normalizes inputs, applies gate validation, and generates concrete scope and acceptance criteria.

What is the best way to automate the intake gate check for project briefing?

Automating intake gate checks involves orchestrating a validation protocol that guides interactive questioning, records responses, and ensures alignment before moving to design phases.

Can I use this requirements intake workflow for both new and existing brownfield projects?

Yes, the requirements intake workflow supports both greenfield and brownfield projects by normalizing requirements and applying consistent gating protocols across different project contexts.

How do I generate project scope and documentation from a raw requirements file?

Generating project scope from a raw requirements file is done by delegating analysis tasks to an analyst subagent that normalizes the file into a structured brief and documentation artefacts.

Does automated intake briefing work without manually writing validation rules?

Automated intake briefing works without manual validation rules by enforcing a built-in gating protocol that orchestrates Gate 0 validation and Gate 1 remediation automatically.