pre-agent-task

name

pre-agent-task

description

Advisory pre-flight check before multi-step AI agent tasks that will modify code or infrastructure. Use before delegating any multi-step task to an AI agent (Claude subagent, Codex, CI automation, or similar) that will touch module source files, databases, queues, or shared resources. Also use when starting any agentic session that will write to production infrastructure, when the task plan includes deletion, recreation, or schema changes, or any time you hear "run an agent on", "have Claude handle", "automate this across modules", or "let the agent figure it out". Reads MODULE_MANIFEST.md for affected modules, cross-checks planned operations against permitted/restricted operations and DECISION_LOG.md warnings, and produces an advisory checklist before the task begins. Advisory only — does not block. Invoke as /pre-agent-task or /pre-agent-task --modules path/to/a path/to/b

/pre-agent-task

Advisory pre-flight check for multi-step agent tasks. This skill catches the obvious mismatches between what an agent plans to do and what the affected modules say is safe — before the agent runs, not after.

What this is catching

Structural dark code — agent-assembled runtime behavior nobody designed — is the hardest category to detect. But a meaningful subset of agent risk is knowable in advance: if a module's MODULE_MANIFEST.md says a resource is persistent and the agent's task plan includes deleting it, that conflict is detectable right now. This skill makes that check.

It cannot observe what the agent does at runtime. It catches declared intent mismatches, not emergent behavior. It is advisory — it will not stop the agent from running. But it gives the engineer the chance to catch the obvious problems before they become incidents.

---

Arguments

• (none) — asks for the task description interactively
• --modules path/to/a path/to/b — pre-specify which modules the agent will touch

---

Phase 1: Get the task description

If --modules was not provided, ask: