Skip to content

Releases

v2.9.1

Choose a tag to compare

@github-actions github-actions released this 14 Nov 13:20
b18f928

Patch Changes

  • 37b9a31: Glossary entries and ADRs now ship with the code that makes them true, never on the default branch ahead of it. to-tickets makes them an Epic's first Sub-issue, which blocks every other one, so they are the first merge into the integration branch. For a single issue, harden owns the files and carries their text, so they arrive in that issue's pull request.

v2.9.0

Choose a tag to compare

@github-actions github-actions released this 14 Nov 12:09
d5347cc

Minor Changes

  • 27003e7: harden now drops a Test scenario an existing test already covers, merges scenarios that differ only by input, and names the test a new scenario replaces.
  • 27003e7: review now accepts a criterion that harden marked as already covered by an existing test, and for a break not run mark it runs the deliberate break and reports the criterion unproven unless the named test turns red. The review panel's testing reviewer accepts both forms of the mark and leaves the break to review.
  • 27003e7: tdd now declines a test another test already covers, and refuses tests of constants, message wording, framework behaviour and trivial code.
  • 27003e7: Added /test-audit, which reads a test suite, reports the tests another test already covers, and files the removals you pick as issues for triage.
  • 27003e7: The review panel's testing Persona now reports a test the pull request adds that another test already covers, and names the test to keep.
  • 27003e7: Triage now proves an issue filed by /test-audit by breaking the code in a scratch copy and running the Keeper, and closes it as wontfix when the Keeper stays green.

Patch Changes

  • a0b1f1f: In auto-grill, every veto line now opens with a handle (V1, V2 and so on, numbered across the stop, lines that depart from common practice first), so "strike V3" is a complete reply. In the Claude desktop app, each drawing is sent right after its own question, and a button sends the letter answer (1B) on its own line, so two clicks no longer run together.

v2.8.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 03:28
5d34caf

Minor Changes

  • e9ef54f: /chief-of-staff now keeps a Wiki: a folder of dated, linked markdown pages above your repos, with one page per goal and an index. It recommends an existing Wiki and uses it only on your yes, cites what a repo records instead of copying it, and supersedes a changed claim instead of rewriting it.
  • e9ef54f: /chief-of-staff now sends work out instead of doing it: it starts a Build session for an Epic or One-off and a triage session for a filed issue, answers a waiting session as your Proxy when a source settles the question, relays the ones that touch the gate, runs research in background subagents, and asks you to type the user-invoked steps.
  • e9ef54f: Added /chief-of-staff, an experimental session role that acts as your Proxy for the goals you give it: it settles what the record settles, brings you Escalations, Challenges and a veto list, and asks before merging to a protected branch, releasing or closing an Epic.
  • 4ab3f54: A grilling Round can now be answered with letters: every option sits on its own line as A:, B: and so on, the recommended one first, with a Rests on: line naming what the recommendation assumes, and a reply such as 1A 2B or all answers the whole Round, with a caveat after any letter. Each Round after the first reads back the replies that changed the plan, says how many choices are settled and which are held back, and lists the facts it looked up with their sources. The closing restatement marks each line with its source (you, the record, or the agent's inference) and puts the inferred lines last as the ones to check. In auto-grill, the veto list stands in for the list of looked-up facts.

v2.7.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 15:31
81b3240

Minor Changes

  • 67611e4: A session can now triage an issue with the new triaging skill: tell it "use triaging for #N" and it triages N exactly as /triage N does, so an agent such as a Chief of Staff session can send out one triage session per filed issue. The triage steps, references and credits move from triage to triaging, and every message in which triaging waits on you opens with #<N> waits on you:. /triage still shows the waiting issues when you name none, and now asks whether to triage here or in a sub-session where sessions can be started.

v2.6.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 02:56
44891ea

Minor Changes

  • 9bdb63d: /build <N> in the desktop app now asks one question first: run the build here, or in a sub-session. It recommends the sub-session when your session has already started other sessions or sits outside N's checkout. A sub-session starts in the checkout of N's repository (found one folder down when you are above it, or asked when there are none or several) and runs building there, and an answer you give in your own session to its question is passed on to it in your words. In a terminal nothing changes: /build builds here without asking. The choice lives in a new shared skill, delegating.
  • 9bdb63d: A session can now start a build with the new building skill: tell it "use building for #N" and it builds N exactly as /build N does, so an agent such as a Chief of Staff session can start a build without anyone typing /build. The build's steps, references and credits move from build to building; /build still works as before and now hands the issue to building.
  • 9bdb63d: Every worker is now a subagent. The desktop and bg Drivers are gone, and so is --driver: spp dispatch <issue> takes no flags and writes the brief without starting claude --bg, spp plan no longer records or renders a Driver, and spp next no longer puts a driver on its dispatch actions. Passing --driver to either command is a usage error. building no longer asks which Driver to use at the first Wave; its approval question now comes first in its message, so a parent session sees it. An Epic whose plan comment still records a Driver builds as before, with subagent workers.
  • 9bdb63d: A build resumed after its session died now asks about the work its lost workers left behind. spp next <epic> --resume returns each Sub-issue that is claimed, with no open or merged pull request and no assignee, as a hand-back saying worker lost, and building passes --resume on the first spp next of each run, so you choose whether to hand the issue back or start a worker on it again. spp next, spp wait, spp wave plan and the Epic board no longer read the claude agents session list: spp wait no longer prints t-<N> done lines, and the board lists only its own session's subagent workers, so its attach button is gone.

Patch Changes

  • 9bdb63d: spp next and spp wave plan take --running <tickets>: the tickets the build started a worker on, until that worker reports back, count as in flight, so neither command dispatches them again, and a ready ticket that overlaps one is held. Without the flag nothing is held that way. building keeps that list and passes it on every spp next, and starts each worker's Agent description with t-<N>, so the Epic board links the worker to its row. The board's worker entries drop their kind field, and a failing agent list read shows as agent list: <message>.
  • 9bdb63d: spp next and spp wave plan share one parser and one error message for the flag. building passes each running ticket in the form the dispatch action named it, and resumes a worker by the agent id its Agent call returned.
  • 9bdb63d: A resumed build no longer starts a fresh worker on a branch another worker left. When a fix round, a rebase or a settled design needs a worker that died with an earlier session, building asks you whether to hand the issue back or take the pull request over. spp brief's first step again only cuts sdd/<N>-<slug> from the base and confirms it, and a restarted lost worker starts on that fresh branch, so a branch the lost worker pushed is yours to delete or the issue goes back. spp next --running now holds a running ticket in any state, landed included: neither it nor its fix pull requests are routed again while its worker works, and main-gate waits for it. spp wave plan --running holds each one until it lands, with the reason running, its worker has not reported back. building keeps each worker's agent id for the rest of the session and puts an issue back on the running list when it resumes its worker.
  • 9bdb63d: building: each answer to the dead-worker question now leaves a mark spp next reads, so the same fix or merge stops coming back. Taking a pull request over puts its issue on the running list until you say you are done; handing back a fix pull request closes it with its open findings, so the main gate can run. spp brief's first step now stops BLOCKED when origin already has the ticket's branch or cannot be reached, and the brief tells the worker never to force-push.
  • 9bdb63d: Every question building stops on now opens with one line, #<N> waits on you: <question>: the first Wave's approval, a lost worker, a red Verify after a merge, a design to settle and an issue it cannot build. delegating relays your answer from a parent session to any of them, not only the Wave approval. /build on a Sub-issue or a raw issue now stops with the reason before it asks where to run, and starts no sub-session. Restarting a lost worker removes its local worktree and branch once you agree.

v2.5.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 21:43
d7ea9fc

Minor Changes

  • c415a22: spp lint pr <pr> checks a pull request body for the review gate's sections: the Closes or Refs line, ## Ticket and ## Laws, a Verify line on the head commit, Verify block corrected: and Interfaces changed:. The implement-issue worker runs it at step 8 and fixes the body before it reports, so a missing section no longer costs a fix round.

Patch Changes

  • c2cb705: spp status, spp next, spp retro, the epic board and spp merge now count a closing reference only when a line of the pull request body opens with a closing keyword (spaces or tabs may come before it), such as Closes #2 or Fixes: acme/app#2. A sentence that says "this also fixes #1's edge case" no longer links the pull request to #1, and a reference followed by an apostrophe is never a closing reference, even at the start of a line. Before this, a Fix pull request that mentioned another ticket in prose could be listed as that ticket's pull request with its verdict, and spp merge could refuse it with gate not passed for the wrong ticket.

  • 54a8c7d: spp findings merge counts one defect once when review-panel Personas title it differently: findings on one file within five lines merge whatever their titles, the body lists each other title as an Also reported as: line, and a ticket-mandated:, Candidate ADR:, Check after deploy: or Terminology title merges only with its own tag. With --fix-diff, a merged finding counts as on a changed line when any finding it absorbed was.

  • ae19d85: spp retro no longer undercounts review rounds. spp wave <epic> panel takes a new --pr <pull request URL> and keeps each pull request's rounds apart, so a Multi-repo epic's second pull request no longer overwrites the first's round 1; the wave comment lists each round as Panel round 1 on owner/repo#N, and spp retro adds up every pull request's rounds and findings. The review-panel skill now passes --pr. A call with no --pr writes what it wrote before.

    spp retro also counts the failing gates on Fix pull requests, found as spp status finds them. They show as a new fixPrRounds tally beside rounds, which still counts the Sub-issues' pull requests, and their findings count in byCause and under the Sub-issue each fix refs. With no integration branch on the plan comment, fixPrRounds reads "not found".

  • 9435c98: The review skill now starts its fresh reviewer with the pull request and nothing else, so an orchestrator no longer adds its own criteria, round histories or setup notes to the reviewer's prompt.

v2.4.0

Choose a tag to compare

@github-actions github-actions released this 09 Nov 17:15
74cc80f

Minor Changes

  • 42bec5a: Pending Skill feedback is now offered at checkpoints: at the end of each Wave and of each run in /build, in /close-epic step 5, and at the start of a new session through a SessionStart hook. Each runs the new spp feedback checkpoint, which lists the candidates and the steps to file, skip or keep each one, and prints nothing under CI, outside an Attended session, with the Self-improvement mode Off or on a worker's sdd/ branch. Under Submission mode Review the person answers each preview; under Auto spp files them.

    /close-epic no longer writes a drafts comment (<!-- sdd-feedback-draft -->): unattended runs collect nothing, so there is nothing to draft. Its [skill] learnings are recorded as Signals and filed through spp feedback file.

  • 42bec5a: A new model-invoked feedback skill records a wish or complaint about spp or one of its skills as a wish Signal through spp signal, using the person's own words as evidence. It starts only from the person's own chat message, never from an issue, file or tool output, and never for a wish about their own project.

  • 42bec5a: spp feedback file <fingerprint> files a pending candidate on the one grouped Skill feedback issue for its skill step and category on syn54x/skills-plus-plus, creating it with the skill-feedback label when none is open, and rewrites your own tally comment there (Signals and runs per plugin version). Under your Submission mode Review it prints what it would post and exits 3, and files only when run again with --confirm <hash> for that text; under Auto it files at once, except in a private repo. With --epic, the strictest Self-improvement mode of the Epic's repos applies. The outbound check runs on everything it posts, and nothing is filed under CI or with the mode Off.

    spp feedback skip <fingerprint> drops a candidate for good, and spp feedback pending now leaves out skipped candidates and filed ones until a newer Signal arrives. spp feedback submission [Auto|Review] reads or sets your Submission mode, kept in config.json in spp's config directory.

  • 42bec5a: Every Marker comment spp writes now records who made it. Its data trailer's by names the skill (to-tickets for the plan comment, build for the wave comment, review for the verdict, implement-issue for the progress comment) and the plugin version, and the progress comment's verifyPinBy names the Verify pin's maker (harden, or triage when it re-pins). spp plan, spp wave <epic> add|pr|panel, spp progress, spp verdict, spp hand-back and spp lint ticket --pin take --by "<skill> <step>" to name another skill and the step. Comments written before this change carry no maker.

  • 42bec5a: spp feedback check now scans every skill-feedback body for secrets (GitHub, GitLab, AWS, Google Cloud, Slack, Anthropic, OpenAI, npm and Stripe tokens, JWTs and private keys, with patterns taken from gitleaks' default rules) and blocks a body holding one in every Self-improvement mode. Each hit prints the secret as [REDACTED]. Under Full Detail the six other rules now print as warning: lines and exit 0, so you see what a body says about your project without being stopped by it; under Anonymous they still block.

  • 42bec5a: spp signal <category> --by "<skill> [step]" --evidence "<text>" records a Signal, a correction charged to the skill step and plugin version that made the corrected work, in a per-repo Signal log beside the notes log. It records only in an Attended session, never under CI, and never when the repo's Self-improvement mode is Off. spp feedback pending lists the recorded Signals grouped by skill step and category.

    The Routing block's Self-improvement mode: line (Off, Anonymous or Full Detail) replaces Upstream feedback:. An old line still works: off reads as Off, counts and detailed as Anonymous, and attributed as Full Detail. spp preflight --json now prints selfImprovement in place of upstreamFeedback.

  • 42bec5a: A new spp gate <pr> command reads a pull request's slice gate the way spp merge does: the verdict comment from a trusted author, judged against the pull request's current head. It prints gate-pass, gate-fail or pr-open with the head and each result, and --json adds the verdict and the maker that wrote it. A skill that asks whether the gate passed a pull request now runs one command instead of decoding the verdict trailer.

Patch Changes

  • 42bec5a: The attended decision spp dispatch passes to a worker now lives in one file per ticket, so dispatches started together no longer overwrite each other's. A worker sees it from its first command (an sdd/<N>- or sdd-<N> branch, or a claude --bg --worktree sdd-<N> folder before it cuts its branch) and honours it only while the ticket's issue is open. Only the issue closing ends it, since the same worker is resumed after its slice merges and after a needs-info hand-back: a worker that finds the issue closed deletes it. spp note --auto, the Stop hook and the epic board now recognise every worker shape too. Claude Code's attended variable is now named in hooks/attended.json, which the npm package also ships, rather than in spp's source.

  • cddc6ca: auto-grill draws each choice so it reads on a narrow screen. Every Escalation and Challenge now opens with the question in one plain sentence, then stacks its options under A: and B: labels within 72 columns, with the Best fit marked and only names you already know. Before this, options sat side by side in columns over 100 characters wide, which wrapped in the desktop app and buried the deciding difference. In the Claude desktop app, where an inline visual tool is available, each choice is drawn as rendered cards, grids or timelines, with a button per option that sends your answer.

  • 42bec5a: Four commands now record the corrections they already see as Signals, charged to the skill step that made the corrected artifact: a failed spp verdict (fix-round), each spp hand-back route (brief-gap, missed-edge, human-needed), each spp plan --add-deviation (contract-edited), and the ready gate's pin-match in spp lint ticket when a trusted person edited the body (contract-edited). spp feedback pending lists them. The same Signal is never recorded twice, and nothing is recorded under CI, outside an Attended session or with the Self-improvement mode Off. Exit codes, stdout and GitHub writes do not change.

    Every Marker comment write that creates the comment or hands it to another skill step now counts one run in a runs log beside the Signal log, the denominator for signals per run.

    spp signal under CI in a checkout with no GitHub origin now prints not recorded: CI and exits 0 instead of failing, and a Signal that cannot be written is reported rather than thrown, so spp findings merge keeps its exit code.

  • 42bec5a: A Signal about another repo's issue now keeps that repo's name (a new optional about field, also on spp feedback pending --json), and spp feedback file treats those repos as it treats an Epic's: Submission mode Auto falls back to Review when one is private, and the outbound check guards their names. A run is recorded once: spp findings merge --fix-diff names its run by the patch's content (fix diff <hash>, after pull request <N> when the patch sits in the panel's spp-panel-<N> folder), so merging the same round again adds none, and a fresh panel run whose round numbers start again at 1 still counts its rounds. When a skill step has no recorded runs, the grouped issue's title and body and the tally comment say its runs are not recorded instead of reporting 0 (the tally's trailer stores runs: null), and the feedback skill charges a wish to the skill alone, so it is counted over that skill's runs. spp feedback checkpoint checks for a worker before anything else, so a worker's session start asks gh nothing. The spp config file, which holds the tally secret, is left at mode 0600 on every write.

  • 42bec5a: spp feedback file now adds your tally only to a grouped issue that you or an owner, member or collaborator of syn54x/skills-plus-plus opened, so a stranger's issue carrying the fingerprint can no longer collect it; the Review preview names the issue's author. You keep one tally comment per repo you file from, keyed by a hash of the repo under a secret kept in your spp config, so the key names no repo and filing from a second repo no longer overwrites the first one's counts. spp feedback file now refuses outside an Attended session and in a worker, and the checkpoint recognises a worker the same way spp does everywhere else.

  • 42bec5a: spp findings merge takes a new --fix-diff <file> flag. From round 2 the review panel passes it the patch of the fixes made since the previous round. A merged finding that sits on a line the patch added or changed, and that no recheck- finding was merged into, is recorded as a fix-regression Signal against the fix round step of implement-issue, and stderr says whether each one was recorded. Without the flag, and in stdout and --json with it, the merge behaves as before.

  • 42bec5a: spp findings merge --fix-diff now records one run of implement-issue step fix round for every merge, whether or not a finding regressed. Before this, nothing recorded fix rounds as runs, so the grouped fix-regression issue reported "over 0 recorded runs" and the per-version rate could not be read.

  • e2e0b67: A worker resumed for a fix round now plans every finding before its first edit, following implement-issue's new FIX-ROUND.md. For each finding it writes down the root cause, every caller and test the change reaches, any overlap with another finding's fix, and the test that guards against a regression. Then it adds a ## Fix plan section to the pull request. Before this, a worker fixed each finding at the line the finding named, and the fix often br...

Read more

v2.3.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 03:25
59864ca

Minor Changes

  • 2d5b628: The epic board now lists an Epic's fix pull requests in a Fixes group after the Waves: one row per open or merged fix with a fix open or fix merged chip, its number, the Sub-issue its Refs line names (or unattributed) and a PR button that copies its link. While the Epic has any fix, the board header and the status line end with the open count, as in 12/12 merged · 3 fixes open. A failing pull request read keeps the ticket rows and shows its error. A board stored by an earlier version is dropped and redrawn on the next refresh.
  • 2d5b628: spp merge now merges a Fix pull request: one that closes no Sub-issue of its Epic but Refs a Sub-issue, with a trusted passing verdict on its head, the Epic's integration branch as base and passing checks. It writes nothing to the wave comment, and a pull request that closes no issue and refs no Sub-issue is refused.
  • 2d5b628: spp next now routes an Epic's Fix pull requests the way it routes a slice: gate when its checks pass and its head has no verdict, fix once after a failed head (naming the failing runs when checks are the cause), hand-back naming the pull request after a second failed head, merge on a passing verdict, and wait while its checks are pending or its Sub-issue's worker is running. An unattributed fix is never gated or merged: it is reported under wait, or stuck when nothing else is in flight, with the way out (add Refs #<Sub-issue> to its body, or close it). main-gate now prints only once no fix is open. The action shape is unchanged.
  • 2d5b628: The review skill now gates a Fix pull request: one with no closing line that opens Refs #N for a Sub-issue and targets its Epic's integration branch gets both verdicts, the Sub-issue's Verify block, and a verdict marker recorded with spp verdict --ticket N. build's Main gate follows spp next for fixes (gate, fix, merge or hand-back) and spp merge merges them, so the orchestrator no longer merges a fix by hand.
  • 2d5b628: spp status now lists an Epic's Fix pull requests: trusted pull requests into its integration branch that close no Sub-issue, open or merged (ADR 0011). The text view prints them under a Fixes heading after the Layers, one line each with its state, its number and the Sub-issue its Refs line names or unattributed, and the header line ends with the open count, as in (3 fixes open); with no fixes it prints neither. --json carries the same list as fixes on the Epic state, each with ticket set to the Sub-issue's URL or null. spp wait exits with a change line when a fix appears, merges or goes (#77 OPEN -> MERGED), gets a new head after a fix round or gets the gate's verdict (#77 OPEN -> OPEN (new head)). The snapshot makes one more GraphQL request per repo of the Epic (its own, each Sub-issue's and each the plan names) for the list, only when the plan comment records an integration branch; a repo that is not there or not readable is warned about on stderr once and loses only its fixes, while any other failure fails the command. snapshot.ts exports pullRequestsArgs(snapshot), fixRepos, withPullRequests and readPullRequests for the epic board.
  • 3c14c8d: /to-tickets now checks the set for values worked out twice. When one Sub-issue works a value out from another module's output (a client inferring each row's state from a summary the server returns), it asks whether the module that holds the inputs should produce the value itself. If so, the producer gains a Produces line or a Sub-issue of its own before anything is released, and the consumer reads the value. A derivation you meant to keep is yours to accept.

Patch Changes

  • 8856ea4: spp dispatch <issue> --driver subagent now refuses a folder that is not inside a git repository, before it reads GitHub. The spp:worker agent cuts its worktree from the session's folder, so every worker started from such a folder failed with Cannot create agent worktree: not in a git repository. The refusal says to run /build from inside the checkout of the repository that owns the issue, or to choose another Driver. The bg and desktop Drivers are unchanged.
  • 2d5b628: A Fix pull request in EpicState.fixes now carries its gate on the current head, computed once, and spp next reads it. The way out for an unattributed fix names Refs #<Sub-issue> only, since Closes on a closed Sub-issue makes the pull request that ticket's own.
  • f197712: The stop hook, spp verify --check, now ends its refusal on a Stop event with one more sentence: if this is a worker's worktree and you are not that worker, cd back to your own checkout and stop again. The hook judges the tree the session stands in and cannot tell whose work is there. An orchestrator whose shell was left inside a worker's worktree was therefore refused at the end of every turn until the worker committed, and one run polled through 18 fix rounds that way. build on Claude Code now tells the orchestrator to read a worker's worktree with git -C <path> and to stay out of it. A SubagentStop refusal and a run by hand print what they printed before, and which stops are refused has not changed.

v2.2.0

Choose a tag to compare

@github-actions github-actions released this 06 Nov 13:32
856d570

Minor Changes

  • 5a6a9ac: New skill discuss: type /discuss <idea>, or say you want to brainstorm or kick an idea around, and the agent talks a vague idea over with you before it is a plan, then names where it should go next. It is experimental, so it may change or be removed.
  • 1ca3abf: /epic-board with no argument now picks the Epic itself: the parent of an sdd/<N>-* branch, the Epic whose plan records a feat/<slug> branch, or the one Epic in flight in the repo. With several in flight it lists them; with none it says so.

v2.1.0

Choose a tag to compare

@github-actions github-actions released this 04 Nov 16:58
ab8302b

Minor Changes

  • b402fe2: In the Claude desktop app, /build now asks which Driver to use when you approve an Epic's first Wave, since desktop linked sessions start each later Wave only on a message from you. spp plan <epic> --driver desktop|bg|subagent records the choice and spp next reports it on dispatch, so a resumed run reuses it.

Patch Changes

  • 5cc096f: Credit each skill's sources: a skill that drew on an incumbent now lists them under metadata.credits in its frontmatter, with a CREDITS.md beside it saying which part came from where.