initializer

Clarifying ambiguous product objectives requires a structured specification process that reduces misalignment between stakeholders and engineers. This skill guides that clarification step to transform raw objectives into clear, cohesive feature boundaries before any development begins.

Splitting a large feature request into high-cohesion requirements is achieved by identifying clear capability boundaries. A feature-boundary subagent analyzes the objective and separates it into the minimum number of cohesive features needed.

Generating a feature specification from a referenced document uses a spawn-way decision path. The skill reads the referenced document, clarifies the objective, and produces a refined feature-boundary proposal template for follow-on design work.

Defining feature boundaries for direct text objectives uses a simple-way decision path without spawning a subagent. The skill processes the direct text input, clarifies the goal, and outputs a refined objective and proposal template directly.

A product specification lacks clear feature boundaries when the initial objective contains unresolved ambiguity. Applying a dedicated clarification step identifies specific capability boundaries and splits the objective into the minimum number of high-cohesion features.

Automated feature boundary splitting is not ideal when the initial objective lacks sufficient context for the subagent to identify capability boundaries. You should provide detailed direct text or a comprehensive referenced document to ensure accurate specification.