8Dionysus/aoa-session-route-forks
.agents/skills/aoa-session-route-forks/SKILL.md
Turn reviewed session evidence into explicit next-route forks with likely gains, costs, risks, owner targets, and stop conditions so continuation stays legible instead of buried in chat memory. Use when a reviewed session ended with several plausible next moves and you need visible branch choices rather than a hidden recommendation. Do not use when there is only one obvious next move, when donor harvest still has not happened, or when the real question is final promotion of one repeated quest unit.
$ install --global
skillsauthnpx skillsauth add 8Dionysus/aoa-skills aoa-session-route-forksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 9:57 PM118.2s5 files scanned
SKILL.md
- name:
- aoa-session-route-forks
- description:
- Turn reviewed session evidence into explicit next-route forks with likely gains, costs, risks, owner targets, and stop conditions so continuation stays legible instead of buried in chat memory. Use when a reviewed session ended with several plausible next moves and you need visible branch choices rather than a hidden recommendation. Do not use when there is only one obvious next move, when donor harvest still has not happened, or when the real question is final promotion of one repeated quest unit.
- license:
- Apache-2.0
- compatibility:
- Designed for Codex or similar coding agents with repository file access and an interactive shell. Network access is optional and only needed when repository validation or referenced workflows require it.
- aoa_scope:
- core
- aoa_status:
- scaffold
- aoa_invocation_mode:
- explicit-only
- aoa_source_skill_path:
- skills/aoa-session-route-forks/SKILL.md
- aoa_source_repo:
- 8Dionysus/aoa-skills
- aoa_technique_dependencies:
- AOA-T-0078,AOA-T-0079
- aoa_portable_profile:
- codex-facing-wave-3
aoa-session-route-forks
Intent
Use this skill to author FORK_CARDS from a reviewed session.
The goal is not prediction theater. The goal is legible choice architecture: what routes exist, why each route matters, what each one likely costs, and where each route probably lands first.
Trigger boundary
Use this skill when:
- a reviewed session ended with multiple plausible next moves
- the operator or Codex needs explicit branch choices instead of a buried recommendation
- the next route may change owner repo, risk posture, or difficulty posture
- the choice may include staying manual, becoming a bounded skill, becoming a playbook automation seed candidate, or waiting for prerequisite repair
- the session needs quest-board legibility without pretending to be runtime state
Do not use this skill when:
- there is only one obvious next bounded move
- the session still needs first-pass donor harvest
- the question is final promotion of a repeated quest unit
- the route needs scenario canon immediately rather than branch analysis
Inputs
- reviewed session artifact or harvest packet
- candidate next routes
- known risks, dependencies, and blockers
- desired control mode or approval posture
- operator preference if already named
Outputs
FORK_CARDSwith likely gain, cost, risk, owner repo, and stop conditions- one suggested default route if evidence is strong enough
- one explicit hold or defer option when honest uncertainty remains
- optional automation and non-automation branches side by side when that choice is real
- optional quest hooks or campaign hints without runtime authority
- one
DECISION_FORK_RECEIPTusingreferences/stats-event-envelope.mdandreferences/decision-fork-receipt-schema.yaml - one
CORE_SKILL_APPLICATION_RECEIPTusingreferences/core-skill-application-receipt-schema.yaml
Procedure
- start from reviewed evidence rather than free speculation
- separate materially different branches instead of cosmetic variants
- name the likely first owner repo for each branch
- state likely gains, likely costs, likely risks, and stop conditions
- attach a small route passport with difficulty, risk, control mode, and delegate tier
- allow automation and non-automation branches to appear side by side when the reviewed evidence supports a real choice between them
- preserve a hold or reanchor path where uncertainty or risk remains meaningful
- emit quest-board-readable language only as adjunct reflection
- emit one
DECISION_FORK_RECEIPTwhen the fork set closes, keeping the receipt smaller than the branch cards themselves - when the finish path closes, emit one
CORE_SKILL_APPLICATION_RECEIPTthat points back to the bounded fork receipt and records one finished kernel-skill application only
Contracts
- branch cards do not become routing authority
- fork analysis must stay evidence-backed
- confidence should be named when weak
- stop conditions are first-class, not footnotes
- a fork card may recommend but must not hide alternatives
- automation-shaped branches must not be read as schedule authority
DECISION_FORK_RECEIPTis descriptive branch telemetry, not routing policyCORE_SKILL_APPLICATION_RECEIPTis generic kernel telemetry, not branch policy or route choice authority- receipt corrections use
supersedesrather than silent overwrite
Risks and anti-patterns
- fake certainty about future routes
- using fork cards as hidden routing policy
- collapsing all branches into one generic recommendation
- confusing playbook outline with branch analysis
- confusing an automation seed candidate with a live scheduler or background job
- treating quest-board cards as runtime state
- treating branch receipts as if they already chose the route
Verification
- confirm each branch differs materially
- confirm likely owner repo is named
- confirm at least one cost or risk is explicit
- confirm stop conditions exist for risky branches
- confirm hold or defer remains possible when uncertainty is real
- confirm any emitted receipt stays evidence-linked and subordinate to the fork cards
- confirm any emitted
CORE_SKILL_APPLICATION_RECEIPTpoints to the fork detail receipt and stays finish-only
Technique traceability
Manifest-backed techniques:
- AOA-T-0078 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/agent-workflows/decision-fork-cards/TECHNIQUE.mdand sections: Intent, Inputs, Outputs, Core procedure, Validation - AOA-T-0079 from
8Dionysus/aoa-techniquesat5c6f0496edc3c2e74590baa35627c85fe58ef765using pathtechniques/agent-workflows/risk-passport-lift/TECHNIQUE.mdand sections: Outputs, Contracts, Risks, Validation
Adaptation points
Project overlays may add:
- local control-mode labels
- local delegate tiers or approval classes
- repo-specific route passports
Related Skills
8Dionysus/aoa-knowledge-stewardship
development
VerifiedTrustedCommunity
Sanitize private technical material into a public-safe owner-bounded derivative, or resolve authority among authored, generated, runtime, and installed sources. Use for governed incidents, logs, configs, diagnostics, or conflicting source roles. Do not use for ordinary editing, memo/session work, direct publication, or durable-memory authority.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-session-recovery
tools
VerifiedTrustedCommunity
Diagnose a reviewed recurring session/workflow failure, or carry one bounded owner repair through checkpoint, rollback, and real health verification. Use for reviewed contamination, drift, repeated route/tool failure, or an established diagnosis ready for repair. Do not use on live evidence, for vague self-improvement, or to call a proposed or merely executed change verified.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-session-harvest
tools
VerifiedTrustedCommunity
Use only when a literal ref to a closed/reviewed session packet is supplied, to extract, classify, propose promotion or branching, or identify an automation opportunity. Missing, live, or unreviewed evidence must fail closed without inventing a ref. Natural closeout preservation belongs to aoa-memo-writeback. Do not use for generic summaries, progression, direct owner writes, scheduling, mutation, or telemetry authority.
4SKILL.mdUpdated Jul 16, 2026
8Dionysus/aoa-verification
testing
VerifiedTrustedCommunity
Turn one stable technical truth into bounded evidence through contract, coverage-audit, or property mode. Use to define a named consumer seam, audit what existing checks really constrain, or express a broad invariant after manual cases establish meaning. Compose with aoa-eval when an evaluation surface must first be found or applied. Do not use for undefined behavior, generic test plans, or green checks as whole-system proof.
4SKILL.mdUpdated Jul 16, 2026