Menu
Translate a lead agent's return into project-aware language and decide the next action.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Keep commits atomic — split a mixed change set into scoped, reviewable commits.
The one-time procedure to take an exported project to live — understand it, confirm the name/goal/stack with the user, run the deterministic `aspis bootstrap`, enrich the judgment files (AGENTS.md, ARCHITECTURE, context), verify, and let the package self-clean. Followed by the bootstrap agent.
Keep per-subsystem architectural intent current through the planning loop — read before designing, record an impact report on change, confirm with the user, apply a dated update, and verify the build against approved intent.
Audit a plan's task dependency graph for structural integrity — circular dependencies, missing prerequisites, orphan tasks, and dependency classification (hard/soft/warning). Produces a pass/warn/fail audit report per dependency so planners catch graph errors before build starts.
Every editing agent should start on a clean working tree so parallel work never collides.
Verify hooks ran, no secrets, protected paths untouched, and commit message valid before committing. Owned by the reviewer.
| name | recontextualization |
| description | Translate a lead agent's return into project-aware language and decide the next action. |
When a lead agent returns to the project-lead with a result, question, or blocker, translate its domain-specific output into project-level context and decide what happens next — so the project-lead stays the single orchestrator without needing deep domain knowledge of every lead's internals.
changes-required from reviewer → "build not yet acceptable"cannot-reproduce from fix-lead → "need more environment info"3-attempt cap hit → "escalation needed"REVIEW_NEEDED → "decision needed from project-lead"