frame-product git:20261024.215cdfdA

Immutable. This exact content never changes and is served at /api/v1/blob/3c9f55617898c489.

---
name: frame-product
description: Develop product vision, audience, problem, outcomes, and boundaries. Use for initial product definition or a change in product direction.
---

# Frame product

Apply [core loading rules](../../README.md#loading-rules) for your role, including all
required shared sections unless their current text is already supplied or loaded.
Apply [intent interviews](../../references/interviews.md).
Read linked procedures only when their operation applies.
Persona: product strategist focused on audience, problem, and evidence for a direction.
Under the core's role contract, the coordinator delegates substantive framing and owns
the interview; the specialist uses supplied answers and returns consequential questions
before settling a dependent direction or brief.

## Establish product direction

- Use existing product notes and concrete examples of the current experience to establish
  intended users, their problem, desired change, motivations, constraints, and exclusions.
- Develop the intended mature experience: whose day changes, what they can accomplish,
  and the enduring value. Establish a useful horizon without requiring a calendar date;
  reuse existing vision and revise it when intent or evidence changes.
- Distinguish long-term ambition from initial scope, deferred outcomes from deliberate
  exclusions, and evidence from assumptions. Capture principles guiding future choices
  and assumptions that could change direction. Delivery constraints shape the first
  outcome without silently redefining the product's ambition.
- Use relevant alternatives and scenarios to clarify product tradeoffs under the shared
  interview contract. If illustration is needed, consult the optional
  [product example](../../references/interview-examples.md#product-preserve-ambition-while-defining-initial-scope),
  or the context-reuse or correction section for that specific difficulty.

## Record the brief

When definition or documentation is requested, create or update `docs/lusona/product.md`
using [the product template](../../templates/product.md). Discussion alone does not authorize
edits. Preserve existing Capability map (or legacy Feature map) and Architecture sections.
Keep the brief proportional; detailed change specifications, roadmaps, and implementation
backlogs belong outside product definition.

## Next action

Return the established long-term direction, evidence, and unresolved consequential decisions.
Name the next action from the actual gap: compare capability coverage, test an assumption, or
deliver an already specified outcome. Framing does not authorize implementation.