메뉴
Show team health and agent activity for a running team session. Checks agent commits, file changes, task progress, and context exhaustion. Use when user says 'team status', 'how is the team doing', 'check agents', or 'who is stuck'.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Investigate a bug with competing hypotheses and parallel subagents. Use when the user asks to debug an error, find a root cause, or investigate why something is failing.
Review Harbangan plans and code with read-only advisory agents. Use `--plan <path>` for domain-driven plan review, and `--code [target]` for fixed reviewer-dimension code review with domain-advisor consultation.
Update project documentation by consulting all domain agents for accuracy. document-writer leads, other agents provide technical review. Use when user says 'update docs', 'write documentation', 'refresh docs', 'document this', or 'sync documentation'.
ACH-based debugging — spawns domain investigators to evaluate competing hypotheses across the Harbangan stack using formal evidence standards and arbitration. Use when user says 'debug this error', 'why is this failing', 'investigate bug', 'root cause analysis', or 'something is broken'.
Full lifecycle feature implementation — spawns teams, assigns tasks, monitors progress, verifies quality, and creates PRs. Agents remain idle after completion — use /team-shutdown to terminate. Use when user says 'implement this', 'build this feature', 'start working on X', or 'execute the plan'.
Analyze scope, explore codebase, and produce implementation plans. Spawns all 7 domain agents for parallel investigation from their domain perspective, and writes structured plans. Use when user says 'plan this feature', 'analyze scope', 'what would it take to build X', or 'explore before implementing'.
| name | team-status |
| description | Show team health and agent activity for a running team session. Checks agent commits, file changes, task progress, and context exhaustion. Use when user says 'team status', 'how is the team doing', 'check agents', or 'who is stuck'. |
| argument-hint | [team-name] |
| allowed-tools | ["Bash","Read","Grep","Glob","TaskList","TaskGet"] |
Show health and activity for a running agent team. Auto-detects the team if only one is active.
Resolve team: If team-name provided, use it. Otherwise, check ~/.claude/teams/ for active teams — if exactly one, use it; if multiple, ask via output which to inspect.
Load team config: Read ~/.claude/teams/{team-name}/config.json to get member list (name, agentType, agentId).
Check agent activity:
git log --author={agent} --since="30 minutes ago" --oneline for recent commitsClassify each agent:
Context exhaustion detection: 3+ consecutive idle notifications with an in_progress task and no file edits = likely exhausted.
Output summary:
Team: {team-name}
Members: {count} agents
Agent | Status | Current Task | Last Activity
---------------|---------|---------------------|---------------
backend-eng | Active | Implement converter | 2m ago (commit)
frontend-eng | Quiet | Build settings page | 8m ago (file edit)
backend-qa | Stale | Write auth tests | 22m ago
Alerts:
- backend-qa may be context-exhausted (3 idle cycles, no edits)
Actionable suggestions: For stale/exhausted agents, suggest respawn or task reassignment.