Skip to content

v1.24.0

Latest

Choose a tag to compare

@github-actions github-actions released this 10 Nov 09:44
a2bfe68

The spec track (Track S, Experimental): three advisory skills before a ticket exists. A spec is
read by fresh reviewers and gets a counted verdict before any code. None of the three closes a gate,
calls a lifecycle skill, or creates a ticket or an epic; the one link to the lifecycle is a
Spec: <path> line a user may add to an epic or a ticket, which design reads (S4).

  • Added (skills): /mango:brainstorm (idea → brief: one open question per turn, reviewer lenses
    only after a readiness gate the user passes), /mango:spec (brief or notes → spec: one section at a
    time, the user chooses every decision from at most three unranked options, the spec is compared with
    its brief and never edited to match it), /mango:spec-review (one reviewer per lens in parallel; a
    lens with no result line is retried once, then not run, never zero findings; resolve as CONTEST,
    ESCALATE, PROPOSE FIX or DECLINE; the review record goes into the document itself, on the user's yes).
  • Added (agent): spec-reviewer — tools: Read, Grep, Glob, omitClaudeMd: true, Sonnet.
    validate.py pins both host keys. The host behaviours it relies on were checked on Claude Code
    2.1.321 against the docs and a reproducible throwaway plugin (docs/spikes/spec-track-host.md);
    omitClaudeMd needs 2.1.271 or later and does not stop a subdirectory CLAUDE.md from attaching.
  • Fixed before release (manual trial): a real /mango:spec-review round on a sample spec found
    that three of four reviewers could not locate principles/spec-review.md and one read a copy from
    another checkout. The dispatch now passes the principle's absolute path, and spec-reviewer reads
    only that path and never searches for a copy (agent 353 → 375 words, ledger raised). The round
    itself caught the planted defect — a per-tenant purge over a shared directory — through all four
    lenses.
  • Added (principle, templates): principles/spec-review.md holds the lenses, severities, resolve
    rules, not run and convergence once for all three skills; templates/spec.md, templates/brief.md.
  • Added (counted lines): BRIEF, SPEC, DIVERGENCE, SPEC REVIEW, parsed by check_lines.py
    under the new --phase brief | spec | spec-review. A spec phase holds a document only to its own
    lines, never to a lifecycle line. Ten envelope tests.
  • Changed (design, S4): a ticket or epic with a Spec: <path> line gets one design evidence
    record in Phase 2 — path, sha256, the spec's last SPEC REVIEW: line, provenance: reported —
    shown at Gate 2 with any open Blocker or not run lens. It informs Gate 2 and never closes it. No
    Spec: line, no change. analysis is not touched and spec creates no ticket file: the plan's
    wider S4 was cut so the spec skills stay independent of the lifecycle. design 3090 → 3164 words
    (ledger raised): the record's fields are the behaviour, and no existing text covers them.
  • Changed (doctor): check 11, informational — a host below Claude Code 2.1.271 is a ⚠, since it
    does not support the omitClaudeMd key spec-reviewer relies on.
  • Added (config, optional): specs_dir (default docs/specs/), spec_review.max_rounds (default 3).
  • Decided, not added: no skill sets disable-model-invocation, like every other mango skill; a
    narrow description limits unwanted auto-invocation, and the flag is reconsidered only if measured.
    The spec track's grammars ship before Phase 2's GATE line rather than after it: no GATE change is
    in flight, and the new grammars only add registry entries.
  • Size: the full-run words rise 34,360 → 34,447 (+87): one row in PRINCIPLES.md's companion index,
    which validate.py requires for every companion (ledger raised 2653 → 2666, +13), and the design
    spec link (+74). maturity.md 923 → 979
    for the new Experimental entry. The three skills total 1,756 words; nothing new loads in a full run.
  • Smoke guard: six new fixtures (spec-review-not-run, spec-review-contest-evidence,
    spec-zero-decision, spec-divergence, brainstorm-readiness-gate, design-spec-evidence); their
    30 dispatch-free self-tests pass. Each fixture passed 3× fresh (--no-cache, sequential; CLI 2.1.322, model
    cli-default). That is a smoke guard, not a regression suite. The whole-guard run then failed one
    wording token on multi-clause-want (the outcome was right: two rows, the single-row ✅ rejected, but
    it said "two separate behaviours", not "clauses"); the token is widened to
    clause|behaviou?rs?|halves, over wording only, with a self-test proving both ways. The whole guard
    then passed fresh: 14/14 fixtures, 148/148 assertions, at 3b16bec.