Skip to content

v1.13.0 — The vibe-coding onramp: Keel proposes the v1

Choose a tag to compare

View all tags
@joseconti joseconti released this 16 Jul 12:11
v1.13.0
eb2b37a

This release makes Keel genuinely usable by someone with no development background who arrives with nothing more than a vague idea. The structure was already there; now the front door is too.

Added

Vague-idea onramp (Phase 1, step 1). A vague idea is a valid entry, not a defect to push back on. When the user cannot answer the discovery questions in their own terms, Keel does not interrogate — it proposes 2–3 concrete interpretations of the idea in plain language (grounded in the competitive scan where it helps) and lets them pick or correct one. The phase never stalls on a question the user cannot answer.

Proposed v1 — the assistant proposes, the user reacts (Phase 1, step 3). Nobody is asked to build a feature list from a blank page anymore. From what discovery has already produced — table stakes from the competitive scan, differentiator candidates from real user demand, AI/MCP added-value proposals, the honest assessment, and the user's own idea — Keel assembles a proposed v1 and presents it unprompted, always, as a draft to react to, never as a decision already made:

  • Every feature carries its why — table stakes (competitors X, Y), differentiator (source), AI/MCP added value, or user's idea — so a non-developer can judge each row on its merits.
  • An explicit "Later" list makes cutting visible and painless: deferred, not lost.
  • The scope is tight by default, and removing items is explicitly invited. The proposal is a starting point, not an anchor — the user's corrections always win.

If the user already arrives with a defined scope of their own, Keel does not re-propose from scratch: it presents the diff against the scan instead — missing table stakes, items that belong in Later, differentiator candidates worth considering.

Every question answerable by a non-developer (all phases). Every question Keel asks now carries a recommended default and a one-line plain-language explanation of what it means and why the default is sensible. "I don't know / whatever you think" is a valid answer: the default is recorded in docs/decisions.md as "default accepted" and the work moves on.

Changed

  • The skill's trigger description now names the vague-one-line-idea, no-technical-background entry (Keel shapes it and proposes the v1 unprompted), and the Phase 1 row of the phase map reads "proposed v1 (assistant proposes, user reacts)" instead of "feature discussion".

Full changelog: keel/CHANGELOG.md

Assets 2
Loading