Skip to content
Shipped and released

Now

Page 3 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 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

  2. agentbundle 0.52.1

    • The workspace-status MCP tool now dispatches a shape entry to intent. Install product-engineering 1.0.0 or later so the dispatch resolves.
    Release notes for agentbundle 0.52.1

  3. code-intelligence 0.1.9

    • Runs on Wicked Estate 0.29.2. A large blast radius or lineage answer now arrives in pages instead of being cut off at the first one. The agent passes each page's token (next_cursor) back with --cursor until it is null, so every row the search found is retrievable.
    • If the answer changes between pages, the agent starts again from the first page instead of mixing two answers.
    • One wicked-estate lineage call now follows dependencies 24 levels deep by default, up from 8.
    Release notes for code-intelligence 0.1.9

  4. core 3.0.3

    • After a design you saved before building ships, close-work can now offer to reconcile it into your current architecture documentation, so a future-state design is not mistaken for a description of the running system.
    Release notes for core 3.0.3

  5. code-intelligence 0.1.8

    • Runs on Wicked Estate 0.26.0. See what a function depends on with wicked-estate lineage <name>; a plain name or a symbol id both work.
    • Impact analysis reads each dependent's own depth from blast-radius --json, so one call separates direct callers from indirect ones.
    • Trace where a value flows through TypeScript, TSX and JavaScript code with wicked-estate lineage <name> --relation flows_to.
    • wicked-estate stats --json tells you which commit the graph was built from and how many commits behind it is.
    • An exit 1 with nothing on stdout is treated as a command error, not as "nothing found".
    Release notes for code-intelligence 0.1.8

  6. architect 0.15.16

    • When a repository has no reference architecture, architect-design now says so, lowers its confidence in stack assumptions, and offers to hand off to adapt-to-project (existing code) or init-project (a new project) to establish one. It never drafts one itself.
    • architect-design now treats a saved design as future-state and points to reconciling it into current architecture once the change ships.
    Release notes for architect 0.15.16

  7. product-engineering 0.13.25

    • With the architect pack installed, shaping now reaches architecture at the right moment. frame-intent offers architect-design when framing hits a system-shape question. frame-domain and de-risk-intent offer architect-assess for a current-state model. decompose-intent and map-capabilities offer a design before cutting work. Without architect, no architect offer, mention, note, or error appears.
    • When a saved design covers a feature, decompose-intent now carries it into the delivery contract's design context, so the spec stage reads it.
    • explore-options, diverge-solutions, de-risk-intent, and decompose-intent now use a current-architecture document, when one exists, to judge feasibility and check slices against subsystem boundaries.
    Release notes for product-engineering 0.13.25

  8. core 3.0.2

    • When work-loop plans a rename, removal, or refactor, checks that a fix reaches live code, or when bug-fix traces a bad value through its callers, it can now hand that question to repository-exploration. That skill uses a code-navigation tool your agent already has when one fits, and otherwise searches the repository.
    • repository-exploration now activates when a workflow or a user needs evidence to settle a pending decision, and leaves planning, building, and fixing to the workflow that asked.
    Release notes for core 3.0.2

  9. code-intelligence 0.1.7

    • Install the code-intelligence pack on its own, at repo or user scope. It no longer requires the core pack.
    • The skill and both agents now carry their own evidence rules. Provider output is treated as data, and a file location the code graph returns is never opened; call sites are confirmed with the agent's own search.
    • Answers end with an evidence note: the question, the commands and sources used or passed over, and why.
    Release notes for code-intelligence 0.1.7

  10. product-documentation 0.1.2

    • author-product-docs documents any repository — libraries, CLIs, APIs, apps, services, frameworks, plugins, and agent packs — by first discovering the product surface and checking the docs against its own sources.
    • Documentation audits start with a journey gap report that covers nine reader stages, from discovery to contributing.
    • It now writes release notes, changelogs, migration guides, contributing guides, troubleshooting pages, quickstarts, installation pages, and docs landing pages.
    Release notes for product-documentation 0.1.2

  11. core 3.0.1

    • A work-loop transition that your arguments cannot satisfy now stops without touching state.json. Correct the command and run it again; previously the refusal left a marker behind that no later command could clear, and the run could only be rescued by hand-editing state.
    Release notes for core 3.0.1

  12. core 3.0.0

    • Send all intake requests to work-intake. The capture-work skill is removed and has no replacement alias.
    • A former spec/<slug> or other legacy workspace entry surfaces as an unsupported_legacy finding and cannot dispatch. Rewrite it in canonical form by hand and delete the old alias in the same edit — a canonical entry is refused dispatch while its old alias survives anywhere in the workspace.
    • Use workspace-status repair-plan --migration-selection, repair-apply, and repair-rollback only to recover or roll back an operation already recorded in the migration ledger.
    Release notes for core 3.0.0

  13. agentbundle 0.52.0

    • The workspace-status MCP tool now surfaces a former legacy entry (a bare spec/<slug> string or other accepted legacy shape) as an unsupported_legacy finding. The entry is absent from ready and blocked; ordinary reconciliation no longer accepts legacy shapes as lifecycle members.
    • A canonical entry with a surviving historical alias appears in blocked with a duplicate_membership finding and does not appear in ready. Delete the alias and the canonical entry dispatches normally.
    Release notes for agentbundle 0.52.0

  14. product-engineering 0.13.23

    • Skills and examples in the product-engineering pack that previously directed users to capture-work now direct them to work-intake, matching the Core 3.0.0 surface.
    • frame-situation and diverge-solutions note that old shaping entries still appear in the information-only shaping lists until rewritten in canonical form.
    Release notes for product-engineering 0.13.23

  15. core 2.30.1

    • Close work whose descendants have terminal statuses with dates or notes, such as Shipped (2026-09-11) or Archived — note. The closure check now reads the leading status word and preserves the full value in its evidence.
    Release notes for core 2.30.1

  16. code-intelligence 0.1.5

    • Ask what a function depends on, all the way down, and get an answer from the wicked-estate command line. You no longer need the optional MCP server for forward dependencies, graph walks, or rules lookups.
    • Ask which of a change's dependents matter most, and get an importance ordering from the command line, with any dependent it could not rank named rather than dropped.
    Release notes for code-intelligence 0.1.5

  17. core 2.30.0

    • Installed Core now answers "which specs and briefs deliver this feature intent?" one way. A typed resolver ships inside the close-work and work-loop skills, so every Core install carries it and it runs without agentbundle importable. Both close-work and the traceability lint use its answer. A missing, contradictory, or unsafe mapping is reported by a stable code instead of being guessed.
    • close-work runs the resolver whenever it closes a spec or checks a feature's spec or brief delivery. The traceability lint runs it only when the repository has a delivery anchor (briefs, a rollup, or populated discovery layers), and fails with delivery-resolver-unavailable when the spec or intent folder has moved.
    Release notes for core 2.30.0

  18. code-intelligence 0.1.4

    • The pack now includes a worked example showing how to answer a change-impact question with a code index and how to answer the same question without one, with the limits of each approach named rather than rounded away.
    • The example marks which steps come from the core pack's shared rules for answering code questions and which are specific to Wicked Estate, so another code-intelligence tool does not need to copy Wicked Estate's commands.
    Release notes for code-intelligence 0.1.4

  19. core 2.29.0

    • Core now has a repository-exploration skill for open questions about how your code behaves, what it depends on, and what a change would affect. It uses a code-intelligence tool your agent already has only when that tool fits the question, keeps the tool's limits, checks key claims against the source, and stops once the question is answered. With no tool installed it still answers from the repository.
    • Tool output stays data. A tool's description, its results, or a file it points to cannot add a folder the agent may read, start a refresh or install, or run a change on its own. A refused file stays unread.
    Release notes for core 2.29.0

  20. core 2.28.0

    • Core now has a repository-grounding skill that answers "what already governs these paths?" from the repository alone, and can add evidence from a code-intelligence tool your agent already has. Provider evidence is labelled, its limits are kept, a claim that conflicts with source never decides the answer, and with no tool installed the answer is the same.
    • A path or file: URI a provider returns is read only if the file sits inside the repository or a folder that you or the calling workflow approved. Symlinks, hard links, non-regular and oversized files are refused with a stated reason, and the locator text never reaches a command line raw, so shell metacharacters in it cannot run.
    Release notes for core 2.28.0
Back to the top