Set direction and goals

Start with the research you already have, and each request below writes one file in docs/product/shaping/.

Read the situation

To pull the themes out of interviews, surveys, or support transcripts, ask:

Synthesize our stakeholder interviews into the themes that recur across groups, and say which group each came from.

The agent writes stakeholder-synthesis.md and keeps groups apart when they disagree. To bring your analyses together, ask for a SWOT with run-swot; Analyse the market covers the others.

Set the direction

To state the direction as if it already shipped, ask:

Write the PRFAQ for this concept: press release first, then the customer and internal FAQs.

The agent writes prfaq.md, a press release and two FAQs, so the customer benefit has to be stated plainly. Read the press release to someone outside the team and ask what the product does, then approve it before it routes to work.

Route it to work

To turn the approved direction into team goals and queued work, ask:

Cascade our company OKRs to team level, identify the gaps, and route them to the shaping queue.

The agent writes okr-cascade.md and adds each gap to workspace.toml, the file where the repository tracks planned work, so core must be installed. Read those entries before you approve, because a vague gap becomes a queued item someone else must interpret. For UX and content, ask for define-ux-strategy and define-content-strategy.

Next, shape a feature from one of the queued gaps.