prod-concept-intake

Normalize raw project inputs into a discovery snapshot with labeled uncertainties.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill prod-concept-intake
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prod-concept-intake
Source: https://github.com/FernanSuoza/AIDD-project-bootstrap/tree/main/templates/skills/prod-concept-intake
Command: npx skills add https://github.com/FernanSuoza/AIDD-project-bootstrap --skill prod-concept-intake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize scattered, incomplete, or contradictory project inputs into a single discovery snapshot that captures the problem framing, outcomes, assumptions, and risks so architecture work can start with a shared understanding and visible decision areas.

Core Features & Use Cases

  • Source consolidation: Read product briefs, support notes, research, and competitor references to extract goals, actors, constraints, and evidence into a unified narrative.
  • Conflict and uncertainty labeling: Mark contradictions and unknowns explicitly as QUESTION, ASSUMPTION, RISK, or CONFLICT and surface targeted human review questions.
  • Artifact production and handoff: Produce a normalized context-and-goals document, glossary, and a HUS-* concept-review story to request human decision before architecture proceeds.
  • Use case example: Turn a short product brief plus scattered stakeholder notes into docs/architecture/context-and-goals.md with labeled assumptions and a review story for the concept-review gate.

Quick Start

Run the prod-concept-intake skill with all available source documents and instruct the assistant to write the normalized concept summary into docs/architecture/context-and-goals.md and create the concept-review HUS story.

Frequently Asked Questions about prod-concept-intake

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

FAQPage Schema
How do I normalize scattered product briefs and stakeholder notes into a single discovery snapshot?

To normalize scattered inputs, the skill consolidates briefs, research, and notes into a unified context-and-goals document, capturing problem framing, outcomes, assumptions, and risks for concept review.

What is the best way to label assumptions and contradictions during project onboarding?

Labeling assumptions and contradictions during onboarding involves marking unknowns explicitly as QUESTION, ASSUMPTION, RISK, or CONFLICT, then surfacing targeted human review questions before architecture work proceeds.

How do I create a context-and-goals artifact from mixed-source documents for early architecture phases?

Creating a context-and-goals artifact from mixed-source documents requires extracting goals, actors, and constraints into a normalized narrative, producing a structured summary and glossary for the concept-review gate.

Can I use this normalization process for risk analysis when project inputs are incomplete?

Yes, this normalization process supports risk analysis by extracting and labeling uncertainties from incomplete inputs, generating a HUS-* review story to request human decisions on visible conflicts and assumptions.

Does the discovery snapshot generation require human review before architecture proceeds?

Yes, discovery snapshot generation requires human review; it produces a HUS-* concept-review story and preserves original headers to ensure stakeholders validate labeled uncertainties before architecture work begins.

When do I need to consolidate mixed-source documents using a product brief normalization skill?

You need to consolidate mixed-source documents using product brief normalization during onboarding and early architecture phases when scattered research notes and briefs must be unified for a concept-review gate.