aoa-summon

Launch child routes safely after validating anchor and named outputs.

4|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/8Dionysus/aoa-skills --skill aoa-summon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aoa-summon
Source: https://github.com/8Dionysus/aoa-skills/tree/main/.agents/skills/aoa-summon
Command: npx skills add https://github.com/8Dionysus/aoa-skills --skill aoa-summon

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents unsafe delegation by ensuring a parent route has a real anchor and named outputs before launching a child helper, enforcing codex‑first execution, stress gates, and proper closeout.

Core Features & Use Cases

  • Gatekeeping: Validates anchor and output naming before any child launch.
  • Lane Selection: Chooses an honest lane (local leaf, reviewed, remote, split, or human gate) based on difficulty, risk, and stress posture.
  • Closeout Planning: Generates return, checkpoint bridge, memo export, and owner publication plans aligned with reviewed closeout.

Quick Start

Use the aoa-summon skill to evaluate a parent route and decide the appropriate child lane and closeout plan.

Frequently Asked Questions about aoa-summon

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely delegate a bounded child route when a parent route has an anchor and named outputs?

Safe child route delegation validates parent anchors and named outputs, enforces codex-first execution, applies stress gates, and selects an honest lane using a passport-lane matrix to prevent unsafe task delegation.

What is an honest lane in child route delegation and how does lane selection work?

An honest lane is an execution path chosen based on difficulty, risk, and stress posture. Lane selection uses a passport-lane matrix to assign a local leaf, reviewed, remote, split, or human gate path for the child helper.

How do I prevent unsafe delegation when launching a single helper for review or implementation?

Prevent unsafe delegation by enforcing gatekeeping rules that validate real anchors and named outputs before any child launch, ensuring the parent route passes difficulty and stress gates prior to helper invocation.

Can I use stress gates to block child route launches if the parent route lacks a real anchor?

Yes, stress gates and anchor validation block child route launches automatically. Gatekeeping ensures a parent route has a real anchor and named outputs, preventing any unsafe helper execution before lane selection begins.

What's the best way to create return, checkpoint, and publication plans for a launched child route?

The best way to create closeout plans is through reviewed closeout planning, which generates return, checkpoint bridge, memo export, and owner publication plans aligned with the selected execution lane after child route launch.

Does child route delegation work without codex-first execution and closeout planning?

No, child route delegation requires codex-first execution and proper closeout planning. Skipping these gates removes the validation and return plans that prevent unsafe delegation and unbounded child execution.