| name | rcc-dev-skills |
| description | RouteCodex V3 evidence-first development: query resource/function/mainline/verification maps, prove first divergence, patch one owner, then run mapped gates and installed same-entry replay. Use for debug, protocol, provider, routing, continuation, SSE, servertool, or runtime changes. |
RouteCodex V3 Development
This skill owns V3 command and gate sequencing. Inherit general methods from coding-principals and boundaries from project AGENTS.md; do not also run a generic development phase workflow. Pure instruction/document edits validate affected references and contracts; runtime build/install/restart/replay applies only when runtime behavior or its delivery changes.
Command-First Flow
- Read
AGENTS.md.
- Query maps before source:
rcc_task_feature='<feature_id>'
rg -n "feature_id: ${rcc_task_feature}" \
docs/architecture/v3-resource-operation-map.yml \
docs/architecture/v3-function-map.yml \
docs/architecture/v3-mainline-call-map.yml \
docs/architecture/v3-verification-map.yml
- Lock resource edge, owner, allowed/forbidden paths, caller/callee, and required gates. Missing or ambiguous binding blocks edits.
Confirm these architecture truths before accepting the map binding:
- V3 is production; V4 is an unconnected refactor; V2 runtime/config/backup ownership is absent.
- The fixed skeleton is configured through typed declarations, with data and control resources physically separate.
- Same-protocol execution defaults to Direct unless configuration explicitly selects Relay.
- Direct payload rewriting exists only in registered Direct hooks. Relay payload rewriting exists only in request/response Chat Process.
- Inbound is lossless normalization only. Outbound is standard target-protocol projection and may filter only unrepresentable fields through declared allowlists/denylists. Compat owns provider-private adjustments only.
- SSE owns the client boundary. Provider attempts are fully buffered before client commit, and provider errors remain independent from client response projection.
- Internal request/response failures are
598/599, network failures are 502, and linked external failures retain their real status.
A conflicting source or map is remediation evidence, not permission to record the target contract as already implemented.
- Read mapped source, generated review surface, current run notes, project
MEMORY.md, and relevant history.
- For defects, capture one request id and find first semantic divergence. Keep one active hypothesis.
- Record red evidence: focused failing test, saved failing shape, or controlled replay.
- Patch only mapped owner. Run positive and negative tests.
- Run feature
required_gates, then project architecture gate:
npm run verify:v3-architecture-ci
- Runtime-impacting change: load
references/50-rcc-config-ssot.md; prove build, install, config check, managed restart, all-listener health, and same-entry replay.
- If a failing runtime sample exists, include its exact replay or same-entry semantic equivalent in step 9 evidence. Review only after verification; do not repeat an unchanged replay solely for this step.
Review Gate
After verification and before commit/merge, use the reviewer selected by global AGENTS.md and its shared review standards. Apply project Semantic Invariants and mapped owner/edge/gate bindings. Preserve declared Target reselection and registered Direct/Relay differences; they do not authorize an undeclared reroute or compensating implementation. Reject payload rewriting outside Direct hooks or Relay Chat Process, partial provider-attempt exposure to clients, client reconstruction of provider errors, Inbound filtering, or provider-private behavior implemented as a second Outbound. Do not maintain a second copy of the global ablation checklist or historical-finding policy here.
Routes
| Need | Reference |
|---|
| owner and gates | references/40-owner-registry.md |
| first-divergence pipe debug | references/10-pipedebug-flow.md |
| protocol/SSE/continuation | references/25-protocol-sse-continuation-boundary.md |
| config/install/runtime replay | references/50-rcc-config-ssot.md |
| servertool/Stopless | references/95-v3-stopless-sop.md |
| error chain | references/96-unified-error-path-audit.md |
| selected provider model | references/96-v3-selected-provider-model-binding-sop.md |
| continuation cache | references/97-continuation-cache-compliance.md |
| provider request/error | references/98-provider-request-dryrun-and-request-error-debug.md |
Report
Report goal, owner, first divergence, changed paths, red/green evidence, mapped gates, installed runtime evidence, review result, remaining gap, and next transition. State why edited owner is unique and which adjacent layers were ruled out.
