receive-brief

To break down a multi-feature product brief into shippable specs, the Skill decomposes externally authored PRDs and solution handoffs into independently shippable delivery slices. It elicits load-bearing details like outcome and scope to scaffold delivery-ready specifications.

Traceability from a product brief to shipped implementation is tracked using automated coverage rollups and spec back-links. This creates a coverage map so teams can track a multi-feature brief from intake through delivery without losing context.

Yes, this approach works with incomplete product briefs that lack user stories by eliciting missing load-bearing details without rejecting the input. It processes requirements packets that span several outcomes, with or without user stories.

To decompose a PRD into shippable delivery slices, the Skill applies shippability-based decomposition to confirm the cut before scaffolding work. This ensures each slice can independently move through the normal delivery loop.

Yes, you can use this for solution handoffs spanning multiple features and teams. The Skill is designed to break externally authored requirements packets into spec-sized slices that can each move through the normal delivery loop.

You should not use automated spec decomposition for product briefs when a brief covers a single, isolated feature rather than spanning multiple outcomes. It is built for multi-feature PRDs requiring shippable slices and coverage rollup.