8Dionysus
125 verified skills379 total stars
aoa-decision-create
--- name: aoa-decision-create scope: core status: evaluated summary: Create a new AoA decision record in the owning repository by using graph context for placement and repo-local decision law for the actual source note and indexes. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0033 - AOA-T-0002 --- # aoa-decision-create ## Intent Use this skill when a real structural, workflow, tooling, source/export, or authority decision needs a durable repo-local `docs/decisions/`
tools4
aoa-decision-correct
--- name: aoa-decision-correct scope: core status: evaluated summary: Correct, supersede, or reindex AoA decision records by editing source notes first, rebuilding repo-local indexes, and refreshing the workspace decision graph. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0001 - AOA-T-0033 - AOA-T-0002 --- # aoa-decision-correct ## Intent Use this skill to repair an existing decision record, its index metadata, supersession links, source-surface list, or generate
development4
aoa-decision-find
--- name: aoa-decision-find scope: core status: evaluated summary: Find AoA decision records through the workspace graph, then verify claims against repo-local source notes and generated decision indexes. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0002 --- # aoa-decision-find ## Intent Use this skill to find decision rationale quickly across AoA repositories while keeping final claims grounded in the owning repository's authored decision note. ## Trigger boundary
testing4
aoa-decision
--- name: aoa-decision scope: core status: evaluated summary: Route AoA decision-lane work through the workspace decision graph first, then hand off to the smallest find, create, or correct subskill while keeping repo-local decision files authoritative. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0033 - AOA-T-0002 --- # aoa-decision ## Intent Use this skill as the front door for AoA `docs/decisions/` work. It decides whether the task is to find, create, or correct
testing4
aoa-automation-opportunity-scan
Detect reviewed or repeated project processes that are candidates for automation, classify whether they are seed-ready, and route them to the right owner layer without granting schedule or mutation authority. Use when a reviewed session or repeated project slice reveals a recurring manual route and the honest question is whether it should stay manual, become a bounded skill, or become a playbook automation seed candidate. Do not use for one-off exploratory work, creative synthesis with no stable trigger or output, live scheduling requests, or hidden self-change.
tools3
aoa-bounded-context-map
Clarify system or domain boundaries, name contexts, and surface interfaces so changes stay semantically scoped. Use when naming is overloaded, responsibilities are mixed, or a task needs a cleaner boundary before coding. Do not use for tiny local edits or when the boundary is already clear and the real task is contract validation.
data-ai3
aoa-change-protocol
Plan and execute a bounded, non-trivial repository change with explicit verification and reporting. Use when code, config, docs, or operational surfaces change in a meaningful way and the task benefits from an explicit plan. Do not use for trivial wording fixes or when a more specific risk skill fits better.
development3
aoa-checkpoint-closeout-bridge
Bridge provisional checkpoint evidence into one explicit reviewed closeout execution chain without turning notes into final harvest, progression, or quest authority. Use when a reviewed session artifact exists, checkpoint notes or closeout handoffs already carry focus hints, and the next honest move is to reread the reviewed artifact while driving donor harvest, progression lift, and quest harvest in that fixed order. Do not use for mid-session collection only, for hidden execution inside `aoa closeout run`, or when the request tries to mint final verdicts from checkpoint notes without reviewed evidence.
testing3
aoa-invariant-coverage-audit
Audit whether existing tests and checks actually constrain the stable invariants that matter. Use when you need to judge if current coverage proves a rule or only repeats examples, and you want the smallest bounded follow-up gaps. Do not use when the invariant itself is still undefined or when the real task is to author new invariants rather than audit coverage.
testing3
aoa-property-invariants
Express stable system or domain truths as invariant-oriented tests or checks rather than only fixed examples. Use when correctness depends on behavior that should hold across many inputs or states, such as monotonicity, idempotency, conservation, or structural rules. Do not use when no meaningful invariant is known yet or when the real task is auditing existing coverage instead of writing the properties.
testing3
aoa-quest-harvest
Give the final promotion verdict on one repeated reviewed quest-shaped unit without collapsing skills, playbooks, orchestrator classes, proof, or memory into one layer. Use when a bounded quest-shaped work pattern has repeated, reviewed evidence exists, and you need the final honest verdict on whether it should stay a quest or move into the next owner surface. Do not use when the route is still active, only one anecdotal occurrence exists, the task is to invent net-new doctrine, or a broader reviewed session artifact still needs donor harvest, route forks, diagnosis, repair, or progression reflection first.
documentation3
aoa-safe-infra-change
Make bounded infrastructure, configuration, service, or operational changes with explicit risk framing, proportional verification, and rollback thinking. Use when a change has runtime or deployment implications and needs stronger discipline than a normal code edit. Do not use for purely local code changes, or when the main need is approval classification or preview-first execution.
development3
aoa-session-route-forks
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.
testing3
aoa-source-of-truth-check
Clarify which files are authoritative for repository guidance, operational instructions, architecture, and status, and keep entrypoint docs short and link-driven once canonical homes exist. Use when docs overlap, conflict, or confuse contributors about which file to trust. Do not use for purely code-local tasks or when authoritative files are already clear and the main need is decision rationale.
development3
aoa-tdd-slice
Implement a bounded feature slice through test-first discipline, minimal implementation, and explicit refactor boundaries. Use when a behavior change can be specified in tests before code and confidence or regression resistance matters. Do not use for undefined exploratory work, one-off glue, or broader architectural restructuring.
development3
aoa-adr-write
Capture a meaningful architectural or workflow decision as an ADR or decision note, place it in the canonical decision surface, and verify the rationale stays discoverable. Use when structure, boundaries, tooling, or workflow expectations change and future contributors need to know why. Do not use for tiny self-evident edits or when the real problem is source-of-truth ambiguity rather than decision rationale.
tools3
aoa-core-logic-boundary
Separate reusable core logic from glue, orchestration, and infrastructure detail. Use when stable rules are mixed with wiring, the same logic repeats in several places, or reviews are muddy because the responsibility center is unclear. Do not use for tiny isolated fixes or when the real task is introducing a port or adapter around a concrete dependency.
testing3
aoa-local-stack-bringup
Bring up a bounded local multi-service stack by rendering runtime truth, checking selector-aware host readiness, and launching through one explicit lifecycle entrypoint with a visible stop path. Use when profiles, presets, or overlays can change what starts and host readiness must be reviewed before launch. Do not use for remote deployment, pure diagnostics without launch intent, or generic infra-change work.
testing3
aoa-session-self-diagnose
Classify drift, friction, proof gaps, ownership confusion, and repeated failure patterns from a reviewed session into a bounded diagnosis packet without mutating anything yet. Use when the next honest move is diagnosis before repair and the reviewed material points to repeated contradictions, blockers, or boundary blur. Do not use for live sessions, for issues that are already fully diagnosed, or when the real task is final quest-promotion triage.
data-ai3
atm10-source-of-truth-check
Apply the aoa-source-of-truth-check workflow inside an atm10-* repository using repo-relative document maps, canonical-file patterns, and local review posture. Use when contributors need a thin project overlay to identify authoritative docs inside an atm10-* repo. Do not use when the task is broader policy design, purely code-local, or better handled by the base skill without local adaptation.
development3
abyss-sanitized-share
--- name: abyss-sanitized-share scope: project status: evaluated summary: Thin abyss overlay for turning raw repo-local technical material into a shareable public-safe surface with explicit local thresholds and canonical placement notes. invocation_mode: explicit-only technique_dependencies: - AOA-T-0034 - AOA-T-0002 --- # abyss-sanitized-share ## Intent Use this skill to adapt `aoa-sanitized-share` to an `abyss-*` repository when the base sanitization workflow is right but the local repo
testing3
aoa-adr-write
--- name: aoa-adr-write scope: core status: canonical summary: Record a meaningful architectural or workflow decision, place it in the canonical note surface, and verify that future readers can find the rationale rather than only the outcome. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0033 - AOA-T-0002 --- # aoa-adr-write ## Intent Use this skill to capture an architectural, structural, or workflow decision in a concise reviewable note, then place and verify that
testing3
aoa-session-self-repair
--- name: aoa-session-self-repair scope: core status: scaffold summary: Turn a reviewed diagnosis packet into the smallest honest repair packet with checkpoint posture, rollback markers, health checks, and explicit owner-layer targets instead of silent self-mutation. invocation_mode: explicit-only technique_dependencies: - AOA-T-0082 - AOA-T-0083 --- # aoa-session-self-repair ## Intent Use this skill to author a bounded `REPAIR_PACKET`. The repair packet should be small, explicit, revers
testing3
aoa-invariant-coverage-audit
--- name: aoa-invariant-coverage-audit scope: core status: canonical summary: Audit whether existing tests or checks actually cover the stable invariants that matter, and identify the smallest bounded gaps that still leave example-only coverage too thin. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0017 --- # aoa-invariant-coverage-audit ## Intent Use invariant-oriented coverage to judge whether an existing validation surface really constrains the stable truth, and tu
testing3
abyss-safe-infra-change
--- name: abyss-safe-infra-change scope: project status: evaluated summary: Thin abyss overlay for bounded infrastructure or configuration changes with repo-relative operational surfaces, explicit local authority, and reviewable risk notes. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 - AOA-T-0001 --- # abyss-safe-infra-change ## Intent Use this skill to adapt `aoa-safe-infra-change` to an `abyss-*` repository when the base operational workflow is correct but the lo
testing3
aoa-approval-gate-check
--- name: aoa-approval-gate-check scope: risk status: canonical summary: Classify whether a requested action should proceed, wait for explicit approval, or be refused at the current authority level. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 --- # aoa-approval-gate-check ## Intent Use this skill to classify whether a requested action crosses an approval boundary and to return a bounded next step that keeps authority explicit before any execution proceeds. ## Trigge
testing3
aoa-checkpoint-closeout-bridge
--- name: aoa-checkpoint-closeout-bridge scope: core status: scaffold summary: Bridge local checkpoint evidence into one reviewed closeout execution chain without turning provisional notes into final harvest, progression, or quest authority. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0075 - AOA-T-0084 - AOA-T-0089 --- # aoa-checkpoint-closeout-bridge ## Intent Use this skill to connect checkpoint-led session growth with explicit reviewed closeout execution. It
testing3
aoa-commit-growth-seam
--- name: aoa-commit-growth-seam scope: core status: scaffold summary: Turn a validated bounded diff into one intentional local commit with explicit scope review, named verification carry-forward, and a visible stop line before push or publish. invocation_mode: explicit-only technique_dependencies: - AOA-T-0001 - AOA-T-0028 --- # aoa-commit-growth-seam ## Intent Use this skill to cross one honest local commit boundary after a bounded change is already prepared and reviewed enough to stop
testing3
aoa-contract-test
--- name: aoa-contract-test scope: core status: canonical summary: Design or extend contract-oriented validation at module, service, or workflow boundaries. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0003 - AOA-T-0015 --- # aoa-contract-test ## Intent Strengthen boundary reliability by making expected inputs, outputs, and validation summaries explicit. ## Trigger boundary Use this skill when: - two modules or services interact across a meaningful boundary - a sm
testing3
aoa-core-logic-boundary
--- name: aoa-core-logic-boundary scope: core status: evaluated summary: Clarify which logic belongs in the reusable core and which parts should remain glue, orchestration, or infrastructure detail. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0016 - AOA-T-0015 --- # aoa-core-logic-boundary ## Intent Use this skill to separate reusable core logic from surrounding glue, orchestration, or infrastructure detail so future changes land in the right place. ## Trigger bou
testing3
aoa-dry-run-first
--- name: aoa-dry-run-first scope: risk status: canonical summary: Prefer simulation, inspection, or preview paths before real execution, and require one explicit confirmation seam before any mutating step runs. invocation_mode: explicit-only technique_dependencies: - AOA-T-0004 - AOA-T-0028 --- # aoa-dry-run-first ## Intent Use this skill to run a preview-first workflow that stops at inspection until one concrete mutation is ready, then asks for a visible confirmation before the real act
testing3
aoa-port-adapter-refactor
--- name: aoa-port-adapter-refactor scope: core status: evaluated summary: Refactor code toward clearer ports and adapters so reusable logic is less entangled with infrastructure details. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0016 - AOA-T-0015 --- # aoa-port-adapter-refactor ## Intent Use this skill to separate domain or application logic from concrete infrastructure details by introducing or clarifying ports and adapters. ## Trigger boundary Use this skill
development3
aoa-quest-harvest
--- name: aoa-quest-harvest scope: core status: scaffold summary: Triage repeated reviewed quest evidence into the right promotion target without confusing skills, playbooks, orchestrator classes, proof, or memory. invocation_mode: explicit-only technique_dependencies: - AOA-T-0089 - AOA-T-0090 --- # aoa-quest-harvest ## Intent Use this skill to decide whether a repeated, reviewed quest-shaped pattern should remain a quest or be promoted into the next honest owner surface. ## Trigger bou
testing3
aoa-safe-infra-change
--- name: aoa-safe-infra-change scope: risk status: canonical summary: Make bounded infrastructure or configuration changes with explicit risk framing, verification, and reversible execution discipline. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 - AOA-T-0001 --- # aoa-safe-infra-change ## Intent Use this skill to shape infrastructure, service, configuration, or operational changes into a safer bounded workflow. ## Trigger boundary Use this skill when: - the task
testing3
aoa-session-donor-harvest
--- name: aoa-session-donor-harvest scope: core status: scaffold summary: Harvest reusable donor units from a reviewed session into a bounded HARVEST_PACKET, route each unit to the right AoA owner layer, and hand off to the next honest post-session skill when needed. invocation_mode: explicit-only technique_dependencies: - AOA-T-0075 - AOA-T-0076 - AOA-T-0077 --- # aoa-session-donor-harvest ## Intent Use this skill to metabolize a reviewed session artifact into a bounded `HARVEST_PACKET
testing3
aoa-session-progression-lift
--- name: aoa-session-progression-lift scope: core status: scaffold summary: Lift reviewed session evidence into a multi-axis progression delta with bounded unlock hints, quest reflection cues, and no fake single-score authority. invocation_mode: explicit-only technique_dependencies: - AOA-T-0084 - AOA-T-0085 --- # aoa-session-progression-lift ## Intent Use this skill to author a `PROGRESSION_DELTA` from reviewed evidence. This is not score inflation. It is an evidence-backed overlay tha
testing3
aoa-session-route-forks
--- name: aoa-session-route-forks scope: core status: scaffold summary: 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. invocation_mode: explicit-only technique_dependencies: - AOA-T-0078 - AOA-T-0079 --- # aoa-session-route-forks ## Intent Use this skill to author `FORK_CARDS` from a reviewed session. The goal is not prediction theater. The go
development3
aoa-session-self-diagnose
--- name: aoa-session-self-diagnose scope: core status: scaffold summary: Classify drift, friction, proof gaps, ownership confusion, and repeated failure patterns from a reviewed session into a bounded diagnosis packet without mutating anything yet. invocation_mode: explicit-only technique_dependencies: - AOA-T-0080 - AOA-T-0081 --- # aoa-session-self-diagnose ## Intent Use this skill to turn a reviewed session into a `DIAGNOSIS_PACKET`. It should answer: what drifted, what hurt, what bo
testing3
aoa-summon
--- name: aoa-summon scope: core status: scaffold summary: Delegate one bounded child route through quest-passport law, Codex-first local execution defaults, progression and self-agent gates, governed return, and checkpoint-aware reviewed closeout planning. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-SUMMON-LANE-SELECTION - AOA-T-PENDING-SUMMON-RETURN-GOVERNANCE --- # aoa-summon ## Intent Use this skill to decide whether and how to launch one bounded child route
development3
aoa-tdd-slice
--- name: aoa-tdd-slice scope: core status: canonical summary: Implement a bounded feature slice through test-first discipline, minimal implementation, and explicit refactor boundaries. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0014 - AOA-T-0001 --- # aoa-tdd-slice ## Intent Use test-first discipline to implement a small feature slice with a clear behavioral target and explicit verification. ## Trigger boundary Use this skill when: - a behavior change can be ex
development3
titan-approval-ledger
--- name: titan-approval-ledger scope: project status: scaffold summary: Record explicit operator approval for Forge mutation or Delta judgment gates without treating approval records as owner truth. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-approval-ledger ## Intent Use this skill to record an explicit Titan approval decision for a bounded Forge mutation or Delta judgment gate. ## Trigge
testing3
titan-approval-loom
--- name: titan-approval-loom scope: project status: scaffold summary: Maintain the app-server bridge approval queue while preserving Forge and Delta gates, receipts, and visible operator intent. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-approval-loom ## Intent Use this skill to inspect, add, or resolve approval-queue items for the Titan app-server bridge. ## Trigger boundary Use this sk
testing3
titan-appserver-bridge
--- name: titan-appserver-bridge scope: project status: scaffold summary: Operate the Titan app-server bridge as inspectable thread, turn, event, approval, replay, and metrics state without hidden execution. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-appserver-bridge ## Intent Use this skill to prepare or inspect the Titan app-server bridge while keeping Codex execution visible and gated.
development3
titan-appserver-plan
--- name: titan-appserver-plan scope: project status: scaffold summary: Generate an inspectable Titan app-server launch plan as JSONL or equivalent plan output without executing Codex. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-appserver-plan ## Intent Use this skill to produce a launch plan for a Titan app-server route while leaving execution to a later explicit operator action. ## Trigge
development3
titan-closeout
--- name: titan-closeout scope: project status: scaffold summary: Close a Titan service-cohort session with role, risk, provenance, gate, verification, and next-owner summary. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-closeout ## Intent Use this skill at the end of a Titan service-cohort session to close the local receipt without claiming final owner truth. ## Trigger boundary Use this s
testing3
titan-console
--- name: titan-console scope: project status: scaffold summary: Open or maintain a visible Titan operator-console state while keeping Forge and Delta locked until approvals exist. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-console ## Intent Use this skill to create, inspect, or update an operator-visible Titan console state. ## Trigger boundary Use this skill when: - the operator wants a
testing3
titan-event-replay
--- name: titan-event-replay scope: project status: scaffold summary: Replay Titan bridge or console events into inspectable state without granting runtime authority to the replay result. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-event-replay ## Intent Use this skill to replay Titan event logs and compare the resulting state to current bridge or console state. ## Trigger boundary Use thi
testing3
titan-memory-prune
--- name: titan-memory-prune scope: project status: scaffold summary: Propose redaction, tombstone, or pruning candidates for Titan memory without silent deletion or canon rewrite. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-memory-prune ## Intent Use this skill to review Titan memory records for retention, masking, tombstone, or pruning proposals. ## Trigger boundary Use this skill when:
testing3
titan-runtime-gate
--- name: titan-runtime-gate scope: project status: scaffold summary: Activate Forge mutation or Delta judgment lanes only through matching explicit runtime gates on a Titan receipt. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-runtime-gate ## Intent Use this skill when a Titan session needs to activate Forge or Delta from locked to gated state. ## Trigger boundary Use this skill when: - Fo
testing3
atm10-change-protocol
--- name: atm10-change-protocol scope: project status: evaluated summary: Thin atm10 overlay for bounded change execution with repo-relative paths, commands, review checklists, and explicit local approval notes. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0001 - AOA-T-0002 --- # atm10-change-protocol ## Intent Use this skill to adapt `aoa-change-protocol` to an `atm10-*` repository without changing the base workflow meaning. ## Trigger boundary Use this skill whe
testing3
titan-receipt
--- name: titan-receipt scope: project status: scaffold summary: Create, validate, note, or close Titan session receipts as witnesses rather than final truth. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-receipt ## Intent Use this skill to manage local Titan session receipts for summon, gate, note, validation, and closeout steps. ## Trigger boundary Use this skill when: - a Titan session ne
testing3
aoa-automation-opportunity-scan
--- name: aoa-automation-opportunity-scan scope: core status: evaluated summary: Detect reviewed or repeated project processes that are candidates for automation, classify whether they are seed-ready, name the highest honest automation mode, and route them without granting schedule or mutation authority. invocation_mode: explicit-only technique_dependencies: - AOA-T-0086 - AOA-T-0087 - AOA-T-0088 --- # aoa-automation-opportunity-scan ## Intent Use this skill to detect where repeated pro
tools3
titan-memory-prune
--- name: titan-memory-prune scope: project status: scaffold summary: Propose redaction, tombstone, or pruning candidates for Titan memory without silent deletion or canon rewrite. invocation_mode: explicit-only technique_dependencies: - AOA-T-0103 - AOA-T-0104 - AOA-T-0043 --- # titan-memory-prune ## Intent Use this skill to review Titan memory records for retention, masking, tombstone, or pruning proposals. ## Trigger boundary Use this skill when: - a Titan memory record may be stal
testing3
aoa-session-progression-lift
Lift reviewed session evidence into a bounded multi-axis progression delta with explicit unlock hints, quest reflection cues, and no fake single-score authority. Use when a reviewed session produced meaningful mastery evidence and you need progression legibility without mutating source role profiles or routing authority. Do not use when there is no reviewed evidence, when the request wants one universal power number, or when progression language is being used as hidden policy.
testing3
aoa-adr-write
--- name: aoa-adr-write scope: core status: canonical summary: Record a meaningful architectural or workflow decision, place it in the canonical note surface, and verify that future readers can find the rationale without confusing it with the evidence that revealed it. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0033 - AOA-T-0002 --- # aoa-adr-write ## Intent Use this skill to capture an architectural, structural, or workflow decision in a concise reviewable note,
testing3
aoa-sanitized-share
Turn raw technical material into a shareable public-safe artifact while keeping the raw source separate, placing the sanitized result in the canonical sharing surface, and preserving the lesson after redaction. Use when logs, configs, diagnostics, or reports may contain secrets, topology, or internal identifiers. Do not use when the material is already clearly public-safe or when the task is to perform the underlying operational change.
testing3
abyss-self-diagnostic-spine
--- name: abyss-self-diagnostic-spine scope: project status: scaffold summary: Thin abyss overlay for turning runtime-body evidence plus optional reviewed session references into one bounded diagnostic session artifact and an honest next-move class without granting silent self-mutation. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0080 - AOA-T-0081 --- # abyss-self-diagnostic-spine ## Intent Use this skill to adapt `aoa-session-self-diagnose` to an `abyss-*` reposit
testing3
aoa-quest-harvest
--- name: aoa-quest-harvest scope: core status: evaluated summary: Triage one isolated repeated reviewed quest unit with explicit repeat evidence posture into the right promotion target without confusing skills, playbooks, orchestrator classes, proof, memory, or downstream acceptance. invocation_mode: explicit-only technique_dependencies: - AOA-T-0089 - AOA-T-0090 --- # aoa-quest-harvest ## Intent Use this skill to decide whether one repeated, reviewed quest-shaped unit should remain a qu
testing3
aoa-checkpoint-closeout-bridge
--- name: aoa-checkpoint-closeout-bridge scope: core status: evaluated summary: Bridge local checkpoint focus hints into one reviewed closeout execution chain without turning provisional notes, mechanical reports, or skipped stages into final harvest, progression, or quest authority. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0075 - AOA-T-0084 - AOA-T-0089 --- # aoa-checkpoint-closeout-bridge ## Intent Use this skill to connect checkpoint-led session growth with
testing3
abyss-safe-infra-change
--- name: abyss-safe-infra-change scope: project status: evaluated summary: Thin abyss overlay for bounded infrastructure or configuration changes with repo-relative operational surfaces, explicit local authority, and reviewable risk notes. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 - AOA-T-0001 --- # abyss-safe-infra-change ## Intent Use this skill to adapt `aoa-safe-infra-change` to an `abyss-*` repository when the base operational workflow is correct but the lo
testing3
aoa-summon
--- name: aoa-summon scope: core status: evaluated summary: Delegate one bounded child route through quest-passport law, local coding-agent execution defaults, progression and self-agent gates, governed return, and checkpoint-aware reviewed closeout planning. invocation_mode: explicit-only technique_dependencies: - AOA-T-0078 - AOA-T-0079 - AOA-T-0062 - AOA-T-0058 --- # aoa-summon ## Intent Use this skill to decide whether and how to launch one bounded child route from an already-anch
development3
titan-approval-loom
--- name: titan-approval-loom scope: project status: scaffold summary: Maintain the app-server bridge approval queue while preserving Forge and Delta gates, receipts, and visible operator intent. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 - AOA-T-0045 - AOA-T-0062 --- # titan-approval-loom ## Intent Use this skill to inspect, add, or resolve approval-queue items for the Titan app-server bridge. ## Trigger boundary Use this skill when: - a bridge turn contains
testing3
abyss-sanitized-share
--- name: abyss-sanitized-share scope: project status: evaluated summary: Thin abyss overlay for turning raw repo-local technical material into a shareable public-safe surface with explicit local thresholds and canonical placement notes. invocation_mode: explicit-only technique_dependencies: - AOA-T-0034 - AOA-T-0002 --- # abyss-sanitized-share ## Intent Use this skill to adapt `aoa-sanitized-share` to an `abyss-*` repository when the base sanitization workflow is right but the local repo
testing3
titan-approval-ledger
--- name: titan-approval-ledger scope: project status: scaffold summary: Record explicit operator approval for Forge mutation or Delta judgment gates without treating approval records as owner truth. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 - AOA-T-0045 - AOA-T-0058 --- # titan-approval-ledger ## Intent Use this skill to record an explicit Titan approval decision for a bounded Forge mutation or Delta judgment gate. ## Trigger boundary Use this skill when: -
testing3
titan-appserver-bridge
--- name: titan-appserver-bridge scope: project status: scaffold summary: Operate the Titan app-server bridge as inspectable thread, turn, event, approval, replay, and metrics state without hidden execution. invocation_mode: explicit-only technique_dependencies: - AOA-T-0045 - AOA-T-0066 - AOA-T-0043 --- # titan-appserver-bridge ## Intent Use this skill to prepare or inspect the Titan app-server bridge while keeping local agent execution visible and gated. ## Trigger boundary Use this
testing3
titan-summon
--- name: titan-summon scope: project status: scaffold summary: Begin an explicit Titan service-cohort session with Atlas, Sentinel, and Mneme active and Forge or Delta locked. invocation_mode: explicit-only technique_dependencies: - AOA-T-0060 - AOA-T-0058 - AOA-T-0028 --- # titan-summon ## Intent Use this skill to begin a local coding-agent session with the first Titan service cohort after an explicit operator summon. ## Trigger boundary Use this skill when: - the operator explicitl
testing3
titan-recall
--- name: titan-recall scope: project status: scaffold summary: Retrieve Titan candidate memory records with source, record id, authority note, confidence, and verification path. invocation_mode: explicit-only technique_dependencies: - AOA-T-0053 - AOA-T-0043 - AOA-T-0045 --- # titan-recall ## Intent Use this skill to retrieve and present Titan remembrance records without treating recall as source truth. ## Trigger boundary Use this skill when: - a user asks what a Titan remembers - a
testing3
titan-memory-loom
--- name: titan-memory-loom scope: project status: scaffold summary: Initialize or update Titan Memory Loom records as candidate memory with source refs, confidence, and authority warnings. invocation_mode: explicit-only technique_dependencies: - AOA-T-0053 - AOA-T-0043 - AOA-T-0045 --- # titan-memory-loom ## Intent Use this skill to ingest Titan receipts or events into candidate-grade remembrance records. ## Trigger boundary Use this skill when: - a Titan receipt or event should beco
testing3
titan-mutation-gate
--- name: titan-mutation-gate scope: project status: scaffold summary: Gate Forge workspace-write work with explicit intent, target paths, prechecks, validation, and rollback or stop posture. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 - AOA-T-0004 - AOA-T-0091 --- # titan-mutation-gate ## Intent Use this skill before Forge performs any workspace-write or code mutation work. ## Trigger boundary Use this skill when: - Forge is being asked to edit files - the mut
development3
titan-runtime-gate
--- name: titan-runtime-gate scope: project status: scaffold summary: Activate Forge mutation or Delta judgment lanes only through matching explicit runtime gates on a Titan receipt. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 - AOA-T-0058 - AOA-T-0091 --- # titan-runtime-gate ## Intent Use this skill when a Titan session needs to activate Forge or Delta from locked to gated state. ## Trigger boundary Use this skill when: - Forge needs a mutation gate - Delta n
testing3
titan-thread-turn-binding
--- name: titan-thread-turn-binding scope: project status: scaffold summary: Bind Titan bridge events, approvals, and replay state to explicit thread and turn ids for inspectable continuity. invocation_mode: explicit-only technique_dependencies: - AOA-T-0062 - AOA-T-0066 - AOA-T-0045 --- # titan-thread-turn-binding ## Intent Use this skill to attach Titan bridge events and approvals to a specific thread and turn boundary. ## Trigger boundary Use this skill when: - events need a thread
testing3
titan-appserver-plan
--- name: titan-appserver-plan scope: project status: scaffold summary: Generate an inspectable Titan app-server launch plan as JSONL or equivalent plan output without starting hidden agent execution. invocation_mode: explicit-only technique_dependencies: - AOA-T-0004 - AOA-T-0091 - AOA-T-0045 --- # titan-appserver-plan ## Intent Use this skill to produce a launch plan for a Titan app-server route while leaving execution to a later explicit operator action. ## Trigger boundary Use thi
testing3
titan-event-replay
--- name: titan-event-replay scope: project status: scaffold summary: Replay Titan bridge or console events into inspectable state without granting runtime authority to the replay result. invocation_mode: explicit-only technique_dependencies: - AOA-T-0066 - AOA-T-0045 - AOA-T-0043 --- # titan-event-replay ## Intent Use this skill to replay Titan event logs and compare the resulting state to current bridge or console state. ## Trigger boundary Use this skill when: - bridge state must b
testing3
titan-console
--- name: titan-console scope: project status: scaffold summary: Open or maintain a visible Titan operator-console state while keeping Forge and Delta locked until approvals exist. invocation_mode: explicit-only technique_dependencies: - AOA-T-0045 - AOA-T-0062 - AOA-T-0028 --- # titan-console ## Intent Use this skill to create, inspect, or update an operator-visible Titan console state. ## Trigger boundary Use this skill when: - the operator wants a visible Titan lane dashboard - con
testing3
titan-closeout
--- name: titan-closeout scope: project status: scaffold summary: Close a Titan service-cohort session with role, risk, provenance, gate, verification, and next-owner summary. invocation_mode: explicit-only technique_dependencies: - AOA-T-0058 - AOA-T-0076 - AOA-T-0045 --- # titan-closeout ## Intent Use this skill at the end of a Titan service-cohort session to close the local receipt without claiming final owner truth. ## Trigger boundary Use this skill when: - a Titan receipt is rea
testing3
aoa-safe-infra-change
--- name: aoa-safe-infra-change scope: risk status: canonical summary: Make bounded infrastructure or configuration changes with explicit risk framing, verification, and reversible execution discipline. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 - AOA-T-0001 --- # aoa-safe-infra-change ## Intent Use this skill to shape infrastructure, service, configuration, or operational changes into a safer bounded workflow. ## Trigger boundary Use this skill when: - the task
testing3
aoa-local-stack-bringup
--- name: aoa-local-stack-bringup scope: risk status: evaluated summary: Bring up a bounded local multi-service stack by reviewing rendered runtime truth, checking host readiness, and launching through one explicit lifecycle entrypoint. invocation_mode: explicit-only technique_dependencies: - AOA-T-0036 - AOA-T-0037 - AOA-T-0028 - AOA-T-0038 --- # aoa-local-stack-bringup ## Intent Use this skill to turn local multi-service startup into a reviewable bring-up workflow with a visible pre
testing3
aoa-commit-growth-seam
--- name: aoa-commit-growth-seam scope: core status: evaluated summary: Turn a validated bounded diff into one authorized local commit with explicit scope review, named verification carry-forward, and a visible stop line before push or publish. invocation_mode: explicit-only technique_dependencies: - AOA-T-0001 - AOA-T-0028 --- # aoa-commit-growth-seam ## Intent Use this skill to cross one honest local commit boundary after a bounded change is already prepared and reviewed enough to stop
testing3
aoa-port-adapter-refactor
--- name: aoa-port-adapter-refactor scope: core status: evaluated summary: Refactor code, builders, tools, or workflow implementations toward clearer ports and adapters so reusable logic is less entangled with concrete dependencies or runtime details. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0016 - AOA-T-0015 --- # aoa-port-adapter-refactor ## Intent Use this skill to separate reusable domain, application, builder, or workflow logic from concrete dependencies an
tools3
aoa-change-protocol
--- name: aoa-change-protocol scope: core status: canonical summary: Bounded workflow for Codex to read the owner route, plan a scoped change, verify it explicitly, and report it clearly. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0001 - AOA-T-0002 --- # aoa-change-protocol ## Intent Ground non-trivial changes in the owner route before editing, then keep the diff reviewable and explicitly verified without hidden scope expansion. ## Trigger boundary Use this skil
development3
aoa-source-of-truth-check
--- name: aoa-source-of-truth-check scope: core status: canonical summary: Check whether repository guidance, canonical docs, active surfaces, legacy/provenance bridges, and operational instructions have clear ownership, then keep entrypoints short once canonical homes exist. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0013 - AOA-T-0002 - AOA-T-0009 --- # aoa-source-of-truth-check ## Intent Use this skill to clarify which files are authoritative for status, archi
testing3
aoa-bounded-context-map
--- name: aoa-bounded-context-map scope: core status: canonical summary: Clarify system, domain, layer, and owner boundaries so changes stay semantically scoped, interface-aware, and portable where needed. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0016 - AOA-T-0002 --- # aoa-bounded-context-map ## Intent Use bounded-context thinking to reduce semantic drift, mixed responsibilities, and unclear interfaces. ## Trigger boundary Use this skill when: - a project mix
testing3
aoa-memo-writeback
--- name: aoa-memo-writeback scope: core status: scaffold summary: Turn session evidence, landed-work context, and owner routes into one explicit memo writeback decision, local memo candidate, export packet, or no-writeback stop line without treating session history as reviewed memory. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0026 - AOA-T-0106 - AOA-T-0076 --- # aoa-memo-writeback ## Intent Use this skill to decide whether a live session, closeout, landed chan
testing3
titan-summon
--- name: titan-summon scope: project status: scaffold summary: Begin an explicit Titan service-cohort session with Atlas, Sentinel, and Mneme active and Forge or Delta locked. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-summon ## Intent Use this skill to begin a Codex session with the first Titan service cohort after an explicit operator summon. ## Trigger boundary Use this skill when: -
development3
titan-thread-turn-binding
--- name: titan-thread-turn-binding scope: project status: scaffold summary: Bind Titan bridge events, approvals, and replay state to explicit thread and turn ids for inspectable continuity. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-thread-turn-binding ## Intent Use this skill to attach Titan bridge events and approvals to a specific thread and turn boundary. ## Trigger boundary Use this
testing3
titan-recall
--- name: titan-recall scope: project status: scaffold summary: Retrieve Titan candidate memory records with source, record id, authority note, confidence, and verification path. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-recall ## Intent Use this skill to retrieve and present Titan remembrance records without treating recall as source truth. ## Trigger boundary Use this skill when: - a u
testing3
titan-mutation-gate
--- name: titan-mutation-gate scope: project status: scaffold summary: Gate Forge workspace-write work with explicit intent, target paths, prechecks, validation, and rollback or stop posture. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-mutation-gate ## Intent Use this skill before Forge performs any workspace-write or code mutation work. ## Trigger boundary Use this skill when: - Forge is
development3
titan-memory-loom
--- name: titan-memory-loom scope: project status: scaffold summary: Initialize or update Titan Memory Loom records as candidate memory with source refs, confidence, and authority warnings. invocation_mode: explicit-only technique_dependencies: - AOA-T-PENDING-TITAN-GATE-DISCIPLINE - AOA-T-PENDING-TITAN-RECEIPT-LINEAGE --- # titan-memory-loom ## Intent Use this skill to ingest Titan receipts or events into candidate-grade remembrance records. ## Trigger boundary Use this skill when: - a
testing3
aoa-session-route-forks
--- name: aoa-session-route-forks scope: core status: evaluated summary: 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. invocation_mode: explicit-only technique_dependencies: - AOA-T-0078 - AOA-T-0079 --- # aoa-session-route-forks ## Intent Use this skill to author `FORK_CARDS` from a reviewed session. The goal is not prediction theater. The g
development3
aoa-session-self-repair
--- name: aoa-session-self-repair scope: core status: evaluated summary: Turn a reviewed diagnosis packet into the smallest honest repair packet with checkpoint posture, execution posture, rollback markers, health checks, and explicit owner-layer targets instead of silent self-mutation. invocation_mode: explicit-only technique_dependencies: - AOA-T-0082 - AOA-T-0083 --- # aoa-session-self-repair ## Intent Use this skill to author a bounded `REPAIR_PACKET`. The repair packet should be sma
testing3
aoa-core-logic-boundary
--- name: aoa-core-logic-boundary scope: core status: evaluated summary: Separate reusable rules, mappings, and decision logic from glue, orchestration, projection, infrastructure, and presentation detail. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0016 - AOA-T-0015 --- # aoa-core-logic-boundary ## Intent Use this skill to separate a stable reusable center from surrounding glue, orchestration, projection, infrastructure, or presentation detail so future changes la
testing3
aoa-contract-test
--- name: aoa-contract-test scope: core status: canonical summary: Design or extend contract-oriented validation across stable module, service, schema, generated/export, workflow, or repo handoff boundaries. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0003 - AOA-T-0015 --- # aoa-contract-test ## Intent Strengthen boundary reliability by making stable producer-consumer expectations, validation surfaces, and claim limits explicit. ## Trigger boundary Use this skill
testing3
aoa-invariant-coverage-audit
--- name: aoa-invariant-coverage-audit scope: core status: canonical summary: Audit whether existing validation or proof surfaces actually cover the stable invariants that matter, and identify the smallest bounded gaps that still leave example-only coverage too thin. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0017 --- # aoa-invariant-coverage-audit ## Intent Use invariant-oriented coverage to judge whether an existing validation or proof surface really constrains th
testing3
aoa-session-progression-lift
--- name: aoa-session-progression-lift scope: core status: evaluated summary: Lift reviewed session evidence into a multi-axis progression delta with baseline posture, per-axis evidence posture, bounded unlock hints, quest reflection cues, and no fake single-score or checkpoint-hint authority. invocation_mode: explicit-only technique_dependencies: - AOA-T-0084 - AOA-T-0085 --- # aoa-session-progression-lift ## Intent Use this skill to author a `PROGRESSION_DELTA` from reviewed evidence.
testing3
aoa-property-invariants
--- name: aoa-property-invariants scope: core status: canonical summary: Express stable behavior, structural, lifecycle, generated/export, workflow, or domain truths as invariant-oriented tests and checks rather than only enumerating examples. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0017 - AOA-T-0007 --- # aoa-property-invariants ## Intent Use invariant-oriented thinking to test broad behavior and stable artifact relationships through properties rather than onl
testing3
titan-receipt
--- name: titan-receipt scope: project status: scaffold summary: Create, validate, note, or close Titan session receipts as witnesses rather than final truth. invocation_mode: explicit-only technique_dependencies: - AOA-T-0058 - AOA-T-0045 - AOA-T-0043 --- # titan-receipt ## Intent Use this skill to manage local Titan session receipts for summon, gate, note, validation, and closeout steps. ## Trigger boundary Use this skill when: - a Titan session needs a receipt - an existing receipt
testing3
aoa-approval-gate-check
Classify whether a requested action is safe to proceed, requires explicit approval, or should not be executed. Use when a task may be destructive, security-sensitive, or operationally sensitive and the authority boundary is unclear. Do not use for clearly low-risk work or when the main need is previewing a mutation rather than deciding whether it may proceed.
testing3
aoa-commit-growth-seam
Turn a validated bounded diff into one intentional local commit with explicit scope review, named verification carry-forward, and a visible stop line before push or publish. Use when a bounded code, config, or docs diff is already prepared locally and the next honest move is one local commit boundary rather than more coding. Do not use when the task still needs more repair or verification, when no bounded diff exists, or when the main task is push, PR, release, or public-share.
development3
aoa-contract-test
Design or extend contract-oriented validation at module, service, or workflow boundaries. Use when two components interact across a meaningful interface, downstream assumptions matter, or a smoke path needs an explicit contract. Do not use for purely local changes or when the real need is invariant or property testing instead of boundary validation.
testing3
aoa-dry-run-first
Prefer simulation, preview, or inspect-only paths before any real mutation, then require one explicit confirmation for the concrete mutating step. Use when the action can be previewed and mistakes would be costly, such as delete, restore, migrate, or reconfigure operations. Do not use for purely analytical tasks or when the primary question is whether execution is authorized at all.
testing3
aoa-session-donor-harvest
Turn a reviewed session artifact into a bounded HARVEST_PACKET, route each reusable unit to the right AoA owner layer, and hand off to the next honest post-session skill when needed. Use when the source is a reviewed session transcript, compaction note, or recap and the real question is what should survive this session rather than merely what happened. Do not use for active or unreviewed sessions, raw session capture or indexing work, or when the only remaining object is already one repeated quest unit that just needs `aoa-quest-harvest` for the final promotion verdict.
data-ai3
aoa-session-self-repair
Turn a reviewed diagnosis packet into the smallest honest repair packet with checkpoint posture, rollback markers, health checks, and explicit owner-layer targets instead of silent self-mutation. Use when diagnosis already exists and the next honest move is a bounded repair plan or repair-ready packet. Do not use without a reviewed diagnosis, for playbook-scale rollout work, or for vague self-improvement rhetoric with no bounded target.
testing3
aoa-summon
Delegate one bounded child route through quest-passport law, local-first Codex execution defaults, hard gates for progression, self-agent, and stress posture, and governed return into reviewed closeout. Use when a parent route already has a real anchor and named outputs and the honest next move is a narrower child reviewer, evaluator, verifier, or leaf helper rather than a larger orchestration layer. Do not use when the route lacks an anchor, the outputs are unnamed, the work is `d3+` and still needs a split, or remote delegation is being used to bypass proof, approval, or closeout posture.
tools3
atm10-change-protocol
Apply the aoa-change-protocol workflow inside an atm10-* repository using repo-relative paths, commands, review checklists, and explicit local approval notes. Use when the base change protocol is correct but a thin project overlay is needed for local commands and source-of-truth surfaces. Do not use when the base skill is sufficient without local adaptation or when a broader playbook is needed.
testing3
abyss-self-diagnostic-spine
--- name: abyss-self-diagnostic-spine scope: project status: scaffold summary: Thin abyss overlay for turning runtime-body evidence plus optional reviewed session references into one bounded diagnostic session artifact and an honest next-move class without granting silent self-mutation. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0080 - AOA-T-0081 --- # abyss-self-diagnostic-spine ## Intent Use this skill to adapt `aoa-session-self-diagnose` to an `abyss-*` reposit
testing3
aoa-automation-opportunity-scan
--- name: aoa-automation-opportunity-scan scope: core status: scaffold summary: Detect reviewed or repeated project processes that are candidates for automation, classify whether they are seed-ready, and route them to the right owner layer without granting schedule or mutation authority. invocation_mode: explicit-only technique_dependencies: - AOA-T-0086 - AOA-T-0087 - AOA-T-0088 --- # aoa-automation-opportunity-scan ## Intent Use this skill to detect where repeated project work is ripe
tools3
aoa-port-adapter-refactor
Refactor code toward clearer ports and adapters so domain or application logic is less entangled with infrastructure details. Use when concrete dependencies leak into core logic, tests are hard because external concerns bleed inward, or a module needs a clearer seam before further change. Do not use for tiny local fixes or when there is no meaningful boundary to clarify.
development3
aoa-property-invariants
--- name: aoa-property-invariants scope: core status: canonical summary: Express stable system or domain truths as invariant-oriented tests and checks rather than only enumerating examples. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0017 - AOA-T-0007 --- # aoa-property-invariants ## Intent Use invariant-oriented thinking to test broad behavior through properties rather than only through a short list of fixed examples. ## Trigger boundary Use this skill when: - a
testing3
aoa-local-stack-bringup
--- name: aoa-local-stack-bringup scope: risk status: evaluated summary: Bring up a bounded local multi-service stack by reviewing rendered runtime truth, checking host readiness, and launching through one explicit lifecycle entrypoint. invocation_mode: explicit-only technique_dependencies: - AOA-T-0036 - AOA-T-0037 - AOA-T-0028 - AOA-T-0038 --- # aoa-local-stack-bringup ## Intent Use this skill to turn local multi-service startup into a reviewable bring-up workflow with a visible pre
testing3
aoa-sanitized-share
--- name: aoa-sanitized-share scope: risk status: canonical summary: Separate raw technical material from a shareable public-safe surface, place the sanitized output in the canonical sharing location, and verify that the lesson survives the redaction. invocation_mode: explicit-only technique_dependencies: - AOA-T-0034 - AOA-T-0002 --- # aoa-sanitized-share ## Intent Use this skill to turn potentially sensitive technical material into a shareable, reviewable, public-safe form, keeping the
testing3
aoa-bounded-context-map
--- name: aoa-bounded-context-map scope: core status: canonical summary: Clarify system, domain, layer, and owner boundaries so changes stay semantically scoped, interface-aware, and portable where needed. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0016 - AOA-T-0002 --- # aoa-bounded-context-map ## Intent Use bounded-context thinking to reduce semantic drift, mixed responsibilities, and unclear interfaces. ## Trigger boundary Use this skill when: - a project mix
testing3
aoa-session-self-diagnose
--- name: aoa-session-self-diagnose scope: core status: evaluated summary: Classify drift, friction, proof gaps, ownership confusion, and repeated failure patterns from a reviewed session into a bounded diagnosis packet with explicit evidence posture and no mutation. invocation_mode: explicit-only technique_dependencies: - AOA-T-0080 - AOA-T-0081 --- # aoa-session-self-diagnose ## Intent Use this skill to turn a reviewed session into a `DIAGNOSIS_PACKET`. It should answer: what drifted,
testing3
atm10-source-of-truth-check
--- name: atm10-source-of-truth-check scope: project status: evaluated summary: Thin ATM10 overlay for clarifying repo-local document authority, public-surface roles, canonical files, review checklists, and review posture without changing the base workflow. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0013 - AOA-T-0002 - AOA-T-0009 --- # atm10-source-of-truth-check ## Intent Use this skill to adapt `aoa-source-of-truth-check` to an `atm10-*` repository when the ba
testing3
aoa-approval-gate-check
--- name: aoa-approval-gate-check scope: risk status: canonical summary: Classify whether a requested action should proceed, wait for explicit approval, or be refused at the current authority level. invocation_mode: explicit-only technique_dependencies: - AOA-T-0028 --- # aoa-approval-gate-check ## Intent Use this skill to classify whether a requested action crosses an approval boundary and to return a bounded next step that keeps authority explicit before any execution proceeds. ## Trigge
testing3
aoa-change-protocol
--- name: aoa-change-protocol scope: core status: canonical summary: Bounded workflow for a local coding agent to read the owner route, plan a scoped change, verify it explicitly, and report it clearly. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0001 - AOA-T-0002 --- # aoa-change-protocol ## Intent Ground non-trivial changes in the owner route before editing, then keep the diff reviewable and explicitly verified without hidden scope expansion. ## Trigger boundary
testing3
aoa-tdd-slice
--- name: aoa-tdd-slice scope: core status: canonical summary: Implement a bounded behavior slice across code, CLI, builder, validator, generated/export, adapter, or workflow surfaces through test-first discipline and explicit refactor boundaries. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0014 - AOA-T-0001 --- # aoa-tdd-slice ## Intent Use test-first discipline to implement a small behavior slice with a clear observable target, minimal implementation, and explici
tools3
aoa-session-donor-harvest
--- name: aoa-session-donor-harvest scope: core status: evaluated summary: Harvest reusable donor units from a reviewed session into a bounded HARVEST_PACKET, filter checkpoint or handoff hints through reviewed evidence, route each unit to the right AoA owner layer, and hand off to the next honest post-session skill when needed. invocation_mode: explicit-only technique_dependencies: - AOA-T-0075 - AOA-T-0076 - AOA-T-0077 --- # aoa-session-donor-harvest ## Intent Use this skill to metabo
testing3
aoa-source-of-truth-check
--- name: aoa-source-of-truth-check scope: core status: canonical summary: Clarify which repository guidance, source, configuration, generated/export, operational, status, or provenance surfaces are authoritative, then keep entrypoints short once canonical homes exist. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0013 - AOA-T-0002 - AOA-T-0009 --- # aoa-source-of-truth-check ## Intent Use this skill to clarify which repository surfaces are authoritative for status
testing3
atm10-change-protocol
--- name: atm10-change-protocol scope: project status: evaluated summary: Thin ATM10 overlay for bounded change execution with repo-relative route cards, public docs, commands, review checks, recovery anchors, and explicit local approval notes. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0001 - AOA-T-0002 --- # atm10-change-protocol ## Intent Use this skill to adapt `aoa-change-protocol` to an `atm10-*` repository without changing the base workflow meaning or movin
testing3
aoa-sanitized-share
--- name: aoa-sanitized-share scope: risk status: canonical summary: Separate raw technical material from a shareable public-safe surface, place the sanitized output in the canonical sharing location, and verify that the lesson survives the redaction. invocation_mode: explicit-only technique_dependencies: - AOA-T-0034 - AOA-T-0002 --- # aoa-sanitized-share ## Intent Use this skill to turn potentially sensitive technical material into a shareable, reviewable, public-safe form, keeping the
testing3
atm10-source-of-truth-check
--- name: atm10-source-of-truth-check scope: project status: evaluated summary: Thin atm10 overlay for clarifying repo-local document authority, canonical files, review checklists, and review posture without changing the base workflow. invocation_mode: explicit-preferred technique_dependencies: - AOA-T-0013 - AOA-T-0002 --- # atm10-source-of-truth-check ## Intent Use this skill to adapt `aoa-source-of-truth-check` to an `atm10-*` repository when the base workflow is right but the local do
testing3
aoa-dry-run-first
--- name: aoa-dry-run-first scope: risk status: canonical summary: Prefer simulation, inspection, or preview paths before real execution, and require one explicit confirmation seam before any mutating step runs. invocation_mode: explicit-only technique_dependencies: - AOA-T-0004 - AOA-T-0028 --- # aoa-dry-run-first ## Intent Use this skill to run a preview-first workflow that stops at inspection until one concrete mutation is ready, then asks for a visible confirmation before the real act
testing3
abyss-safe-infra-change
Apply the aoa-safe-infra-change workflow inside an abyss-* repository using repo-relative operational surfaces, explicit local authority notes, rollback posture, and local validation commands. Use when the base infra-change workflow is correct but a thin project overlay is needed for one abyss repo. Do not use when the base skill is sufficient without local adaptation or when the task is really about producing a shareable artifact.
testing3
abyss-sanitized-share
Apply the aoa-sanitized-share workflow inside an abyss-* repository using repo-relative sharing surfaces, explicit local thresholds, and local review posture. Use when the base sanitization workflow is correct but a thin project overlay is needed for one abyss repo. Do not use when the base skill is sufficient without local adaptation or when the real task is the underlying operational mutation.
testing3
abyss-self-diagnostic-spine
Apply the aoa-session-self-diagnose workflow inside an abyss-* repository using repo-relative runtime evidence, bounded diagnostic-session artifacts, last-good comparison posture, and honest owner-aware handoff. Use when the base diagnosis workflow is correct but one abyss repo needs a thin runtime-owned diagnostic read model before any repair claim becomes honest. Do not use when the request is really for silent repair, when no concrete target path exists, or when the base skill is already sufficient without local adaptation.
development3