ComponentsExamples

pm

user-story

The user-story molecule — one story as a card with id, statement, acceptance criteria, and priority/status/points meta, composed from the typed PM content model.

US-101
MustIn progress3 pts

As a reviewer, I want select a passage and start a thread on it, so that feedback lands where it applies.

  • Given a rendered report, when I select text, a comment affordance appears
  • When I submit, the passage is anchored and the thread opens
  • When I reload, the thread reattaches to the same passage

Note. Selection model only; no freeform pins in v1.

US-104
ShouldReady1 pt

As a archivist, I want export the document and its threads as markdown, so that review evidence survives the tooling.

  • Each thread quotes its anchored passage as a blockquote
  • Resolved threads carry their resolution
US-207
CouldBlocked

As a compliance reviewer, I want verify who said what and when.

  • Thread export carries author and timestamp per comment

Note. Blocked on the identity model decision (Q1).

US-101

As a reviewer, I want select a passage and start a thread on it, so that feedback lands where it applies.

MustIn progress3 pts

Full cards for three stories (note the tone-mapped priority/status and the reader-checkable criteria), then the same molecule at list density below.

Installation

Usage

UserStory: Root · Id · Statement · StatementPlain · Meta · Criteria · Notes · Full

Use when

  • A spec, backlog, or review document renders user stories from data
  • The same story data must export to markdown losslessly (with lib/pm toMarkdown)
  • Different densities are needed — the Full composition for spec bodies, Id+StatementPlain+Meta for list rows

Not for

  • A task tracker UI with mutable state — this renders authored data, it does not manage it
  • One-off prose bullet points — plain ArticleShell.List is enough