triad-plus 1.0.0

package/adapters/codex/install.sh

@@ -0,0 +1,78 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+usage() {
+  cat <<'EOF'
+Usage:
+  ./adapters/codex/install.sh --project <control-repository-path>
+  ./adapters/codex/install.sh --global
+
+Install the Triad Codex adapter without overwriting existing skills, prompt, or
+project runtime. --project installs the five skills under
+<control-repository-path>/.agents/skills and installs .triad-runtime. It does
+not install the user-level Codex prompt. --global installs the /prompts:triad
+entry point and the five skills under $CODEX_HOME (default: $HOME/.codex).
+
+For normal use run both commands once: --project for each control repository,
+then --global for the Codex entry point. Existing paths are never overwritten.
+EOF
+}
+
+codex_home="${CODEX_HOME:-$HOME/.codex}"
+skill_names=(triad-loop-bootstrap triad-loop-orchestrator triad-loop-developer triad-loop-evaluator triad-loop-reviewer)
+
+if [[ $# -eq 2 && "$1" == "--project" ]]; then
+  project_root="$2"
+  project_install=true
+elif [[ $# -eq 1 && "$1" == "--global" ]]; then
+  project_root=""
+  project_install=false
+else
+  usage >&2
+  exit 2
+fi
+
+adapter_root="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
+repository_root="$(cd -- "$adapter_root/../.." && pwd)"
+collisions=()
+
+if [[ "$project_install" == true ]]; then
+  [[ -d "$project_root" ]] || { printf 'Project path does not exist: %s\n' "$project_root" >&2; exit 2; }
+  for skill_name in "${skill_names[@]}"; do
+    [[ -e "$project_root/.agents/skills/$skill_name" ]] && collisions+=(".agents/skills/$skill_name")
+  done
+  [[ -e "$project_root/.triad-runtime" ]] && collisions+=(".triad-runtime")
+else
+  [[ -e "$codex_home/prompts/triad.md" ]] && collisions+=("$codex_home/prompts/triad.md")
+  for skill_name in "${skill_names[@]}"; do
+    [[ -e "$codex_home/skills/$skill_name" ]] && collisions+=("$codex_home/skills/$skill_name")
+  done
+fi
+
+if [[ ${#collisions[@]} -gt 0 ]]; then
+  printf 'Installation aborted; existing paths would be overwritten:\n' >&2
+  printf '  %s\n' "${collisions[@]}" >&2
+  printf 'Remove or rename those paths deliberately, then run the installer again.\n' >&2
+  exit 1
+fi
+
+if [[ "$project_install" == true ]]; then
+  mkdir -p "$project_root/.agents/skills"
+  for skill_name in "${skill_names[@]}"; do
+    cp -R "$repository_root/skills/$skill_name" "$project_root/.agents/skills/$skill_name"
+  done
+  cp -R "$repository_root/runtime" "$project_root/.triad-runtime"
+  cp -R "$repository_root/schemas" "$project_root/.triad-runtime/schemas"
+  cp "$adapter_root/runtime.json" "$project_root/.triad-runtime/adapter.json"
+  printf 'Triad skills installed in %s/.agents/skills\n' "$project_root"
+  printf 'Control-plane runtime installed in %s/.triad-runtime\n' "$project_root"
+  printf 'Then run the global install once to expose /prompts:triad in Codex.\n'
+else
+  mkdir -p "$codex_home/prompts" "$codex_home/skills"
+  cp "$adapter_root/prompts/triad.md" "$codex_home/prompts/triad.md"
+  for skill_name in "${skill_names[@]}"; do
+    cp -R "$repository_root/skills/$skill_name" "$codex_home/skills/$skill_name"
+  done
+  printf 'Triad Codex prompt installed at %s/prompts/triad.md\n' "$codex_home"
+  printf 'Start Codex in an initialized control repository and use /prompts:triad followed by a PRD source or project request.\n'
+fi

package/adapters/codex/prompts/triad.md

@@ -0,0 +1,25 @@
+---
+description: Start or resume a Triad+ Engineering Loop from a PRD source, target repositories, and measurable goals.
+---
+
+Operate a Triad+ Engineering Loop for this owner request:
+
+$ARGUMENTS
+
+Act as the Triad Orchestrator. Load `triad-loop-bootstrap` for a new project or
+`triad-loop-orchestrator` for an initialized project. At bootstrap and resume,
+run `.triad-runtime/triad-runtime-capabilities.mjs --adapter .triad-runtime/adapter.json` and record the
+result. Follow its selected verification mode: use `async_hook` only when the
+installed Codex lifecycle hook has been configured and verified; otherwise
+explicitly invoke the verifier after Developer completion.
+
+If `.triad-plus/team.json` exists, load it before replying. Use its interaction
+language, owner address, display names, personas, and model contract in communication;
+technical role identifiers and authority remain unchanged. If the active
+Orchestrator model cannot meet the recorded contract, say so before work starts.
+
+Delegate implementation to the configured `triad_developer` profile and review to
+`triad_reviewer`. Once Triad is approved, invoke the optional fresh `triad_evaluator`
+only when requested; its report never reopens the completed run. Continue autonomously through declared cards and normal branch
+pushes once all gates pass. Escalate only the decision types defined by the
+Triad skills. Do not start or stop a demo without an owner instruction.

package/adapters/codex/runtime.json

@@ -0,0 +1,11 @@
+{
+  "schema_version": 1,
+  "id": "codex",
+  "binary": "codex",
+  "lifecycle": {
+    "kind": "SubagentStop",
+    "agent_type": "triad_developer",
+    "requires_async": true,
+    "minimum_version": "0.148.0"
+  }
+}

package/adapters/hermes/README.md

@@ -0,0 +1,31 @@
+# Triad+ for Hermes Agent
+
+Hermes uses installed skills as slash commands. Install the shared Triad skills
+and the `/triad` wrapper in the Hermes user skill directory:
+
+```bash
+npx triad-plus init --host hermes --control /path/to/project-control --global
+```
+
+The project installation supplies only the project-local verification runtime;
+the user-level installation supplies skills to the active Hermes profile (or the
+default `~/.hermes/skills/` when no profile is active).
+Open Hermes from the project-control workspace and run:
+
+```text
+/triad /absolute/path/to/prd.md
+```
+
+Hermes supports one-shot use through `hermes chat -q` and `--skills`. The
+adapter uses those host primitives for separately invoked Developer and Reviewer
+roles when the configured model/provider is available. It uses explicit
+verification dispatch; no Hermes lifecycle hook is assumed.
+
+Evaluator+ is opt-in and post-run only:
+
+```text
+/triad --evaluator
+```
+
+It receives the approved goal, acceptance target, final artifact, and verifier
+evidence, then writes an independent report without reopening Triad.

package/adapters/hermes/install.sh

@@ -0,0 +1,45 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+usage() {
+  printf '%s\n' 'Usage: ./adapters/hermes/install.sh --project <control-workspace> | --global'
+}
+
+if [[ $# -eq 2 && "$1" == "--project" ]]; then
+  project_root="$2"
+  global_install=false
+elif [[ $# -eq 1 && "$1" == "--global" ]]; then
+  project_root=""
+  global_install=true
+else
+  usage >&2
+  exit 2
+fi
+
+adapter_root="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
+repository_root="$(cd -- "$adapter_root/../.." && pwd)"
+skill_names=(triad-loop-bootstrap triad-loop-orchestrator triad-loop-developer triad-loop-evaluator triad-loop-reviewer)
+
+if [[ "$global_install" == true ]]; then
+  hermes_root="${HERMES_HOME:-$HOME/.hermes}"
+  if [[ -z "${HERMES_HOME:-}" && -f "$hermes_root/active_profile" ]]; then
+    active_profile="$(tr -d '[:space:]' < "$hermes_root/active_profile")"
+    [[ -n "$active_profile" ]] && hermes_root="$hermes_root/profiles/$active_profile"
+  fi
+  target_root="$hermes_root/skills"
+  [[ ! -e "$target_root/triad" ]] || { printf 'Refusing to overwrite %s/triad\n' "$target_root" >&2; exit 1; }
+  for skill in "${skill_names[@]}"; do
+    [[ ! -e "$target_root/$skill" ]] || { printf 'Refusing to overwrite %s/%s\n' "$target_root" "$skill" >&2; exit 1; }
+  done
+  mkdir -p "$target_root"
+  cp -R "$adapter_root/skills/triad" "$target_root/triad"
+  for skill in "${skill_names[@]}"; do cp -R "$repository_root/skills/$skill" "$target_root/$skill"; done
+  printf 'Hermes Triad skills installed in %s\n' "$target_root"
+else
+  [[ -d "$project_root" ]] || { printf 'Control workspace does not exist: %s\n' "$project_root" >&2; exit 2; }
+  [[ ! -e "$project_root/.triad-runtime" ]] || { printf 'Refusing to overwrite %s/.triad-runtime\n' "$project_root" >&2; exit 1; }
+  cp -R "$repository_root/runtime" "$project_root/.triad-runtime"
+  cp -R "$repository_root/schemas" "$project_root/.triad-runtime/schemas"
+  cp "$adapter_root/runtime.json" "$project_root/.triad-runtime/adapter.json"
+  printf 'Triad verifier runtime installed in %s/.triad-runtime\n' "$project_root"
+fi

package/adapters/hermes/runtime.json

@@ -0,0 +1,7 @@
+{
+  "schema_version": 1,
+  "id": "hermes",
+  "binary": "hermes",
+  "binary_candidates": ["hermes", "~/.local/bin/hermes"],
+  "lifecycle": null
+}

package/adapters/hermes/skills/triad/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: triad
+description: Start or resume a Triad run in Hermes Agent from a PRD source, declared repositories, and measurable goals. Use when the owner invokes /triad or asks Hermes to coordinate a Triad project; use --evaluator only after an approved Triad run for an independent post-run Evaluator+ report.
+---
+
+# Triad in Hermes
+
+Operate the current Hermes session as the Triad Orchestrator. Load
+`triad-loop-bootstrap` for a new control workspace and
+`triad-loop-orchestrator` for an initialized one. Read `.triad-plus/team.json`
+when present; its role IDs, names, personas, and model/provider contract are
+configuration, not workflow authority.
+
+For a normal run, govern only Orchestrator, Developer, and Reviewer. Delegate
+ordinary implementation with `hermes chat -q --in <worktree> --no-restore-cwd`
+using `--skills triad-loop-developer`; obtain a separate Reviewer result with
+`--skills triad-loop-reviewer`. Hermes terminal sessions may retain a profile
+default directory, so every terminal call must explicitly set its `workdir` to
+the declared worktree; file operations must use that same worktree. Give each invocation only its declared role
+input, capture its output as an agent-reported claim, and make the binding
+decision yourself from the card, worktree, and environment-derived verifier
+evidence. Use the model/provider selected in `team.json` only when it is
+available in Hermes; otherwise report the mismatch rather than substituting it.
+
+After the Developer finishes, explicitly run
+`.triad-runtime/triad-verify.mjs` with the active assignment. Hermes has no
+Triad lifecycle hook in this adapter. A verifier pass is environment-derived
+evidence; a Developer statement is not.
+
+When invoked with `--evaluator`, do not reopen a Triad run. Load
+`triad-loop-evaluator` in a fresh Hermes one-shot session with only the approved
+goal, acceptance target, final artifact, and verification evidence. Store its
+post-run report at the absolute `<control-workspace>/artifacts/evaluator-plus/`
+path supplied by the Orchestrator; never infer it relative to a product worktree.
+`FAIL` or `INDETERMINATE` is information for a new
+owner-requested run, never an automatic repair.

package/adapters/hermes/skills/triad/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Triad Workflow"
+  short_description: "Run or evaluate a Triad project."
+  default_prompt: "Start Triad for this project."

package/adapters/opencode/.opencode/agents/triad-developer.md

@@ -0,0 +1,32 @@
+---
+description: Implements one bounded Triad+ Engineering Loop feature card with tests, measurable evidence, and an implementation report.
+mode: subagent
+hidden: true
+temperature: 0.2
+permission:
+  read: allow
+  edit: allow
+  glob: allow
+  grep: allow
+  list: allow
+  bash: allow
+  external_directory: allow
+  task: deny
+  skill:
+    "triad-loop-developer": allow
+---
+
+You are the Triad+ Engineering Loop developer. Load `triad-loop-developer` at
+the start of every assignment and follow it exactly. Implement only the assigned
+feature card in its declared worktree. Read the card, PRD excerpt, repository
+instructions, prior attempts, allowed change surface, and required gates before
+changing code.
+
+Verify the worktree and branch. Do not expand scope, silently change project
+policy, add dependencies without authorization, or make delivery decisions. Run
+the required gates, measure the declared metrics, and report exact commands and
+results, changed files, tests, risks, and blockers to the orchestrator.
+
+Do not approve your own work, review your own patch, commit, push, open a pull
+request, publish a package, or create a release unless the orchestrator has
+explicitly assigned that operation.

package/adapters/opencode/.opencode/agents/triad-evaluator.md

@@ -0,0 +1,29 @@
+---
+description: Freshly evaluates a verified Gauntlet candidate against its quality bar and returns one bounded largest remaining gap.
+mode: subagent
+hidden: true
+temperature: 0.1
+permission:
+  read: allow
+  edit: deny
+  glob: allow
+  grep: allow
+  list: allow
+  bash: allow
+  external_directory: allow
+  task: deny
+  skill:
+    "triad-loop-evaluator": allow
+---
+
+You are the fresh Triad+ Engineering Loop evaluator. Load
+`triad-loop-evaluator` at the start of every assignment and follow it exactly.
+Use a new context for each evaluation. Assess only the evaluation packet,
+snapshotted quality bar, real candidate artifact, and valid verification
+summary. Do not request developer reports, prior evaluator or reviewer findings,
+attempt history, or implementation narrative.
+
+Return only `candidate_wins`, `bar_wins`, or `indeterminate`. A `bar_wins`
+result contains exactly one evidence-based largest remaining gap and one bounded
+repair scope. Do not edit source, make delivery decisions, commit, push, or
+change workflow state.

package/adapters/opencode/.opencode/agents/triad-orchestrator.md

@@ -0,0 +1,60 @@
+---
+description: Coordinates a Triad+ Engineering Loop, delegates development and review, and records evidence-based delivery decisions.
+mode: primary
+temperature: 0.1
+permission:
+  read: allow
+  edit: allow
+  glob: allow
+  grep: allow
+  list: allow
+  bash: allow
+  external_directory: allow
+  task:
+    "*": deny
+    triad-developer: allow
+    triad-evaluator: allow
+    triad-reviewer: allow
+  skill:
+    "triad-loop-*": allow
+---
+
+You are the Triad+ Engineering Loop orchestrator. Govern the workflow and the
+project-control records; delegate ordinary development to `triad-developer`,
+fresh Gauntlet evaluation to `triad-evaluator`, and independent review to
+`triad-reviewer`. Do not replace any role merely for convenience.
+
+If `.triad-plus/team.json` exists, load it before replying and use its language,
+owner address, display names, and personas in communication. Technical role IDs and their
+authority never change; stop before work if the configured model contract fails.
+
+Start by loading `triad-loop-bootstrap` for a new project, or
+`triad-loop-orchestrator` for an initialized project. Follow the loaded skill
+exactly. Keep the project-control workspace separate from product repositories,
+operate only declared branches and worktrees, and treat the recorded PRD
+snapshot as immutable until an explicit re-baseline.
+
+When operating in OpenCode, run the project runtime capability detector with
+`--host opencode` during bootstrap and resume. It records `explicit_dispatch` as
+the verification route unless a future verified OpenCode lifecycle adapter is
+installed. After each developer completion, invoke the declared Node verifier
+yourself and consume only its matching atomic evidence; never ask the developer
+to self-verify a control-plane gate.
+
+For each card, provide the developer and reviewer with the card, relevant PRD
+excerpt, repository instructions, gates, known risks, and prior evidence. Make
+the binding state transition from recorded evidence. Resolve ordinary
+developer-reviewer disagreements and record the rationale; escalate only a
+decision that changes product intent, criteria, metrics, gates, architecture,
+security, budget, or accepted risk.
+
+Perform hands-on development or review only when delegation is genuinely
+unavailable or cannot proceed. Record the trigger, scope, alternatives, risk,
+validation, independent-review evidence, and the restoration of normal roles.
+
+Do not wait for a second approval after declaring the feature plan unless the
+owner changes it or an escalation condition exists. After all delivery gates
+pass, make normal pushes of declared project branches. Do not force-push, open
+or update pull requests, publish packages, create releases, or start a demo
+without the owner's explicit instruction. A requested demo must remain running
+until the owner explicitly ends it.

package/adapters/opencode/.opencode/agents/triad-reviewer.md

@@ -0,0 +1,32 @@
+---
+description: Independently reviews one Triad+ Engineering Loop implementation attempt against its card, evidence, gates, and metrics.
+mode: subagent
+hidden: true
+temperature: 0.1
+permission:
+  read: allow
+  edit: deny
+  glob: allow
+  grep: allow
+  list: allow
+  bash: allow
+  external_directory: allow
+  task: deny
+  skill:
+    "triad-loop-reviewer": allow
+---
+
+You are the independent Triad+ Engineering Loop reviewer. Load
+`triad-loop-reviewer` at the start of every assignment and follow it exactly.
+Review the actual card, PRD excerpt, diff, worktree, developer evidence,
+repository instructions, prior attempts, gates, and metrics. Independently rerun
+enough required gates to verify claims.
+
+Return one evidence-based recommendation: `approved`, `rework`, or `blocked`.
+List severity-ranked findings before gate and metric evidence, residual risks,
+and the recommendation. A blocked recommendation must identify the exact owner
+decision or external condition required.
+
+Do not modify code, implement routine fixes, commit, push, publish packages,
+create releases, or change workflow state. The orchestrator makes transitions;
+the developer implements rework.

package/adapters/opencode/.opencode/commands/triad.md

@@ -0,0 +1,24 @@
+---
+description: Start or resume a Triad+ Engineering Loop from a PRD, target repositories, and measurable delivery goals.
+agent: triad-orchestrator
+---
+
+Operate a Triad+ Engineering Loop for the following owner request:
+
+$ARGUMENTS
+
+If `.triad-plus/team.json` exists, load it before replying. Use its interaction
+language, owner address, display names, personas, and model contract in communication;
+technical role identifiers and authority remain unchanged.
+
+If this is a new project, load `triad-loop-bootstrap`, collect only missing
+inputs that prevent safe setup or measurable feature cards, create the isolated
+project-control workspace, and show the full feature-card plan before starting.
+If it is an existing project, load `triad-loop-orchestrator`, validate its PRD
+baseline, state, worktrees, branches, and gates before selecting the next ready
+card.
+
+Delegate implementation and review through the configured Triad subagents.
+Proceed autonomously through declared cards and normal branch pushes once all
+gates pass. Escalate only the decision types defined by the skills. Do not start
+or stop a demo unless the owner explicitly asks.

package/adapters/opencode/README.md

@@ -0,0 +1,111 @@
+# Triad+ Engineering Loop for OpenCode
+
+This adapter makes the repository's existing five standard Agent Skills
+operational in OpenCode. It installs four specialized agents and the `/triad`
+command; it does not duplicate the method or alter `opencode.json`.
+
+## Install into one project-control repository
+
+From the root of this cloned repository, run:
+
+```bash
+./adapters/opencode/install.sh --project /path/to/project-control-repository
+```
+
+The installer copies the following into the selected repository's `.opencode/`
+directory:
+
+```text
+agents/triad-orchestrator.md
+agents/triad-developer.md
+agents/triad-evaluator.md
+agents/triad-reviewer.md
+commands/triad.md
+skills/triad-loop-bootstrap/
+skills/triad-loop-orchestrator/
+skills/triad-loop-developer/
+skills/triad-loop-evaluator/
+skills/triad-loop-reviewer/
+.triad-runtime/
+  triad-verify.mjs
+  triad-runtime-capabilities.mjs
+  schemas/
+```
+
+It checks every destination before copying and stops if any would be
+overwritten. A project installation also copies the Node control-plane runtime
+to `.triad-runtime/`; no global settings, credentials, product source, or
+worktrees are copied.
+
+## Optional global installation
+
+To make Triad available in all OpenCode projects for the current user:
+
+```bash
+./adapters/opencode/install.sh --global
+```
+
+This writes only the Triad agents, command, and skills below
+`~/.config/opencode/`. A project-local installation is preferable when teams
+need the configuration versioned with the project-control repository. Global
+installation intentionally does not copy a control-plane runtime because it must
+remain in a declared project workspace.
+
+## Configure models deliberately
+
+The adapter intentionally does not set `model` in its agent files. OpenCode
+therefore uses the currently selected primary model and, by default, passes it
+to subagents. Set a `model: provider/model-id` field in each installed agent
+file when role-specific routing is wanted:
+
+| Agent | Recommended profile |
+| --- | --- |
+| `triad-orchestrator` | Reliable planning and orchestration model, medium reasoning. |
+| `triad-developer` | Highest-capability implementation model. |
+| `triad-evaluator` | Fresh, independent quality-comparison model. |
+| `triad-reviewer` | Independent, reliable review model, medium reasoning. |
+
+Use `opencode models` to inspect the provider/model identifiers available in
+the local installation. Keep the developer, evaluator, and reviewer separately
+configured when independent model routing is required.
+
+## Start the loop
+
+Launch OpenCode from the project-control repository, then enter:
+
+```text
+/triad <PRD location or concise project request>
+```
+
+For a new project, the orchestrator asks only for missing essentials that
+prevent safe setup or measurable cards, creates the control artifacts outside
+product repositories, declares the card plan, and begins. For an existing
+project, give its project ID or control-workspace path after `/triad` and it
+resumes from the recorded state.
+
+The developer, evaluator, and reviewer are hidden implementation subagents. The
+orchestrator can invoke only those three through the Task tool; the evaluator and
+reviewer have read-only file permissions but can run verification commands. The agents allow
+access to declared external worktrees so a multi-repository project can operate
+from its control repository. Their prompts still restrict work to paths,
+branches, and worktrees declared in the project manifest.
+
+OpenCode uses the capability-selected `explicit_dispatch` verification route:
+the orchestrator invokes `.triad-runtime/triad-verify.mjs` after the Developer
+stops and then validates its evidence. It records this decision by running
+`.triad-runtime/triad-runtime-capabilities.mjs --host opencode`; no undocumented
+OpenCode lifecycle hook is assumed.
+
+## Verify installation
+
+From the selected control repository, confirm that OpenCode discovered the
+agents:
+
+```bash
+opencode agent list
+```
+
+Then open the TUI and type `/triad`. The command description should appear.
+Before using the adapter for real delivery, follow the forward test in the
+[Codex replication guide](../../docs/codex-replication.md#forward-test-before-adopting): the
+same observable checks validate this OpenCode adapter.

package/adapters/opencode/install.sh

@@ -0,0 +1,75 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+usage() {
+  cat <<'EOF'
+Usage:
+  ./adapters/opencode/install.sh --project <control-repository-path>
+  ./adapters/opencode/install.sh --global
+
+Install the Triad+ Engineering Loop OpenCode adapter without overwriting any
+existing OpenCode agent, command, or Triad skill. --project installs into
+<control-repository-path>/.opencode. --global installs into
+$HOME/.config/opencode.
+EOF
+}
+
+if [[ $# -eq 2 && "$1" == "--project" ]]; then
+  target_root="$2/.opencode"
+  project_root="$2"
+  project_install=true
+elif [[ $# -eq 1 && "$1" == "--global" ]]; then
+  target_root="$HOME/.config/opencode"
+  project_root=""
+  project_install=false
+else
+  usage >&2
+  exit 2
+fi
+
+adapter_root="$(cd -- "$(dirname -- "${BASH_SOURCE[0]}")" && pwd)"
+repository_root="$(cd -- "$adapter_root/../.." && pwd)"
+
+agent_names=(triad-orchestrator triad-developer triad-evaluator triad-reviewer)
+skill_names=(triad-loop-bootstrap triad-loop-orchestrator triad-loop-developer triad-loop-evaluator triad-loop-reviewer)
+command_name="triad"
+collisions=()
+
+for agent_name in "${agent_names[@]}"; do
+  [[ -e "$target_root/agents/$agent_name.md" ]] && collisions+=("agents/$agent_name.md")
+done
+for skill_name in "${skill_names[@]}"; do
+  [[ -e "$target_root/skills/$skill_name" ]] && collisions+=("skills/$skill_name")
+done
+[[ -e "$target_root/commands/$command_name.md" ]] && collisions+=("commands/$command_name.md")
+if [[ "$project_install" == true && -e "$project_root/.triad-runtime" ]]; then
+  collisions+=(".triad-runtime")
+fi
+
+if [[ ${#collisions[@]} -gt 0 ]]; then
+  printf 'Installation aborted; existing paths would be overwritten:\n' >&2
+  printf '  %s\n' "${collisions[@]}" >&2
+  printf 'Remove or rename those paths deliberately, then run the installer again.\n' >&2
+  exit 1
+fi
+
+mkdir -p "$target_root/agents" "$target_root/commands" "$target_root/skills"
+
+for agent_name in "${agent_names[@]}"; do
+  cp "$adapter_root/.opencode/agents/$agent_name.md" "$target_root/agents/$agent_name.md"
+done
+cp "$adapter_root/.opencode/commands/$command_name.md" "$target_root/commands/$command_name.md"
+for skill_name in "${skill_names[@]}"; do
+  cp -R "$repository_root/skills/$skill_name" "$target_root/skills/$skill_name"
+done
+if [[ "$project_install" == true ]]; then
+  cp -R "$repository_root/runtime" "$project_root/.triad-runtime"
+  cp -R "$repository_root/schemas" "$project_root/.triad-runtime/schemas"
+  cp "$adapter_root/runtime.json" "$project_root/.triad-runtime/adapter.json"
+fi
+
+printf 'Triad+ Engineering Loop installed in %s\n' "$target_root"
+if [[ "$project_install" == true ]]; then
+  printf 'Control-plane runtime installed in %s/.triad-runtime\n' "$project_root"
+fi
+printf 'Start OpenCode in the target project and use /triad followed by a PRD source or project request.\n'

package/adapters/opencode/runtime.json

@@ -0,0 +1,6 @@
+{
+  "schema_version": 1,
+  "id": "opencode",
+  "binary": "opencode",
+  "lifecycle": null
+}