factory-intake

Clarify ambiguous requirements into brief, scope, and acceptance criteria documents.

Updated Aug 23, 2026

Search Tags:#workflow #scoping #requirements #clarification #acceptance-criteria #brief-generation #break-phase

Ready to run

npx skills add https://github.com/selossebdc-cell/portail-client-v2 --skill factory-intake-selossebdc-cell

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: factory-intake
Source: https://github.com/selossebdc-cell/portail-client-v2/tree/main/.claude/skills/factory-intake
Command: npx skills add https://github.com/selossebdc-cell/portail-client-v2 --skill factory-intake-selossebdc-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies ambiguous requirements into a concrete brief, scope, and acceptance criteria, enabling faster alignment and fewer rework in product initiatives.

Core Features & Use Cases

Automates requirement clarification during the BREAK phase by reading the current state, validating inputs, and guiding the user through questions.
Generates essential documents (brief.md, scope.md, acceptance.md) or enriches existing ones in greenfield or brownfield evolution workflows.
Supports optional resources (scripts, references, assets) to enhance the intake process as needed.

Quick Start

Run the factory-intake skill to read the current state, perform gate checks, and generate the core documentation for project scoping.

Frequently Asked Questions about factory-intake

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

FAQPage Schema

How do I clarify ambiguous requirements into acceptance criteria and a project scope?▼

To clarify ambiguous requirements, the system validates current inputs and poses targeted questions to generate a concrete brief, project scope, and acceptance criteria for greenfield or brownfield initiatives.

What is the best way to generate a brief and scope for greenfield or brownfield evolutions?▼

Generating a brief and scope for greenfield or brownfield evolutions requires orchestrating gate checks during the BREAK phase to produce core governance documents like brief.md, scope.md, and acceptance.md from templates.

How do I automate requirement clarification and gate checks during the BREAK phase?▼

Automating requirement clarification during the BREAK phase requires running a process that reads the current project state, validates provided inputs, and guides the user through questions to produce core governance documents.

Can I enrich existing project documentation instead of creating new briefs from scratch?▼

Enriching existing documentation is fully supported for brownfield evolutions, allowing the intake process to update current briefs, scope definitions, and acceptance criteria rather than generating entirely new files from templates.

Do I need to provide optional resources like scripts and references for project scoping?▼

Optional resources such as scripts, references, and assets are not required but can be managed under the SKILL definition to enhance the intake process and support the generation of core project scoping documents.

Why does requirement scoping fail when initial inputs are not validated?▼

Requirement scoping fails without input validation because ambiguous needs cannot be reliably transformed into concrete acceptance criteria, leading to misaligned project briefs and increased downstream rework.