Team Skills

The features you use. Every entry-point skill is a slash command you can run (/team, /team-fix, …). There are no methodology skills: what agents used to preload now lives in ordinary playbooks and references they read by path.

Source of truth: the skill bodies themselves, skills/*/SKILL.md. This page is a hand-maintained reference. When it disagrees with a SKILL.md, the SKILL.md wins.

Each entry starts with a short user-facing description of what the skill does, maintained separately from its invocation metadata. **Uses:** lists the skills this skill consumes: the ones it loads through the Skill tool and the ones whose SKILL.md its files read by path. **Used by:** lists the skills that consume it. Both use comma-separated lists, or None. The load form is Call the Skill tool with `<name>`. The path form is a reference to <name>/SKILL.md, relative or root-relative. A reference to any other file in a skill’s directory is neither a load nor a use, and neither is a reference that only locates a skill’s install directory — “the directory containing skills/<name>/SKILL.md” names a location, not the skill.

The edges are therefore directed, and reading them transitively gives the graph. team loads team-code-review, team-pr, and team-security-review. None loads back. **Uses:** None marks a leaf with no further consumption.

References are collected across every .md file in the skill’s directory, so a reference written in a references/ file counts the same as one in SKILL.md. This page carries both directions of each skill-to-skill edge. For what separates a load from a citation, and for how a skill is loaded, see architecture.md §6.

The catalog has 14 registered skills, all commands. The six shared principle documents, playbooks, templates, and operational rules are ordinary installed resources. They are read at the consuming operation and add no picker entries.

Runs the compressed bug-fix pipeline.

Used by: None

Uses: team-worktree

Setup migration and update

Explicit-only commands that change the user’s agent setup rather than a repository.

team-migrate

Moves a machine set up before v0.147.0 onto the Team and bostonaholic/skills plugins in every harness, with no moved skill missing or shown twice.

Used by: None

Uses: None

team-update

Updates Team to the latest release in every harness that already has it from a release. It installs Team nowhere new, retires no skill copy, and leaves a dev install from a local checkout for the developer to pull.

Used by: None

Uses: None

Prose composition and evaluation

The writing standards reference protects exact text and semantic force, scans the untouched draft, and records the applicable checklist before style edits. It then resolves every recorded match, rescans, and self-audits meaning and protected text.

The live-model suite covers zero, one, and many matches; exact code, user, and vendor text; pipeline authors; the technical-writer semantic veto; the fresh DESIGN reviewer; isolated Research producers and assembly; nested helpers; and the named-parent fallback. These evals are stochastic, paid, periodic, and non-gating. Their assertions use required contracts and score floors rather than expecting identical prose across runs.

Name-collision pairs

Several skills and agents share a stem, which is an easy trap. The pattern is consistent: the skill is the orchestrator or methodology, while the agent is the specialist that does the work.

Skill	Agent	How they differ
`team-research`	`researcher`	Skill dispatches the Research phase. The agent is the doer that runs the research.
`team-question`	`questioner`	Skill drives the Question phase. The agent decomposes the intent.
`team-design`	`design-author`	Skill drives the Design phase. The agent drafts the alignment doc.

Shared principle resources

Read these ordinary documents at their consuming step. They add no registrations or picker entries.

Team Skills

Entry-point skills

Setup migration and update

Prose composition and evaluation

Name-collision pairs

See also

Shared principle resources