team-ship

name	team-ship
description	Full team pipeline then commit and open a PR to develop (Git Flow)

Run the full team development pipeline, then commit and open a PR. YOU (the main session) are the orchestrator — you spawn and wait for subagents. Execute every phase automatically without asking between phases unless genuinely ambiguous.

Task: the task/scope the user described when invoking this skill (if none given, ask or infer from context)

Concurrency & nesting limits: at most 6 subagents run concurrently; nesting depth is 1, so spawned subagents CANNOT spawn their own subagents. The main session orchestrates directly rather than delegating orchestration to a spawned team-lead.

Phase 1: Analysis (PARALLEL)

Spawn in parallel and wait for BOTH:

• planner — dependency-ordered, testable task breakdown.
• architect — structure, patterns, integration points, risks. Reconcile both reports into one plan.

Phase 2: Design (UI 작업 포함 시에만)

Skip for backend-only, bug-fix, or refactor tasks with no UI change.

• design-system/MASTER.md가 있으면 로드해 재사용 (필요 시 page override).
• 없으면 ~/.codex/skills/ui-ux-pro-max/ (reasoning-rules.md → styles.md)로 토큰 확정 후 design-system/MASTER.md 생성.
• 구현은 MASTER 토큰 100% 준수 (raw hex 금지, 시맨틱 토큰만, 이모지 구조 아이콘 금지, 터치 타겟 ≥44pt).

Phase 3: Implement

• Foundation first (types → logic → UI), following existing conventions.
• If the plan has 3+ independent components, spawn one worker subagent per component (distinct, non-overlapping file sets; never two agents on the same file). Respect the 6-concurrent cap; batch if more. Wait for all before proceeding.
• Dependent components stay sequential.

Phase 4: Verify

Run and auto-fix failures (up to 3 attempts): build, lint/type-check, tests. For UI changes also run /design-audit checks.

Phase 5: Review (PARALLEL)

Spawn in parallel and wait for ALL: code-reviewer + security-reviewer (+ qa-tester only if UI). Merge findings; fix every CRITICAL and WARNING; re-run Phase 4.

Phase 6: Git & PR (Git Flow)

1. Stage relevant files (exclude .env, secrets, large binaries).
2. Branch off develop: git checkout develop && git pull then create a feat/…, fix/…, or hotfix/… branch. If develop doesn't exist, branch off the default branch and note it.
3. Commit: type(scope): description.
4. Push with -u.
5. Open a PR targeting develop with gh pr create --base develop: clear title (<70 chars), summary of changes, test plan, and review findings addressed.

Phase 7: Report

PR URL, summary of changes, review results (quality + security + any QA), and manual testing needed.

Rules

• Execute autonomously — don't ask between phases.
• Spawn independent agents in one batch (max 6 concurrent).
• Never force-push; never commit secrets.
• Ask only if genuinely ambiguous.