本文へ移動
cccskills
無料GitHub で公開

team-control

Unit Circle Laboratory + sc-dev-team autonomous mission control. Provides human-in-the-loop automation layer, pipeline management, context lifecycle, stuck-state prevention. UC re-execution series and dev branch milestones. Adapted from uc-lab pattern for code plan/execute/verify/complete. Auto-activates during UC milestone work; trigger: user says 'bring up the dev team'.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Team Control — Autonomous Mission Control

Autonomous mission-control skill with two parameterized modes for the two team branches:

  • UC Mode — Unit Circle Laboratory, v1.50 milestone review series (formerly uc-lab)
  • Dev Mode — SC Dev Team, dev branch code execution (formerly sc-dev-team)

Both modes share the same four-agent architecture, autonomy principles, context management, and stuck-state prevention. The mode is selected by the active branch (UC on v1.50, Dev on dev) or by explicit invocation. Either way, the team acts as the human-in-the-loop layer so the pipeline never stalls waiting for decisions.

Team Architecture (shared)

AgentModelRoleKey Responsibility
lab-directorOpusAuthorityGo/no-go, plan approval, quality rubric, strategic direction
flight-opsOpusOperationsPipeline management, milestone/phase spawning, error handling
capcomSonnetCommunicationsContext lifecycle, handoffs, warm starts, continuity
watchdogHaikuMonitorStuck detection, health checks, overload alerts

Agent definitions: .claude/agents/lab-director.md, flight-ops.md, capcom.md, watchdog.md.

Team pre-flight (topology check). Before launching the team — spawning the four agents, or any larger fan-out flight-ops sizes up — run the spectral-topology-preflight skill on the proposed communication graph. It builds the row-stochastic operator from the team graph and emits a (ρ, Δ, κ) coordination signature plus a pass/fail verdict against per-task-class thresholds, so coordination defects are caught pre-dispatch rather than mid-run. Honor a fail verdict (adjust the topology) before flight-ops spawns work.

Autonomy Principles (shared)

  1. lab-director IS the human — no waiting for external approval
  2. Auto-approve plans that pass quality gates (TDD, tests, NASA SE or clean commits)
  3. Auto-close milestones when enforcement checks pass
  4. Auto-handoff context when pressure detected (>80%)
  5. Auto-scale parallelism based on observed metrics (UC Mode)
  6. Auto-heal stuck states via watchdog detection + flight-ops resolution

Context Management (shared)

  • Green (0-60%): Normal operations
  • Yellow (60-80%): Prepare handoff materials
  • Red (80%+): Initiate handoff immediately
  • Handoffs stored at .planning/uc-observatory/handoffs/ (UC Mode) or repo-local (Dev Mode)
  • STATE.md is always the source of truth

Stuck State Prevention (shared)

PatternDetectionResolution
Waiting for userWatchdoglab-director decides
Context fullCapcomHandoff protocol
Agent idleWatchdogflight-ops reassigns
Repeated failureWatchdogflight-ops escalates
Lost stateCapcomRestore from handoff

UC Mode — Unit Circle Laboratory

Autonomous mission control for the Unit Circle re-execution series (v1.50.14+). Branch-bound to v1.50.

Pipeline Flow

QUEUE → PRE-FLIGHT → INIT → PLAN → APPROVE → EXECUTE → VERIFY → ANALYZE → RETRO → CLOSE → HANDOFF → NEXT
  ↑                                                                                                    |
  +----------------------------------------------------------------------------------------------------+

Quality Rubric (UC Mode, VERBATIM)

DimensionWeightMin Score
Completeness25%3.0
Depth30%3.0
Connections25%3.0
Honesty20%3.0

Weighted average must be >= 3.0 for auto-approval.

Integration with Observatory

The lab team coordinates with uc-observatory agents:

  • Pre-milestone: Spawns uc-brainstorm-engine, uc-skill-forger
  • Post-milestone: Spawns uc-perf-analyst, uc-proof-engineer, uc-retro-analyst
  • Between milestones: Reviews observatory reports for strategic decisions

Chipset & Files (UC Mode)

  • Lab chipset: .planning/uc-observatory/lab-chipset.yaml
  • Observatory chipset: .planning/uc-observatory/chipset.yaml
  • Handoffs: .planning/uc-observatory/handoffs/
  • Reports: .planning/uc-observatory/reports/
  • Metrics: .planning/uc-observatory/metrics/

Dev Mode — SC Dev Team

Autonomous execution team for dev branch milestones. Adapted from the UC pattern for code execution (plan/execute/verify/complete). Trigger: user says "bring up the dev team" or "sc-dev-team". Branch-bound to dev.

Activation

  1. Read .planning/STATE.md for current position
  2. Read ~/.claude/teams/sc-dev-team/config.json for team state
  3. Check TaskList for pending work
  4. Create team if not exists: TeamCreate(team_name: "sc-dev-team")
  5. Spawn agents into team:
    • flight-ops (opus) — drives execution
    • lab-director (opus) — approves, unblocks
    • capcom (sonnet) — context management
    • watchdog (haiku) — health monitoring
  6. Assign first pending task to flight-ops

Pipeline Flow (Dev Mode)

STATE.md → PLAN PHASE → EXECUTE PHASE → VERIFY → NEXT PHASE → ... → COMPLETE MILESTONE

Key Differences from UC Mode

  • Branch: dev (not v1.50)
  • Work type: Code execution (not review milestones)
  • GSD commands: /gsd:plan-phase, /gsd:execute-phase, /gsd:complete-milestone
  • No observatory integration (dev milestones don't use the UC review rubric)
  • Quality gate: Tests pass + clean commits (not the review scoring rubric above)

Team Files (Dev Mode)

  • Team config: ~/.claude/teams/sc-dev-team/config.json
  • Tasks: ~/.claude/tasks/sc-dev-team/

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Provides web accessibility best practices for semantic HTML, ARIA, keyboard navigation, color contrast, and screen reader patterns. Use when building UI components, reviewing accessibility, or when user mentions 'a11y', 'accessibility', 'ARIA', 'screen reader', 'keyboard navigation', 'WCAG'.

日本語の概要は準備中です。原文の説明を表示しています。

Tibsfox/gsd-skill-creator712026年7月20日 更新

Active listening techniques for effective communication. Covers attending behaviors, paraphrasing, reflective listening, clarifying questions, empathic response, barriers to listening, listening in conflict, and cross-cultural listening. Use when building listening skills, improving understanding in conversation, mediating disputes, or analyzing communication breakdowns.

日本語の概要は準備中です。原文の説明を表示しています。

Tibsfox/gsd-skill-creator712026年7月20日 更新

Adversarial spec-compliance PR review — cross-references diffs against approved specs, verifies runtime claims against source, detects competing PRs, audits scope/convention compliance. Use before merging.

日本語の概要は準備中です。原文の説明を表示しています。

Tibsfox/gsd-skill-creator712026年7月20日 更新

Provides best practices for AI agent orchestration including MCP servers, A2A protocol, multi-agent coordination, and swarm architectures. Use when designing agent systems, configuring MCP servers, setting up agent teams, or when user mentions 'MCP', 'A2A', 'agent orchestration', 'multi-agent', 'swarm', 'agent team', 'LangGraph', 'CrewAI', 'AutoGen'.

日本語の概要は準備中です。原文の説明を表示しています。

Tibsfox/gsd-skill-creator712026年7月20日 更新

Symbolic manipulation, equation solving, and algebraic structures for mathematical reasoning. Covers distributive law, factoring, completing the square, linear through polynomial equation solving, systems of equations (substitution, elimination, Gaussian elimination, matrix methods), algebraic structures (groups, rings, fields), modular arithmetic, polynomial theory, and inequalities. Use when solving equations, simplifying expressions, working with algebraic structures, or performing symbolic manipulation.

日本語の概要は準備中です。原文の説明を表示しています。

Tibsfox/gsd-skill-creator712026年7月20日 更新

Understanding how algorithmic systems shape what users see, know, and do -- from recommendation feeds to search ranking to credit scoring to hiring software. Covers the mechanics of recommendation systems, algorithmic bias and its sources, personalization's effects on information diets, opacity and accountability, AI limitations (hallucination, confident wrongness), and the human-in-the-loop question. Use when a learner needs to think critically about why particular content reached them.

日本語の概要は準備中です。原文の説明を表示しています。

Tibsfox/gsd-skill-creator712026年7月20日 更新

Tibsfox のスキルをすべて見る

このスキルの問題を報告する