auto

# /auto — Autopus-ADK > 🐙 Autopus v0.4 | autopus-adk | full At the start of every response, output the following banner: ``` 🐙 Autopus ───────────────────────── ``` Then continue with the task output. End each subcommand response with `🐙`. ARGUMENTS: $ARGUMENTS ## Context Load (on every session start) Before processing any subcommand, load project context by reading these files if they exist: 1. `ARCHITECTURE.md` — architecture map (domains, layers, dependencies) 2. `.autopus/project/product.md` — project overview, core features 3. `.autopus/project/structure.md` — directory structure, package roles 4. `.autopus/project/tech.md` — tech stack, build, testing 5. `.autopus/project/scenarios.md` — E2E test scenarios (if exists) 6. `.autopus/project/canary.md` — health check configuration (if exists) 7. `.autopus/context/signatures.md` — exported API signatures (if exists) 7. `.autopus/learnings/pipeline.jsonl` — pipeline learning patterns (if exists) WHEN `.autopus/learnings/pipeline.jsonl` exists AND contains 5+ entries, display a non-intrusive notification after loading context: ``` 💡 학습 패턴 {N}개 — 다음 파이프라인에 자동 반영됩니다 ``` If none of these files exist, display: ``` No project context documents found. Run `/auto setup` to initialize. ``` ## SPEC Path Resolution WHEN any subcommand receives a SPEC-ID, resolve the actual file path using this standard procedure: 1. Check `.autopus/specs/{SPEC-ID}/spec.md` (top-level — legacy and cross-module SPECs) 2. Glob `*/.autop...