hatch3r-ci-pipeline

# CI Pipeline Workflow ## Quick Start ``` Task Progress: - [ ] Step 0: Detect ambiguity (P8 B1) - [ ] Step 1: Audit existing pipeline - [ ] Step 2: Design stage structure - [ ] Step 3: Optimize test parallelization - [ ] Step 4: Configure artifact management - [ ] Step 5: Implement and validate ``` ## Step 0 — Detect Ambiguity (P8 B1) Before any work, scan the invocation for unresolved questions in scope, intent, acceptance criteria, target environment, or irreversibility. If any are found, ask the user via the platform-native question tool per `agents/shared/user-question-protocol.md`. Do not proceed under silent assumption. Default path, not an exception. Triggers for THIS skill: CI platform (GitHub Actions vs GitLab vs CircleCI vs Azure Pipelines), pipeline duration target, runner sizing budget, deploy gate (auto vs manual approval for prod), and artifact retention policy. ## Fan-out Discipline (P8 B2) Fan-out scales with task size; token cost never justifies serializing independent work (`rules/hatch3r-fan-out-discipline.md` P8 B2; `agents/shared/efficiency-patterns.md`). Emit `sub_agents_spawned: { count, rationale, task_structure }` in your output. ## Step 1: Audit Existing Pipeline - Map the current pipeline stages, their dependencies, and execution times. - Identify bottlenecks: which stages take the longest? Which block others unnecessarily? - Check for flaky tests that cause unnecessary reruns. - Review resource usage: are runners appropriately sized? Are ca...