v1.4
SKILLS · ARCHITECTURE · v2 · MOBILE · v1.5

opchain skills ecosystem

Checkpoint-driven pipeline · 22 skills · 6 phases · 7 tri-agent · 3 audit gates · spine ordinals

Foundation · cross-cutting
PROTOCOL oc-checkpoint-protocol
JSON schema written by every skill: phase · progress · blockers · next_actions. Single source of truth — no database, no vendor lock-in.
ORCH oc-orchestrator
/oc-ops · routing · cross-project status · gate enforcement.
1 Discover Phase 1 of 6
1 oc-reverse-spec Specialist · Workflow /oc-rev-spec · /oc-rev-full

Reverse-engineer existing codebases into structured spec documents. The output feeds oc-app-architect as a Phase 2 baseline so the oc-orchestrator never starts from a cold context. Optional — greenfield projects skip this band entirely.

CPphase · codebase_scan · spec_output
2 Plan Phase 2 of 6
oc-scale-ops Advisor /oc-scale · perf · capacity auto-invoke ↓ ↑ advisory oc-stack-forge Advisor /oc-stack · /oc-stack-decide auto-invoke ↓ ↑ advisory 2 oc-app-architect Tri-agent · Orchestrator Generator / Evaluator · QA ≥ 7/10 /oc-app · /oc-discover · /oc-spec /oc-design · /oc-build · /oc-launch auto-invokes: oc-stack-forge · oc-ux-engineer auto-invoke ↓ ↑ advisory oc-migration-ops Specialist /oc-migrate · schema · platform ↓ spine 2 → 3 (build)

oc-app-architect anchors the spine, auto-invoking oc-stack-forge for platform decisions, taking advisory input from oc-scale-ops on capacity, and routing oc-migration-ops when a live system needs a schema, framework, or platform change. The plan checkpoint is the master record downstream skills consume. In v1.5, /oc-discover gained an “AI app?” branch that routes to the new AI phase.

CPphase · stack_decision · capacity · migration_plan
✦ Pack fabric v1.5 · 36

oc-stack-forge owns the registry; 6 skills consume it. Source: skills/oc-stack-forge/packs/<id>/pack.yml

LANGUAGES 13
buncsharpdenoelixirgojavakotlinphppythonrubyrustswifttypescript
FRAMEWORKS 9
dotnet-aspnetlaravel-phpphoenixremixsolidspring-javaspring-kotlinsveltekitswiftui
MOBILE 4
kotlin-androidflutterios-swiftuireact-native-expo
DEPLOY 6
app-storeaws-amplifyplay-storeherokunetlifyrailway
VECTOR-DB · NEW v1.5 4
pgvectorpineconesupabase-vectorsturbopuffer
consumed by oc-stack-forge · oc-app-architect · oc-migration-ops · oc-api-dev · oc-deploy-ops · oc-rag-forge View /coverage →
3 AI Phase 3 of 6 · NEW
↑ “AI app?” branch off oc-app-architect oc-claude-api Specialist · Advisor /oc-claude-api · model routing NEW · v1.5 · gated oc-rag-forge Tri-agent · Designer/Builder/Eval /oc-rag · vector DB · eval NEW · v1.5 · gated oc-agent-forge Tri-agent · Planner/Builder/Eval /oc-agent · Agent SDK NEW · v1.5 · gated oc-prompt-ops Specialist · prompt-as-code /oc-prompt · eval · regression NEW · v1.5 · gated ↓ checkpoints → oc-app-architect → build

v1.5 adds an AI-native phase. When /oc-discover flags an AI app, oc-app-architect auto-invokes four new skills — oc-claude-api (model routing · caching · tool use · migration), the tri-agent pair oc-rag-forge (vector DB · embeddings · hybrid search · retrieval eval) and oc-agent-forge (Agent SDK · subagents · tool budgets · agent eval), and oc-prompt-ops (prompt versioning · eval datasets · regression). All four ship gated behind skills.registry.<id>.enabled and return checkpoints to oc-app-architect; oc-rag-forge consumes the vector-db packs.

CPphase · model_routing · retrieval · agent_topology · prompt_versions
3 Build Phase 4 of 6
oc-ux-engineer Tri-agent · Planner / Generator / Eval /oc-uxe · /oc-design branches → oc-dash-forge oc-dash-forge Specialist · Tufte-density UI /oc-data-forge · /dashboard parallel build track ↓ PARALLEL · API + INTEGRATIONS oc-api-dev Tri-agent · OpenAPI / GraphQL first-party API surface branches → oc-code-auditor oc-integrations-engineer Tri-agent · Planner / Builder / Tester /oc-integrate · OAuth · webhooks branches → oc-code-auditor ↑ ALL 4 RETURN CHECKPOINTS to oc-app-architect (Phase 2) ↓ spine 3 (ship)

Three tri-agent loops (oc-ux-engineer · oc-api-dev · oc-integrations-engineer) plus the dense-UI specialist (oc-dash-forge) work in parallel. oc-ux-engineer hands data-heavy screens to oc-dash-forge; oc-api-dev produces an OpenAPI/GraphQL contract that the deploy-time drift gate later enforces. All four feed checkpoints back to oc-app-architect.

CPphase · ux_specs · api_surface · integrations · dashboards
4 Ship Phase 5 of 6
oc-bug-check Audit gate · pre-commit type · lint · secrets · vuln /oc-bugcheck 3 oc-git-ops Specialist · Workflow /oc-git · /oc-commit · /oc-pr · /oc-push auto-runs oc-bug-check pre-commit ↑ ↓ MUST PASS BEFORE PROD oc-code-auditor Tri-agent · gates prod Auditor · Fixer · Verifier /oc-audit · score ≥ 7/10 branches → oc-security-auditor oc-security-auditor Audit gate · posture review STRIDE · OWASP · TLS · CSP /oc-security · /oc-threat-model 3rd of 3 gates 3 GATES PASSED → RELEASE 4 oc-release-ops Specialist · Workflow · release-boundary only plan draft bump announce ship activates at release boundaries only /oc-release · changelog · semver bump · ticket · post hand off 5 oc-deploy-ops Orchestrator · Workflow /oc-deploy gates → prod → rollback enforces all 3 audit gates ↓ spine 5 → 6 (monitor)

Three audit gates (oc-bug-check pre-commit, oc-code-auditor for code-level findings, oc-security-auditor for STRIDE/OWASP/infra) all must pass before oc-deploy-ops will run the production sequence. At release boundaries the spine threads oc-git-ops → oc-release-ops → oc-deploy-ops; oc-release-ops produces the changelog · version bump · release ticket · announcement, then hands off (it is not itself a deployer). v1.5 taught oc-code-auditor prompt-injection and tool-use safety rules for AI apps.

CPphase · audit_score · posture · branch · pr · release_tag · deploy_status
5 Monitor Phase 6 of 6
6 oc-monitoring-ops Specialist · observability /oc-monitor · uptime · SLO + oc-api-dev SLO/drift manifest

oc-deploy-ops hands off to oc-monitoring-ops once production is green. oc-monitoring-ops also receives oc-api-dev's SLO + drift manifest so contract violations alert the same way uptime errors do. Incident response runbooks and postmortems live here.

CPphase · slo_status · alert_rules · incident_log
Appendix A · Cross-cutting
Checkpoint Protocol — sync topology

Every skill (all 22) writes a JSON checkpoint after each state change. The oc-orchestrator both reads from and writes to each — bidirectional sync. Diagram below shows 6 representative connections; the same topology extends to all 22 skills.

CP oc-reverse-spec CP oc-app-architect CP oc-git-ops oc-orchestrator /oc-ops · routing · sync reads + writes all CPs CP oc-deploy-ops CP monitor-ops CP oc-code-auditor
{
  "skill": "oc-app-architect",
  "phase": "build",
  "progress_table": { "discover": "complete" },
  "context_primer": "2-sentence summary...",
  "blockers": ["waiting on API key"],
  "next_actions": ["/oc-git-sync"]
}
Appendix B · Cross-cutting
Orchestrator — routing decision flow

When a request enters /oc-ops, the oc-orchestrator reads source-skill checkpoint state, decides the next skill, and dispatches. All three states shown together (desktop version animates each in sequence).

source skill writes checkpoint · requests next request oc-orchestrator read source CP match next_actions to registry enforce gates → dispatch dispatch target skill activates · writes new checkpoint

Legend

Connections · markers · skill types
N
Spine ordinal
Numbered mint pill on the 6 primary-spine skills marks handoff position. Replaces directional arrows between bands — vertical reading order is the sequence.
1 oc-reverse-spec → 2 oc-app-architect → 3 oc-git-ops → 4 oc-release-ops → 5 oc-deploy-ops → 6 oc-monitoring-ops
Auto-invoke
Orchestrator silently triggers a sub-skill without explicit user command. The sub-skill operates in the oc-orchestrator's current phase context.
e.g. oc-app-architect → oc-stack-forge · oc-app-architect → oc-ux-engineer
Advisory
Non-blocking recommendations passed via checkpoint. The receiver can accept or override. No hard dependency.
e.g. oc-scale-ops → oc-app-architect · oc-migration-ops ↔ oc-app-architect
Audit gate
Pipeline blocks until the gate writes a passing result. Three gates in this ecosystem: oc-bug-check (pre-commit), oc-code-auditor (code-level), oc-security-auditor (posture).
score ≥ 7/10 · STRIDE clean · zero critical CVEs
CP · checkpoint indicator
Solid ember dot in each skill's top-right corner indicates the skill writes a checkpoint. All 22 skills carry CP — desktop version shows full CP badge on each rect; mobile uses the dot for legibility.
.checkpoints/<skill>.json · phase · progress · blockers · next_actions
ORC · oc-orchestrator indicator
Faded ember dot adjacent to the CP dot indicates the skill participates in /oc-ops routing. All 22 skills carry ORC — every skill is route-addressable by the oc-orchestrator.
/oc-ops · cross-project routing · gate enforcement · "what should I do next"
Skill types
Tri-agent
Skills running an internal Planner / Generator / Evaluator loop. The Evaluator scores output (≥ 7/10 to advance); failure triggers Generator retry until threshold or max iterations.
oc-app-architect · oc-ux-engineer · oc-api-dev · oc-integrations-engineer · oc-code-auditor · oc-rag-forge · oc-agent-forge
Advisor
Non-orchestrating skills that return recommendations or analysis. No tri-agent loop. Results fed back via checkpoint; caller can override.
oc-stack-forge · oc-scale-ops
Standalone specialist
Single-purpose skills that produce a concrete artifact and hand it off. No internal loop, no orchestration of others.
oc-reverse-spec · oc-dash-forge · oc-git-ops · oc-release-ops · oc-migration-ops · oc-monitoring-ops
Workflow / oc-orchestrator
Skills that drive structured, sequential pipelines. oc-app-architect orchestrates the build; oc-deploy-ops orchestrates the ship; oc-orchestrator routes across projects.
oc-app-architect · oc-deploy-ops · oc-orchestrator
Audit gate
Quality enforcement skills that block pipeline progression until thresholds are met. Three in this ecosystem cover three layers: pre-commit, code-level (also tri-agent — see yellow stroke on oc-code-auditor), security posture.
oc-bug-check · oc-code-auditor · oc-security-auditor

Reference

Pipeline patterns at a glance

Spine Ordinals

  • Mint pills on the 6 spine skills mark the handoff sequence
  • 1 oc-reverse-spec → 2 oc-app-architect → 3 oc-git-ops → 4 oc-release-ops → 5 oc-deploy-ops → 6 oc-monitoring-ops
  • Direction is implicit from vertical reading order
  • Branch handoffs noted inline as captions:
  •   oc-ux-engineer → oc-dash-forge
  •   oc-api-dev / integ-eng → oc-code-auditor
  •   oc-code-auditor → oc-security-auditor

Tri-Agent Patterns (7)

  • oc-app-architect: Generator / Evaluator
  • oc-ux-engineer: Planner / Generator / Evaluator
  • oc-api-dev: Planner / Generator / Evaluator
  • oc-integrations-engineer: Planner / Builder / Tester
  • oc-code-auditor: Auditor / Fixer / Verifier
  • oc-rag-forge: Designer / Builder / Evaluator (v1.5)
  • oc-agent-forge: Planner / Builder / Evaluator (v1.5)

Audit Gates (3)

  • oc-bug-check — pre-commit type/lint/secret scan
  • oc-code-auditor — code-level Auditor/Fixer/Verifier
  • oc-security-auditor — STRIDE / OWASP / infra hardening
  • All three must pass before oc-deploy-ops ships

Checkpoint Protocol

  • JSON files at .checkpoints/<skill>.json
  • Keys: phase · progress_table · context_primer · blockers · next_actions
  • All 22 skills read all 22 checkpoints (no ACL)
  • Resume order: own → upstream → novice mode
  • Framework-agnostic — no platform lock-in

Routing Key

  • Bus pattern: 1 trunk + N branches for fan-outs/fan-ins
  • Width: spine 2px · secondary 1.8px · advisory 1.5px · gate 2px
  • Style: solid for spine handoffs · dashed for auto-invoke / advisory / gate
  • Bidirectional: paired arrows when the receiver also sends back (advisor pattern)
  • Mobile note: vertical reading order replaces left-right gutter routing from desktop
static · mobile · 390pt · no JS · no animations
SKILLS · ARCHITECTURE · v2 · RELEASE v1.5

opchain skills ecosystem

Checkpoint-driven pipeline · 22 skills · 6 phases · 7 tri-agent · 3 audit gates · spine ordinals · v1.5 pack fabric (36)

Every skill writes a JSON checkpoint after each state change. Single source of truth — any skill can read any other's to rebuild context. Plain JSON on disk · no database · no vendor lock-in.

{
  "skill": "oc-app-architect",
  "phase": "build",
  "progress_table": { "discover": "complete", "spec": "in_progress" },
  "context_primer": "2-sentence summary...",
  "blockers": ["waiting on API key"],
  "next_actions": ["/oc-git-sync"]
}
oc-orchestrator /oc-ops · routing · sync CP oc-reverse-spec CP oc-app-architect CP oc-stack-forge CP oc-api-dev CP oc-dash-forge CP oc-ux-engineer

The oc-orchestrator routes every skill invocation across projects. Tracks which checkpoint is current, enforces audit gates before deploys, and answers /oc-ops queries. Reads all 22 checkpoints; writes its own pipeline state.

CP oc-app-architect checkpoint update oc-orchestrator /oc-ops · routing → build sprint deciding CP oc-ux-engineer CP oc-dash-forge CP oc-api-dev
DISCOVER
oc-reverse-spec — standalone specialist; reverse-engineers existing code into spec docs oc-reverse-spec Specialist · Workflow /oc-rev-spec · /oc-rev-full CP ORC 1·↓2
skills
oc-reverse-spec
checkpt
CP phase · codebase_scan · spec_output
links
↓ handoff to plan
Phase 1 of 6
Discover
Reverse-engineer existing codebases into structured spec documents. The output feeds oc-app-architect as a Phase 2 baseline so the oc-orchestrator never starts from a cold context. Optional — greenfield projects skip this band entirely.
PLAN
oc-scale-ops — advisor; capacity planning, perf budgets, load-test guidance oc-scale-ops Advisor /oc-scale · perf · capacity CP ORC oc-stack-forge — advisor; recommends platform, framework, hosting oc-stack-forge Advisor /oc-stack · /oc-stack-decide CP ORC oc-app-architect — tri-agent oc-orchestrator: Generator / Evaluator loop; idea → spec → design → build → launch. v1.5: /oc-discover routes AI apps to the AI phase. oc-app-architect Tri-agent · Orchestrator Generator / Evaluator · QA loop ≥ 7/10 /oc-app · /oc-discover · /oc-spec /oc-design · /oc-build · /oc-launch auto-invokes: oc-stack-forge · oc-ux-engineer · oc-api-dev · oc-dash-forge “AI app?” /oc-discover → claude-api · rag-forge · agent-forge · prompt-ops CP ORC ↑1·2·↓3 oc-migration-ops — specialist; database/framework/platform migrations oc-migration-ops Specialist /oc-migrate · schema · platform CP ORC auto-invoke advisory advisory auto-invoke auto-invoke advisory
skills
oc-app-architect oc-stack-forge oc-scale-ops oc-migration-ops
checkpt
CP phase · stack_decision · capacity · migration_plan
links
↑ from discover ↓ to build
Phase 2 of 6
Plan
oc-app-architect anchors the spine, auto-invoking oc-stack-forge for platform decisions, taking advisory input from oc-scale-ops on capacity, and routing oc-migration-ops when a live system needs a schema, framework, or platform change. The plan checkpoint is the master record downstream skills consume.
PACK FABRIC
v1.5 · cross-cutting · oc-stack-forge owns
Pack fabric — language · framework · mobile · deploy · vector-db

Declared in skills/oc-stack-forge/packs/<id>/pack.yml · drives skills.coverage.<id>.enabled · consumed by oc-stack-forge · oc-app-architect · oc-migration-ops · oc-api-dev · oc-deploy-ops · oc-rag-forge

v1.5 · 36 packs →
LANGUAGES 13
buncsharpdenoelixirgojavakotlinphppythonrubyrustswifttypescript
FRAMEWORKS 9
dotnet-aspnetlaravel-phpphoenixremixsolidspring-javaspring-kotlinsveltekitswiftui
MOBILE 4
kotlin-androidflutterios-swiftuireact-native-expo
DEPLOY 6
app-storeaws-amplifyplay-storeherokunetlifyrailway
VECTOR-DB 4
pgvectorpineconesupabase-vectorsturbopuffer
AI
oc-claude-api — specialist/advisor (NEW v1.5, flag-gated); model routing, prompt caching, tool use, version-migration playbooks oc-claude-api Specialist · Advisor routing · caching · tool use /oc-claude-api NEW · v1.5 · gated CP ORC oc-rag-forge — tri-agent: Designer / Builder / Evaluator (NEW v1.5, flag-gated); vector-DB choice, embeddings, chunking, hybrid search, retrieval eval oc-rag-forge Tri-agent Designer · Builder · Eval /oc-rag · vector DB NEW · v1.5 · gated CP ORC oc-agent-forge — tri-agent: Planner / Builder / Evaluator (NEW v1.5, flag-gated); Claude Agent SDK scaffold, subagent topology, tool-budget design, harness loops, agent eval oc-agent-forge Tri-agent Planner · Builder · Eval /oc-agent · Agent SDK NEW · v1.5 · gated CP ORC oc-prompt-ops — specialist (NEW v1.5, flag-gated); prompts as versioned, diffable artifacts — eval datasets, regression and drift detection oc-prompt-ops Specialist prompt-as-code · eval /oc-prompt NEW · v1.5 · gated CP ORC
skills
oc-claude-api oc-rag-forge oc-agent-forge oc-prompt-ops
checkpt
CP phase · model_routing · retrieval · agent_topology · prompt_versions
links
↑ auto-invoked by oc-app-architect · “AI app?” branch ↓ checkpoints back to oc-app-architect
Phase 3 of 6 · NEW v1.5
AI
v1.5 adds an AI-native phase. When /oc-discover detects an AI app, oc-app-architect routes to four new skills: oc-claude-api (model routing, prompt caching, tool use, version migration), the tri-agent pair oc-rag-forge (vector-DB choice, embeddings, hybrid search, retrieval eval) and oc-agent-forge (Agent SDK, subagent topology, tool budgets, agent eval), and oc-prompt-ops (prompts as versioned, eval-gated artifacts). All four ship gated behind skills.registry.<id>.enabled and feed checkpoints back to oc-app-architect; oc-rag-forge consumes the vector-db packs.
BUILD
oc-ux-engineer — tri-agent: Planner / Generator / Evaluator. Auto-attaches Design Evaluator to UI sprints. oc-ux-engineer Tri-agent Planner · Generator · Eval /oc-uxe · /oc-design → oc-dash-forge CP ORC oc-dash-forge — standalone specialist; dashboard + dense-info UI designer (Tufte density) oc-dash-forge Specialist Tufte-density UI /oc-data-forge · /dashboard CP ORC oc-api-dev — tri-agent; first-party API surface; OpenAPI/GraphQL elaboration oc-api-dev Tri-agent OpenAPI / GraphQL first-party API surface → oc-code-auditor CP ORC oc-integrations-engineer — tri-agent: Planner / Builder / Tester; third-party API integrations (OAuth, webhooks) integrations-eng Tri-agent Planner · Builder · Tester /oc-integrate · OAuth · webhooks → oc-code-auditor CP ORC
skills
oc-ux-engineer oc-dash-forge oc-api-dev integrations-eng
checkpt
CP phase · ux_specs · api_surface · integrations · dashboards
links
↑ auto-invoked by oc-app-architect ↓ to ship gates
Phase 4 of 6
Build
Three tri-agent loops (oc-ux-engineer · oc-api-dev · oc-integrations-engineer) plus the dense-UI specialist (oc-dash-forge) work in parallel. oc-ux-engineer hands data-heavy screens to oc-dash-forge; oc-api-dev produces an OpenAPI/GraphQL contract that the deploy-time drift gate later enforces. All four feed checkpoints back to oc-app-architect.
SHIP
oc-git-ops — specialist; branch, commit, PR, sync oc-git-ops Specialist · Workflow /oc-git · /oc-commit · /oc-pr · /oc-push CP ORC ↑2·3·↓4 oc-release-ops — specialist · workflow; plan/draft/bump/announce/ship a versioned release. Sits between oc-git-ops and oc-deploy-ops — activates at release boundaries only. oc-release-ops Specialist · Workflow · release-boundary only plan draft bump announce ship /oc-release · changelog · semver bump · ticket · post ↑3·4·↓5 oc-deploy-ops — oc-orchestrator; staging, prod, rollback, audit gate enforcement oc-deploy-ops Orchestrator · Workflow /oc-deploy · gates → prod → rollback CP ORC ↑4·5·↓6 oc-bug-check — audit gate; pre-commit type/lint/secret/vulnerability scan oc-bug-check Audit gate · pre-commit type · lint · secrets · vuln /oc-bugcheck CP ORC oc-code-auditor — tri-agent: Auditor / Fixer / Verifier; functions as audit gate (red dashed exits gate the production deploy) oc-code-auditor Tri-agent · gates prod Auditor · Fixer · Verifier /oc-audit · ≥7/10 · AI-safety → oc-security-auditor CP ORC oc-security-auditor — audit gate; STRIDE threat model, OWASP Top 10, infra hardening oc-security-auditor Audit gate · posture review STRIDE · OWASP · TLS · CSP /oc-security · /oc-threat-model CP ORC pre-commit audit gate posture gate
skills
oc-bug-check oc-git-ops oc-release-ops oc-code-auditor oc-security-auditor oc-deploy-ops
checkpt
CP phase · audit_score · posture · branch · pr · release_tag · deploy_status
links
3 audit gates block prod oc-release-ops at release boundaries ↓ handoff to monitor
Phase 5 of 6
Ship
Three audit gates (oc-bug-check pre-commit, oc-code-auditor for code-level findings, oc-security-auditor for STRIDE/OWASP/infra) all must pass before oc-deploy-ops will run the production sequence. At release boundaries the spine threads oc-git-ops → oc-release-ops → oc-deploy-ops; oc-release-ops produces changelog · version bump · release ticket · announcement, then hands off (it is not itself a deployer). The gate cluster sits below and writes blocker status into shared checkpoints. v1.5 taught oc-code-auditor prompt-injection and tool-use safety rules for AI apps.
MONITOR
oc-monitoring-ops — specialist; uptime, error tracking, alerting, SLO dashboards, incident response oc-monitoring-ops Specialist · observability /oc-monitor · uptime · SLO · incidents CP ORC ↑5·6
skills
oc-monitoring-ops
checkpt
CP phase · slo_status · alert_rules · incident_log
links
↑ handoff from oc-deploy-ops oc-api-dev SLO + drift manifest
Phase 6 of 6
Monitor
oc-deploy-ops hands off to oc-monitoring-ops once production is green. oc-monitoring-ops also receives oc-api-dev's SLO + drift manifest so contract violations alert the same way uptime errors do. Incident response runbooks and postmortems live here.
connections
↑N↓
spine ordinal
auto-invoke
advisory
audit gate
CP · checkpoint
ORC · oc-orchestrator
skill types
tri-agent
advisor
specialist
workflow / oc-orchestrator
audit gate
AI-native · v1.5

Spine Ordinals

  • · Ember chips on the 6 spine skills mark the handoff sequence
  • · 1 oc-reverse-spec → 2 oc-app-architect → 3 oc-git-ops → 4 oc-release-ops → 5 oc-deploy-ops → 6 oc-monitoring-ops
  • · Each chip carries ↑prev·↓next for direction
  • · Branch handoffs as inline mint pills inside source rects:
  •   oc-ux-engineer → oc-dash-forge
  •   oc-api-dev / integ-eng → oc-code-auditor
  •   oc-code-auditor → oc-security-auditor

Tri-Agent Patterns (7)

  • · oc-app-architect: Generator / Evaluator
  • · oc-ux-engineer: Planner / Generator / Evaluator
  • · oc-api-dev: Planner / Generator / Evaluator
  • · oc-integrations-engineer: Planner / Builder / Tester
  • · oc-code-auditor: Auditor / Fixer / Verifier
  • · oc-rag-forge: Designer / Builder / Evaluator
  • · oc-agent-forge: Planner / Builder / Evaluator

Audit Gates (3)

  • · oc-bug-check — pre-commit type/lint/secret scan
  • · oc-code-auditor — code-level Auditor/Fixer/Verifier
  • · oc-security-auditor — STRIDE / OWASP / infra hardening
  • · All three must pass before oc-deploy-ops ships

AI Phase (v1.5)

  • · Phase 3 of 6 — auto-invoked via oc-app-architect's "AI app?" branch
  • · oc-claude-api — model routing · prompt caching · tool use · migration
  • · oc-rag-forge — tri-agent; vector DB · embeddings · retrieval eval
  • · oc-agent-forge — tri-agent; Agent SDK · subagents · tool budgets
  • · oc-prompt-ops — prompt versioning · eval datasets · regression
  • · All four gated behind skills.registry.<id>.enabled

Checkpoint Protocol

  • · JSON files at .checkpoints/<skill>.json
  • · Keys: phase · progress_table · context_primer · blockers · next_actions
  • · All 22 skills read all 22 checkpoints (no ACL)
  • · Resume: own → upstream → novice mode
  • · Framework-agnostic — no platform lock-in

Routing Key

  • · Bus pattern: 1 trunk + N branches for fan-outs/fan-ins
  • · Lane offsets: handoff −10, auto-invoke −3, advisory +4, gate +11
  • · Width: spine 1.8 · secondary 1.2 · advisory 1.0 · gate 1.4
  • · Opacity: spine .95 · secondary .78 · advisory .55
  • · Long-jumps: route via left/right gutter (safeX 32)
  • · Edge centers only: top receives, bottom sends
  • · Bidirectional: single line, both arrowheads (e.g. oc-migration-ops ↔ app-arch)

opchain skills ecosystem v2 · asfbay-bit/opchain · 22 skills · 6 phases · 7 tri-agent · 3 audit gates · spine ordinals · v1.5 · checkpoint-driven