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'.

Jump to install

Repository: Tibsfox/gsd-skill-creator
Last source activity: June 10, 2026 at 22:32
Detected SKILL.md language: English
Stars: 69
Forks: 9

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/Tibsfox/gsd-skill-creator --skill team-control

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

goal-ambiguity-gate

Use the moment a request is underspecified and you are about to act on an ASSUMED goal. Enumerate the candidate goals the request could mean, project the action or artifact each one implies, and check whether they diverge: if two or more plausible goals lead to materially different actions or artifacts, ask exactly ONE targeted clarifying question; otherwise proceed on the most-likely goal and state the assumption in one line. Clarification is an evidence-producing action, not a delay — but one question, never an interrogation. Distinct from gsd-spec-phase (GSD-phase-bound, emits a heavy SPEC.md) and intent-router (fetch strategy, not goal disambiguation). Backed by agent goal-state inference (arxiv 2606.16813v1). Triggers on acting under an assumed goal when the request admits more than one materially different reading.

2026-07-19

memory-hubness-gate

Use at write time to vector/embedding memory — Grove content-addressed insertion, chroma/pgvector upserts, memory-consolidation promoting session traces to MEMORY.md, or embedding externally-ingested content. Scores each candidate record against a fixed panel of sentinel queries and quarantines any record that would become the nearest neighbor of too many unrelated queries — a hub — whether from adversarial poisoning or accidental over-generality. This is the memory-record-side sibling of skill-injection-guardian (file-side) and the write-side complement of memory-use-warrant (read-side). Quarantine, never silently drop; a human reviews. Backed by the admission-time hubness gate (arxiv 2606.19692v1). Triggers on inserting into vector memory, consolidating memory, and embedding stranger content.

2026-07-19

memory-use-warrant

Run this appropriateness check the moment you are about to integrate a retrieved long-term memory — a Grove content-addressed hit, a chroma/pgvector neighbour, a memory-consolidation digest, or a MEMORY.md line — into a response, especially anything touching private origins, Fox Companies IP, credentials, or Center Camp / consent-governed content. It answers a question intent-router never asks: not WHAT to fetch or HOW, but WHETHER a correctly-retrieved item should reach output. Relevance is not appropriateness — a perfect similarity match can still be a boundary violation. Default is FAIL-CLOSED: if in-context authorization is uncertain, the memory may inform behaviour but must not be surfaced. Backed by RBI-Eval (arxiv 2606.06055v1). Triggers on surfacing recalled sensitive memory into a response.

2026-07-19

View all from this repository

name	team-control
description	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'.
format	"2025-10-02T00:00:00.000Z"
version	1.0.0
status	ACTIVE
updated	"2026-04-15T00:00:00.000Z"
triggers	["during UC milestone work","user says 'bring up the dev team'"]

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)

Agent	Model	Role	Key Responsibility
lab-director	Opus	Authority	Go/no-go, plan approval, quality rubric, strategic direction
flight-ops	Opus	Operations	Pipeline management, milestone/phase spawning, error handling
capcom	Sonnet	Communications	Context lifecycle, handoffs, warm starts, continuity
watchdog	Haiku	Monitor	Stuck 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)

lab-director IS the human — no waiting for external approval
Auto-approve plans that pass quality gates (TDD, tests, NASA SE or clean commits)
Auto-close milestones when enforcement checks pass
Auto-handoff context when pressure detected (>80%)
Auto-scale parallelism based on observed metrics (UC Mode)
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)

Pattern	Detection	Resolution
Waiting for user	Watchdog	lab-director decides
Context full	Capcom	Handoff protocol
Agent idle	Watchdog	flight-ops reassigns
Repeated failure	Watchdog	flight-ops escalates
Lost state	Capcom	Restore 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)

Dimension	Weight	Min Score
Completeness	25%	3.0
Depth	30%	3.0
Connections	25%	3.0
Honesty	20%	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

Read .planning/STATE.md for current position
Read ~/.claude/teams/sc-dev-team/config.json for team state
Check TaskList for pending work
Create team if not exists: TeamCreate(team_name: "sc-dev-team")
Spawn agents into team:
- flight-ops (opus) — drives execution
- lab-director (opus) — approves, unblocks
- capcom (sonnet) — context management
- watchdog (haiku) — health monitoring
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/

team-control

Source facts

Install options

Review the source files

More from this repository

Team Control — Autonomous Mission Control

Team Architecture (shared)

Autonomy Principles (shared)

Context Management (shared)

Stuck State Prevention (shared)

UC Mode — Unit Circle Laboratory

Pipeline Flow

Quality Rubric (UC Mode, VERBATIM)

Integration with Observatory

Chipset & Files (UC Mode)

Dev Mode — SC Dev Team

Activation

Pipeline Flow (Dev Mode)

Key Differences from UC Mode

Team Files (Dev Mode)

More from this repository

Team Control — Autonomous Mission Control

Team Architecture (shared)

Autonomy Principles (shared)

Context Management (shared)

Stuck State Prevention (shared)

UC Mode — Unit Circle Laboratory

Pipeline Flow

Quality Rubric (UC Mode, VERBATIM)

Integration with Observatory

Chipset & Files (UC Mode)

Dev Mode — SC Dev Team

Activation

Pipeline Flow (Dev Mode)

Key Differences from UC Mode

Team Files (Dev Mode)