feat(agentic-harness): tracker-advisor skill, generalized advisor gate, version-sync CI (v0.7.0)#14
Merged
Merged
Conversation
…-coordination The two-way handoff (activate, owned segment, hand-back, write-back), auto-invokable vs human-gated activation, and the two rules (one owner per phase/concern, one source of truth per artifact) were SDD-specific prose in sdd-coordination.md, but the protocol is system-agnostic. Extract it into shared/coordination-protocol.md so each process area (spec process, issue tracking, future areas) adds an instance file with its per-system map instead of duplicating protocol prose. sdd-coordination.md is now the SDD instance: a pointer to the protocol plus the per-system coordination map.
…-layers gate (v0.7.0) New tracker-advisor skill: detects whether a software project lacks an issue tracker suited to agentic work and, if so, advises a best-fit git-managed option (Beads, Backlog.md, git-bug, git-issues, Beans — or GitHub Issues / Linear / Jira as advise-only SaaS) and delegates setup to that system's own installer. Mirrors spec-advisor: offline-first curated shortlist + decision tree, scan-first stay-out, opt-in online in two narrow forms, never authors issues, writes nothing to CLAUDE.md. All shortlist facts verified against official repos; git-issues and Beans flagged early-stage. harness-setup's Step 0 SDD branch becomes a generic process-layers gate — a table of advisor areas (spec process, issue tracking) with one shared gate algorithm — so a future advisor adds a row, not a new conditional. New shared/tracker-coordination.md (per-tracker command map; the tracker owns the work-state concern), tracker addenda in the orchestrator template (phase 0 pulls ready work or creates the issue; integrate writes status back; never copy issue content into the workspace), an Issue tracking line in the CLAUDE.md pointer, and tracker detection signatures (incl. the git-bug refs/bugs check, the bare-backlog/ and ISSUE_TEMPLATE weak-signal rules, and the Taskmaster spec-derived boundary). Both advisors gain a symmetric installer failure contract: report plainly, record no coordination context, leave a clean retry path, and tell the caller to proceed as if no system is present.
The agentic-harness 0.4.0 and 0.6.0 releases bumped plugin.json without marketplace.json (stuck at 0.5.0 until this branch) and nothing caught it. validate-versions.sh compares every plugin.json version against its marketplace.json entry and flags marketplace entries with no plugin directory; registered as the fourth structural suite.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Extends the harness with issue-tracker advisory, modeled on the spec-advisor (SDD) architecture:
tracker-advisorskill — detects whether a software project lacks an issue tracker suited to agentic work and, if so, advises a best-fit git-managed option and delegates setup to that system's own installer. Same posture as spec-advisor: offline-first curated shortlist + decision tree, scan-first stay-out, opt-in online (discovery search + post-selection authoritative fetch), never authors issues, writes nothing to CLAUDE.md.bd, Backlog.md, git-bug, git-issues (early-stage), Beans (early-stage); GitHub Issues / Linear / Jira are advise-only SaaS profiles via their official access paths (gh, vendor MCP servers). Taskmaster stays on spec-advisor's side (spec-derived decomposition) with an explicit boundary rule.shared/coordination-protocol.md;sdd-coordination.mdis slimmed to the SDD instance; newshared/tracker-coordination.mdcarries the per-tracker command map.refs/bugsref check (not a path scan), the bare-backlog/and.github/ISSUE_TEMPLATE/weak-signal rules, and the Taskmaster boundary.tests/validate-versions.sh— asserts every plugin.json version matches its marketplace.json entry (the existing 0.5.0/0.6.0 agentic-harness drift is fixed here; both now 0.7.0).Dual-tracker sync (repo-native ⇄ Jira/Linear via generated sync skill/agent/scheduled task) is designed but deferred to v0.8.0 per scoping decision; design and the session's adversarial-review findings are recorded in
.aidocs/(gitignored).Test plan
bash tests/ci/run-structural-tests.sh— all 4 suites green (incl. new Version Sync, all 7 plugins)claude plugin validate ./agentic-harness --strict— passesshared/*.mdcitations resolve 1:1 (CI ignores shared paths; checked by grep)🤖 Generated with Claude Code