feat(agentic-harness): coordinate generated orchestrator with installed SDD (v0.5.0)#12
Merged
Merged
Conversation
…ed SDD (v0.5.0) When a spec-driven development (SDD) system is present, the generated orchestrator now coordinates with it via a two-way handoff instead of ignoring it: the orchestrator stays the driver, activates the SDD's owned segment with a contextual prompt (auto-invokable CLI/MCP, or prompt-and-pause for human-gated IDE/approval flows), the SDD hands back its artifacts as the contract, and the orchestrator resumes (execute, integrate, cross-boundary QA), writing status back in the SDD's conventions. Two invariants hold: one owner per phase, and one source of truth per artifact (SDD artifacts referenced in place, never copied into _agents_workspace/). - New shared/sdd-coordination.md: the handoff protocol and the per-system coordination map (owned segment, activation, hand-back contract, write-back). - Move detection-signatures.md from spec-advisor/references/ to shared/ so both spec-advisor and harness-setup read one source; update spec-advisor paths. - harness-setup: Step 0 detects an installed SDD and records a coordination context; Step 2 settles delegated vs owned phases with the user; Step 5 splices the SDD-coordination addenda into the orchestrator with concrete paths inlined; checklist updated. - orchestrator-template.md: new "SDD coordination" section (three addenda, Spec Kit and Kiro worked snippets, defer-heavy note) for templates A/B/C. - claude-md-pointer.md: optional "Spec process" line recording the relationship. - Bump plugin.json 0.4.0 -> 0.5.0 and refresh description/README; correct the stale marketplace.json version (0.3.1 -> 0.5.0). Scope is "core only": harness-review SDD-drift checks and a spec-advisor post-install hand-back offer are deferred. Structural suite and `claude plugin validate ./agentic-harness --strict` both pass.
|
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.
Context
The
agentic-harnessplugin generates a project's orchestrator skill. Until now the SDD (spec-driven development) touchpoint was one-directional and setup-only:harness-setuponly offeredspec-advisorwhen a software project had no SDD system. Once a system was installed, the generated orchestrator was blind to it — it could run a parallel agentic flow that conflicts with the spec process.This makes the relationship bidirectional: when an SDD system is present, the orchestrator and the SDD work coordinated, without overlap and with minimal friction.
The coordination model
A two-way handoff, applied uniformly to all 8 supported systems:
Two invariants: one owner per phase (
→ SDD: {system}or orchestrator-owned) and one source of truth per artifact (SDD artifacts referenced in place, never copied into_agents_workspace/).Changes
shared/sdd-coordination.md— the protocol + per-system coordination map (owned segment / activation / auto? / hand-back contract / write-back).detection-signatures.mdfromspec-advisor/references/→shared/so bothspec-advisorandharness-setupread one source (CI-safe: the reference validator ignores${CLAUDE_PLUGIN_ROOT}/shared/...paths). Updated spec-advisor's path references.harness-setup/SKILL.md— Step 0 detects an installed SDD and records a coordination context; Step 2 settles delegated vs owned phases with the user; Step 5 splices the addenda with concrete paths inlined; checklist updated.orchestrator-template.md— new "SDD coordination" section (three addenda, Spec Kit + Kiro worked snippets, defer-heavy note) spliced into templates A/B/C.shared/claude-md-pointer.md— optional "Spec process" line recording the relationship.plugin.json0.4.0 → 0.5.0 + description/README refresh; corrected the stalemarketplace.jsonversion (0.3.1 → 0.5.0; the prior release left it un-bumped and the validator doesn't enforce the match).Scope
Core only (per request). Deferred to a later change:
harness-reviewSDD-drift checks, and aspec-advisorpost-install hand-back offer.Test plan
bash tests/ci/run-structural-tests.sh— passes (pre-existing connector/asset warnings only, none from agentic-harness)claude plugin validate ./agentic-harness --strict— passesreferences/detection-signaturespaths remain after the move🤖 Generated with Claude Code