Skip to content
Shipped and released

Now

Page 2 of 14. Every release ever published is still here — across these pages, in theAtom feed, and at its own permanent link. Nothing is dropped as it ages.

  1. product-engineering 2.0.0

    • ux-writing now ships in the experience-design pack, beside the screen flows and brand register it writes from. After upgrading, reinstall product-engineering once so it lets go of the old copy; the product-engineering 2.0.0 release note has the steps.
    Release notes for product-engineering 2.0.0

  2. product-engineering 1.0.3

    • Requirements ingest now says when it applies: a multi-slice or cross-repository document goes to author-delivery-brief create, a single-feature one to new-spec; shipped skills state the content-not-runtime rule directly instead of citing internal records.
    Release notes for product-engineering 1.0.3

  3. product-engineering 1.0.5

    • Every product-engineering skill now ships activation evals, so you can check that each shaping step fires on the right requests and stays quiet on its neighbours'.
    Release notes for product-engineering 1.0.5

  4. desk-research 1.1.10

    • The pack's activation-eval comment now names the live agentbundle pack evals run command instead of a removed script.
    Release notes for desk-research 1.1.10

  5. figma 0.3.4

    • The pack's activation-eval comment now names the live agentbundle pack evals run command instead of a removed script.
    Release notes for figma 0.3.4

  6. core 3.1.4

    • The pack's activation-eval comment now names the live agentbundle pack evals run command instead of a removed script.
    Release notes for core 3.1.4

  7. product-engineering 1.0.4

    • The nine longer-route shaping skills now open with what they produce, in the words people use, and take 45% less room in the skill listing every session loads.
    Release notes for product-engineering 1.0.4

  8. converters 0.9.8

    • The pack's activation-eval comment now names the live agentbundle pack evals run command instead of a removed script.
    Release notes for converters 0.9.8

  9. experience-design 4.1.6

    • The pack's activation-eval comment now names the live agentbundle pack evals run command instead of a removed script.
    Release notes for experience-design 4.1.6

  10. contracts 0.3.8

    • The pack's activation-eval comment now names the live agentbundle pack evals run command instead of a removed script.
    Release notes for contracts 0.3.8

  11. architect 0.15.17

    • The pack's activation-eval comment now names the live agentbundle pack evals run command instead of a removed script.
    Release notes for architect 0.15.17

  12. core 3.1.2

    • The offline intent view opens on four session-start questions: what to work on next, what is open under a capability, what has no parent, and what is broken.
    • Each item shows its name first, its state as a word plus a shape, and a plain next step that names the skill to use and why.
    Release notes for core 3.1.2

  13. core 3.1.3

    • Review failures recorded by a shadow-enabled run now surface as read-only knowledge candidates through a pull scan, and one invalid merged knowledge record is quarantined on enquiry and the distillation pending page instead of breaking every read.
    Release notes for core 3.1.3

  14. product-engineering 1.0.2

    • Discovery guidance now hands off through work-intake at G3 and ingests an outside requirements document as a new brief.
    Release notes for product-engineering 1.0.2

  15. core 3.1.1

    • Open briefs and specs are now named by their title in navigate-intents query results and in the offline export, so you can tell them apart without opening each file.
    Release notes for core 3.1.1

  16. core 3.1.0

    • See every outstanding intent, brief, and spec placed under its parent intent, without opening files one by one and without workspace.toml. The new navigate-intents skill derives the intent graph from preamble headers each time it is asked and writes nothing back.
    • Walk the intent tree by level, parent, children, and recorded status. One broken parent link no longer hides the rest of the tree — it shows as a flagged line naming what is wrong. An incomplete outstanding-work list is refused rather than returned silently.
    • close-work now checks every intent ancestor that an artifact's parent pointers record, including capability, outcome, and opportunity parents. close-work and navigate-intents now agree on every parent link.
    • When an intent and a brief (or spec) share a slug, both now count, so a parent can no longer look ready to close while one of them is still open.
    • A broken parent pointer or a fault while building the intent tree now refuses closure with a named reason: parent-edge-refused, artifact-not-in-graph, or intent-graph-unavailable.
    • Relate two intents with one Related intents: line. navigate-intents shows the relation from both ends, and the intent lint refuses a value that is malformed, names the intent itself, or matches no live intent of that kind.
    • Export the whole intent graph as one HTML file that opens offline, to share with a reviewer or browse without a terminal. It lists every intent with its parents, outstanding work, refused pointers, and parentless intents. It links each source file. It works from the keyboard. Record text is shown as plain text. The file is always written outside the repository.
    Release notes for core 3.1.0

  17. product-engineering 1.0.1

    • Frame an intent that sits beside another one with an optional Related intents: line. The template offers it as comment-only guidance, so it stays absent until you fill it.
    Release notes for product-engineering 1.0.1

  18. core 3.0.5

    • Add a conforming reviewer to any repository without changing work-loop code. The structured review boundary ships a generic reviewer port: select an obligation, submit a versioned structured report, and the boundary assesses findings and derives review readiness from it. No reviewer-role condition or reviewer-specific hook exists in the runtime modules.
    • Integrate the compatibility adapter that reconciles legacy review events with structured boundary facts. The legacy review authority and reviewer-specific procedure remain active; moving authority belongs to the review-authority cutover follow-on.
    Release notes for core 3.0.5

  19. core 3.0.4

    • workspace-status now suggests intent for a shape entry. Install product-engineering 1.0.0 or later so that suggestion resolves to a skill you have.
    Release notes for core 3.0.4

  20. product-engineering 1.0.0

    • Shape product work with one skill. Use intent frame to turn an idea into an outcome and the opportunity behind it. Use intent de-risk to test the assumption that would sink it. Use intent decompose to break what survives into child intents or a delivery contract.
    • Not sure how much shaping a piece of work needs? Ask intent which way to go. Route mode names the short, longer, or supervised route and where it starts, then offers the first step without taking it.
    • Every intent mode shows where you are on the intent lifecycle, offers the next step, and recommends the shaping review at the point it applies.
    Release notes for product-engineering 1.0.0
Back to the top