facilitating-product-vision

Files (8)

• SKILL.md
• evals.json · evals/
• items.md · evals/fixtures/backlog/
• ROADMAP.md · evals/fixtures/lean-roadmap/
• owner-notes.md · evals/fixtures/lean-roadmap/
• README.md · evals/fixtures/single-item/
• artifact-format.md · references/
• consumer-session.md · references/

SKILL.md (first lines)

# Facilitating Product Vision

Run a structured, owner-led session that turns product ambition into a
strategy-only vision artifact plus roadmap items. The output is two
artifacts (vision document + provisional `ROADMAP.md` rows) plus a
working session record — never a rebuild of an existing roadmap and
never a strategy invented under the owner's name.

The session is owner-driven. Every judgment call is owner-owned and
recorded with a one-line rationale; the facilitator does not invent
strategy. The artifact is the contract: a separate reviewer reads it
cold and must be able to defend the strategy and roadmap-item set.

## Contents

- The session (process checklist)
- Step 1 — Inputs & constraints (incl. Step 1a — decide the session mode)
- Step 2 — Strategy batch + Checkpoint 1
- Step 3 — Roadmap batch + Checkpoint 2
- Step 4 — Compliance & phase gates + Checkpoint 3
- Step 5 — Write the artifacts
- Step 6 — Council consults and handoffs
- Boundary routing
- References

## The session (process checklist)

Copy this checklist and check off items as you complete them. Owner
checkpoints are batched into three decision points — not one pause per
piece — to keep the session conversational and avoid late-session
rubber-stamping.

```
Vision Session Progress:
- [ ] 1. Inputs & constraints (ambition, current assets, envelope, non-negotiables, vision-artifact home)
- [ ] 1a. Decide mode (interactive multi-turn | declared one-shot | decisions pre-supplied inline) — the mode determines what fills Open Questions and what the final response must say
- [ ] 2. Strategy batch draft (vision, segments+JTBD, alternatives+non-goals+anti-vision, value model, north star + guardrails)
- [ ] 2a. CHECKPOINT 1 — strategy batch: present draft as questions-with-proposals; owner decides, every call recorded (skipped only when decisions are pre-supplied — recorded instead)
- [ ] 3. Roadmap batch draft (3–6 outcome themes banded Now/Next/Later under the capacity envelope; each theme's work emitted as roadmap items in the sibling item-row schema — ACs NOT emitted, they are plan-time artifacts; risk-first ordering)
- [ ] 3a. CHECKPOINT 2 — roadmap batch: same Q-with-proposal cadence (skipped only when decisions are pre-supplied — recorded instead)
- [ ] 4. Compliance & phase gates draft (consent/privacy/regulatory milestones, phase gates that unlock later segments)
- [ ] 4a. CHECKPOINT 3 — compliance + gates: confirm gates and owners (skipped only when decisions are pre-supplied — recorded instead)
- [ ] 5. Write artifacts (vision doc at the owner-confirmed home using EXACT Title-Case headings; append outcome-theme + roadmap-item rows to ROADMAP.md per the sibling item-row schema; record the session as a working artifact)
- [ ] 6. Optional council consults + handoffs (triaging-requirements ranks, designing-architecture plans the top roadmap item)
```

## Step 1 — Inputs & constraints

Capture what the strategy is constrained by. Read the consumer's
existing decision-doc convention (an `AGENTS.md`, a `docs/`, an ADR
index) for the project name, the team's pre-existing context, and the
canonical home for a long-lived document.

Ask the owner, and record in a one-line recap:

- **Ambition** — what the product is for, in the owner's own words.
- **Current assets** — what already exists (live code, design system,
  installed skills, an established `ROADMAP.md`, a prior vision doc).
- **Budget / time envelope** — team capacity, regulatory deadlines,
  quarters the session is planning into.
- **Non-negotiables** — pre-decided constraints the strategy must
  respect (legal posture, a platform commitment, a partner contract).

Then ask the **canonical home for the vision artifact** and record the
owner's answer. The vision artifact's path is a consumer decision, not
a default. The skill cites the artifact's content contract
(`references/artifact-format.md`, resolved against this skill's own
directory — not the project's); the owner decides where it lives.

If the owner names an established `ROADMAP.md`, read it. The session
appends to it; it never rebuilds it from scratch (the
established-once rule below).

### Step 1a — Decide the session mode

Three modes, picked from the prompt before drafting starts. The
mode determines what fills the artifact and what the final response
is required to say. Pick one and stay in it for the whole session:

- **Interactive multi-turn (default).** The session pauses at each
  of the three checkpoints and asks the owner. Owner decisions are
  recorded in-session as they are given.
- **Declared one-shot (no back-and-forth).** The owner has said
  they cannot answer back (e.g., "this is a one-shot, I'll read the
  doc later"). The session still writes the artifact (it does not
  end with an intention to write it later). Sections that require
  owner input — Segments & Jobs-to-be-Done, Alternatives &
  Non-goals, Value & Business Model, North Star + Guardrails,
  Compliance & Phase Gates, the capacity envelope — get a
  placeholder of the form
  `Open question: <what is needed, which section it will land in>`
  rather than invented content. The final response addresses the
  owner and lists every open question in plain text — using the
  literal words "owner" and "question" — so the consumer can
  recover the artifact on a later pass. The session does not
  present an invented strategy as decided.
- **Decisions pre-supplied inline.** The owner has already supplied
  every (or most) owner decisions for THIS run in this turn's
  prompt, or in the owner's own notes file the session has read. Each
  pre-supplied decision is recorded as a decision with its source
  cited. Anything the owner has NOT pre-supplied is surfaced as an
  Open Question. The session does not invent the missing inputs.

The boundary between *interactive* and *pre-supplied* is whether
the owner can answer back; the boundary between *one-shot* and
*pre-supplied* is whether the owner has already given the
decisions. A prompt that says "complete in one pass, here are the
answers" is *pre-supplied*, not one-shot: the decisions exist;
they are recorded. A prompt that says "I can't answer, write what
you can" is one-shot: the decisions do not exist; they are
surfaced.

## Step 2 — Strategy batch + Checkpoint 1

Draft the strategy batch. Read
[references/artifact-format.md](references/artifact-format.md) (resolved
against this skill's own directory) for the fixed section order and
section schemas — the body cites it, never duplicates it. Cover:

From hierovision/ai-framework, MIT.

More from hierovision/ai-framework