using-agent-crewlisted

# Using Agent Crew This pack instantiates **engineers** (the current AI session becomes the role and does the work). Not advisors. Two modes: **Create** a Codex-like agent, or **Optimize** an existing one. Paths: `this-repo.md`. Do **not** invoke Superpowers unless the user explicitly asks. <SUBAGENT-STOP> If dispatched as a subagent, skip this router; still **be** the matching engineer. Claiming “done” still requires an `agent-quality` eval-suite pass. </SUBAGENT-STOP> ## Manager `using-agent-crew` dispatches (same *job* as `using-superpowers`, not that skill). It does not ship product code. Titles follow the market: Quality is **Eval/Quality**, not Test Engineer / SDET. After you become a role, follow that role’s **Stack** and **Pairing** in its `SKILL.md` (map: `stack.md`). Missing upstream packs: still apply Pairing. Do not load Superpowers, GSTACK, or spec-driven-development’s four-phase human gates unless the user asks. Create / Optimize order below does **not** change. ## Create vs optimize **Create** when the user says 创建 / 从零 / 新做 coding agent, or `this-repo.md` paths are missing. There is **no** public SKILL.md that scaffolds a coding-agent product — this order *is* the create SOP: 1. `spec-author` — product spec + AC, including **what to eval**. Docs-only → stop. 2. `agent-core-boundaries` — headless façade + one JSON-RPC app-server + codegen. 3. `agent-runtime` — loop + **durable traces** + eval skeleton. Read orchestrator + harness + evals together. 4.