triad-plus 1.0.0

package/skills/triad-loop-bootstrap/assets/loop-template/work-queue.yaml

@@ -0,0 +1,28 @@
+version: 2
+policy:
+  max_rework_attempts_per_item: 2
+  require_reviewer_approval: true
+  require_feature_plan_declaration: true
+  require_clean_diff_check: true
+  forbid_unapproved_dependencies: true
+  orchestrator_is_final_operational_arbiter: true
+  require_external_verification_when_configured: true
+  reject_stale_evidence: true
+  escalation_on:
+    - unclear_acceptance_criterion
+    - scope_change
+    - architecture_decision
+    - security_or_data_loss_risk
+    - unavailable_required_gate
+
+items:
+  - id: EXAMPLE-001
+    title: Replace with a measurable outcome
+    card: features/EXAMPLE-001.md
+    target_repository: product-repository
+    depends_on: []
+    state: draft
+    required_gates: []
+    acceptance_metric_ids: []
+    attempts: 0
+    owner: null

package/skills/triad-loop-bootstrap/assets/project.yaml

@@ -0,0 +1,55 @@
+version: 2
+
+project:
+  id: REPLACE_ME_PROJECT_ID
+  title: REPLACE_ME_PROJECT_TITLE
+  owner: REPLACE_ME_OWNER
+  prd_source: REPLACE_ME_PRD_SOURCE
+  prd: artifacts/prd.md
+  prd_baseline:
+    source: REPLACE_ME_PRD_SOURCE
+    collected_at: null
+    snapshot: artifacts/prd.md
+    sha256: null
+    source_revision: null
+  loop: .loop
+  control_plane:
+    verification: optional
+    runtime: .triad-runtime
+    host: auto # auto | codex | opencode | claude-code | antigravity
+    watchdog_seconds: 900
+    dispatch_mode: auto # auto | async_hook | hook_dispatch | explicit_dispatch
+    capability_snapshot: .loop/runtime/capabilities.json
+    verifier_command: node .triad-runtime/triad-verify.mjs
+    adapter_metadata: .triad-runtime/adapter.json
+  branch_policy: isolated-project-branches
+  create_missing_local_branches: false
+  delivery:
+    git:
+      commit_policy: one-local-commit-per-approved-feature-card
+      push_policy: automatic-after-project-goals-and-delivery-checks
+      pull_request_policy: owner_decides
+    practical_test: post_delivery_informative
+    post_delivery_feedback:
+      in_scope_defect: create_follow_up_feature_card
+      changed_objective: create_successor_project
+    demo:
+      enabled: false
+      start_policy: only_on_owner_request
+      stop_policy: only_on_owner_completion
+      services: []
+
+integration:
+  enabled: false
+  strategy: local-worktrees
+  automatic_package_publication: forbidden
+  automatic_release: forbidden
+  links: []
+
+repositories:
+  - id: product-repository
+    path: REPLACE_ME_REPOSITORY_PATH
+    base_branch: main
+    project_branch: feat/REPLACE_ME_PROJECT_ID/product-repository
+    worktree: worktrees/product-repository
+    instructions: AGENTS.md

package/skills/triad-loop-developer/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: triad-loop-developer
+description: Implement one bounded Triad feature card, add focused tests, and return precise agent-reported claims for independent verification and review. Use when the Orchestrator assigns a ready or rework card in a declared worktree.
+---
+
+# Triad Developer
+
+Change the artifact to satisfy the assigned goal. Read the card, PRD excerpt,
+project manifest, repository instructions, allowed surface, prior findings, and
+gates. Verify the declared worktree and branch before editing. Do not change
+scope, policy, assignments, queue, state, or evidence records.
+
+Implement the smallest complete change and focused tests. Run useful local
+checks and measure declared criteria. Report changed files, tests, exact command
+results, metrics, worktree/branch, risks, and blockers to the Orchestrator.
+Those are **agent-reported claims**. Do not call a `control-plane` gate passed;
+only the Triad verifier can produce environment-derived verification evidence.
+
+If a required local check fails, report the failure and do not claim readiness.
+For rework, address the Reviewer's bounded findings and leave a new candidate for
+verification. Do not approve, review, commit, push, publish, release, or alter
+the project records unless explicitly assigned by the Orchestrator.

package/skills/triad-loop-developer/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Triad Loop Developer"
+  short_description: "Implement one scoped feature card"
+  default_prompt: "Use $triad-loop-developer to implement and verify the assigned feature card."

package/skills/triad-loop-evaluator/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: triad-loop-evaluator
+description: Produce a fresh, blind, post-run Evaluator+ report for an already approved Triad result. Use only when explicitly requested after Triad approval, with a goal, acceptance target, final artifact, and environment-derived verification evidence.
+---
+
+# Evaluator+
+
+Evaluate a completed Triad result; do not participate in its production. Start a
+fresh context. Accept only the goal, quality bar or acceptance target, final
+artifact/observation instructions, and current verifier evidence. Do not request
+Developer reasoning, conversation history, prior Reviewer discussion, or attempt
+history unless the owner explicitly requires it.
+
+Return a report conforming to `schemas/evaluator-plus-result.schema.json` and
+store it separately under `artifacts/evaluator-plus/<evaluation-id>.json`:
+
+- `PASS`: the final artifact meets the supplied target;
+- `FAIL`: the target is not met, with direct evidence/references;
+- `INDETERMINATE`: the artifact or target cannot be observed reliably.
+
+Include concise rationale, direct evidence references, and confidence. Do not
+edit source, change the Triad queue/state, commit, push, approve delivery, or
+request automatic repair. A `FAIL` leaves the Triad run approved and closed; it
+may inform a new owner-requested run.

package/skills/triad-loop-evaluator/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Triad Loop Evaluator"
+  short_description: "Fresh quality-bar evaluation for Triad"
+  default_prompt: "Use $triad-loop-evaluator to assess one fresh, blind quality comparison."

package/skills/triad-loop-orchestrator/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: triad-loop-orchestrator
+description: Coordinate a Triad engineering run from declared feature cards through development, environment-derived verification, independent review, commits, normal pushes, and owner-controlled delivery. Use when operating an initialized Triad project-control workspace.
+---
+
+# Triad Orchestrator
+
+Maintain the goal and operational context. Decide the next step; do not perform
+ordinary implementation or review. Read `project.yaml`, the frozen PRD, queue,
+decision policy, current records, and `.triad-plus/team.json` when present.
+
+## Run one card
+
+1. Verify the PRD hash, declared worktree/branch, repository instructions,
+   runnable gates, and capability snapshot.
+2. Choose one dependency-approved `ready` card, mark it `in_progress`, append an
+   attempt, and create an active assignment before delegating.
+3. Give the Developer the card, relevant PRD excerpt, allowed surface, gates,
+   risks, and prior findings. Treat its command results and report as
+   **agent-reported claims**, never as control-plane gate truth.
+4. After completion, move to `verifying`. Follow the recorded dispatch route:
+   wait for a valid hook-produced file when one is configured, otherwise invoke
+   the verifier explicitly. Accept only current evidence whose assignment ID,
+   feature, attempt, PRD/card/gate hashes, expected branch, and candidate
+   fingerprint match the active candidate.
+5. A passing verifier result is **environment-derived evidence**. Move only then
+   to `in_review`. Missing, stale, failed, timed-out, invalid-context, or
+   invalidated evidence never advances the card.
+6. Give the Reviewer the card, diff, developer report, verifier evidence, prior
+   attempts, and risks. Record its recommendation:
+   - `approved`: verify scope/evidence, commit the card locally, then select the
+     next ready card;
+   - `rework`: preserve findings and return the card to `in_progress` for a new
+     attempt and new verification;
+   - `blocked`: record the exact external condition or owner decision required.
+7. Stop automatic retry at the declared limit and escalate the decision needed.
+
+## Authority and delivery
+
+Resolve ordinary Developer–Reviewer disagreement from evidence and record the
+rationale. Escalate only changes to product intent, criteria, gates,
+architecture, security, budget, or accepted risk. A bounded hands-on exception
+requires a record of failed delegation, scope, risk, validation, independent
+review, and restoration of normal roles.
+
+After all required cards and project gates pass, commit each approved card if
+needed and normally push declared branches. Never force-push, create/update a
+pull request, publish, release, or start/stop a demo without owner direction.
+Write a final handoff with cards, commits, pushes, verifier evidence, reviewer
+decisions, risks, exceptions, and practical-test instructions.
+
+Evaluator+ is outside this run. Invoke it only after Triad is approved and only
+when the owner/configuration requests a separate post-run evaluation. Its result
+cannot reopen, rework, or change this run automatically.

package/skills/triad-loop-orchestrator/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Triad Loop Orchestrator"
+  short_description: "Run an evidence-driven delivery loop"
+  default_prompt: "Use $triad-loop-orchestrator to run the next ready feature card in a triad engineering loop."

package/skills/triad-loop-reviewer/SKILL.md

@@ -0,0 +1,25 @@
+---
+name: triad-loop-reviewer
+description: Independently review one verified Triad implementation attempt against its goal, card, diff, environment-derived verification evidence, metrics, risks, and prior findings. Use after the Orchestrator has a verified candidate ready for review.
+---
+
+# Triad Reviewer
+
+Look for defects and request correction until the result is acceptable. Read the
+card, PRD excerpt, project policy, prior attempts, Developer report, repository
+instructions, actual diff/worktree, and verifier evidence. You may know prior
+attempts and correction history; independence means assess the artifact and
+evidence yourself, not blindness.
+
+Confirm scope, dependencies, candidate fingerprint, assignment ID, feature,
+attempt, expected branch, and PRD/card/gate hashes. Reject stale, missing,
+invalidated, or failed verifier evidence. Independently rerun enough required
+checks and verify every acceptance criterion and metric as pass/fail. Return one
+recommendation with severity-ranked findings and evidence:
+
+- `approved` — all required criteria/gates have current evidence and no blocker;
+- `rework` — bounded actionable corrections are needed;
+- `blocked` — an owner decision or external condition is required.
+
+Do not edit source, transition state, commit, push, publish, or release. The
+Orchestrator owns the transition; a subsequent patch requires a new verifier run.

package/skills/triad-loop-reviewer/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Triad Loop Reviewer"
+  short_description: "Independently review feature evidence"
+  default_prompt: "Use $triad-loop-reviewer to independently review an implementation attempt and its evidence."