Skip to content

v1.7.0

Choose a tag to compare

@phuryn phuryn released this 07 Nov 18:46
· 90 commits to main since this release

Discovery now ends in one page you look at and decide on: the research, the key screens and the open decisions together. There is no Markdown proposal plus a separate prototype any more. And design is now ui-design.

Changed: propose ends in one artifact

  • One self-contained HTML page, kept in your repository (by default docs/product/proposal.html) and published from that file where your agent shares pages (in Claude, an artifact). It holds:
    • the research, every claim marked by kind with its source;
    • the value proposition and value curve;
    • the recommendation, with the first version's parts and the next builds on an impact-and-effort grid;
    • the jobs map;
    • one high-fidelity screen per key job, numbered to match the map, static or clickable as you agree;
    • the open decisions, each with the agent's recommendation;
    • the hypotheses and how the weakest is tested.
  • No separate app prototype. The first working version takes hours, and you try the full flow there.
  • You decide on the page. Where your agent's pages can keep your picks, as Claude's can, you pick there. Elsewhere you copy your choices into the chat, or just answer there. Either way the agent writes each pick into the page's file and the decision log in the same turn.
  • Before you see it, a fresh session that gets only the page and a reader's role says what is unclear.

Changed: the plan for a complex change. When the change alters what people see or leaves choices open, the part you review grows the same page: the key assumptions first, then the screens of the flows that change, then the choices still open. What the builders need stays in the repository's plan. app-lifecycle's stage 1 is now the page's screen options.

Renamed: design is ui-design (in app-stack). In a repository without app-stack, the old bare name reached Claude Code's own /design command, which only you can start. Its trigger now covers a product's screens and the mocks, prototypes or artifacts that show them, not every visual task.

Also:

  • value-curve: factors and the four actions are worded in the customer's direction ("Low price for one host", "Raise: one host pays less"), and "to create" stays until the product scores there.
  • value-curve and beachhead-segment: every score shown names its scale.
  • ui-design's visual checks: geometry assertions for insets, overlaps and cropped images.
  • The README's process graphic is redrawn to match.

What to do

  • Your agent instructions say "apply design": change it to "apply ui-design", or run the agent-instructions pass again. A copy of the skill under .claude/skills/design/ is stale; delete it once app-stack is installed.
  • You have docs/product/proposal.md: the next propose run rewrites it once as the page in the same place and removes the Markdown file; git keeps its history. An old prototype can stay as history.
  • You use propose with only the product pack: install app-stack too, for ui-design's method. Without it, propose falls back to the jobs map and a checked screenshot.

44 skills in six packs.

Install: README § Install. Lost at any point? Type /product:start-here (Codex: $product:start-here) and say what you have.