Agent skill

Development Team

by mvschwarz in mvschwarz/openrig

A skill your agent uses when a development pod begins or hands off implementation, QA, or design work.

Apache-2.0Auto-check passedAgent Workflows

Install Development Team

skills CLI
$ npx skills add mvschwarz/openrig --skill development-team -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig development-team --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/_canonical/pods/development-team .claude/skills/development-team && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
development-team
GitHub stars
5.9k
Token cost
~721 tokens
SKILL.md length
389 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when a development pod begins or hands off implementation, QA, or design work.

  • A development pod begins
  • SKILL.md covers Start from the work, Build and verify, QA and design and Blockers and return
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Hands off implementation

What it does

Development Team is an agent skill from mvschwarz/openrig. Use when a development pod begins or hands off implementation, QA, or design work.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • A development pod begins
  • Hands off implementation

Example prompts

  • “/development-team”

What it can do on your machine

Read from SKILL.md and the folder at commit 1f69831. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Development Team loads about 721 tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 389 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~721

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit 1f69831, republished under its Apache-2.0 licence (© mvschwarz). 389 words, ~721 tokens.

Download SKILL.mdSave it as .claude/skills/development-team/SKILL.md (or your agent's skills folder).
name
development-team
description
Use when a development pod begins or hands off implementation, QA, or design work.

Development Team

The pod turns the assigned user outcome into working software. Builders, QA and designers are capabilities; neighboring roles may be held by one seat unless independence was explicitly selected.

Start from the work

Run rig whoami --json, then resolve project.yaml -> mission.yaml -> active slice.yaml -> selected component or wave map -> addressed context. The complete lookup and precedence rule is docs/reference/product-journey-sdlc.md#resolve-the-selected-path (installed: $OPENRIG_HOME/reference/product-journey-sdlc.md#resolve-the-selected-path). Read the selected addresses and source needed for this task; skills available in your profile are capabilities, not a mandatory reading list. No composition means light Part A. Role names and idle seats add no gates. Explicit rigor and authored wave boundaries retain their named checks.

Build and verify

Clarify consequential uncertainty, inspect the existing seam, then complete one coherent outcome. Reproduce a defect before repairing it; use tests that distinguish the failure and verify through the public surface. Keep chunks as large as the outcome and file territory permit. TDD is a feedback loop, not a two-seat protocol.

The builder reports the exact candidate, changed behavior, commands and observed results, with remaining uncertainty. No universal pre-edit proposal, QA approval or post-edit gate is implied. When one is explicitly selected, honor its boundary and send the relevant evidence directly to its owner.

Show full SKILL.md (185 more words)Show less

QA and design

QA compares the delivered behavior with the actual contract. Read the diff and exercise the result; avoid tests that merely repeat the implementation. On a tiny change the builder may hold QA. Independent QA excludes the author when selected. A wave receives independent review at its authored boundary, not per slice.

Design clarifies user flows and ambiguous behavior when the outcome needs it. Browser and dogfood skills load for a relevant UI journey, not every task. During assigned dogfood, fix-and-retest only within the granted scope; a read-only assignment stays read-only. If a tester becomes an author, preserve that attribution when independent evaluation is required.

Blockers and return

Use systematic-debugging for an unexpected failure and verification-before-completion before claiming success. A permission prompt is a concrete blocker; report the command and consequence instead of labeling it progress. A missing decision goes to the owner who can settle it.

Return the candidate and evidence through the selected handoff. Do not create obligations just to keep an idle QA, guard or reviewer occupied. Quality is a working product with honest evidence, not the number of transfers.

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/_canonical/pods/development-team of mvschwarz/openrig.

Open the folder on GitHubat commit 1f69831

Compare with similar skills

Development Team next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Development Team compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Development Team this skillmvschwarz/openrig5.9k—~721Automated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from mvschwarz/openrig

All 49 skills in this repo
  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    5.9k GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed
  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    5.9k GitHub stars~864 tokensUpdated today
    Auto-check passed
  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    5.9k GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    5.9k GitHub starsUsed in 1 repo~341 tokens
    Auto-check passed
  • Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    5.9k GitHub stars~2.1k tokensUpdated today
    Auto-check passed
  • Cross Host Rig Commands

    mvschwarz/openrig

    A skill your agent uses when addressing a registered remote OpenRig host, choosing its transport, or interpreting a cross-host result.

    5.9k GitHub starsUsed in 1 repo~1.3k tokens
    Auto-check passed

Categories

Questions about Development Team

What does Development Team do?

A skill your agent uses when a development pod begins or hands off implementation, QA, or design work. Development Team is an agent skill from mvschwarz/openrig. Use when a development pod begins or hands off implementation, QA, or design work.

When should I use Development Team?

Development Team fits situations like: A development pod begins; hands off implementation.

How do I install Development Team in Claude Code?

Run `npx skills add mvschwarz/openrig --skill development-team -a claude-code`. Or copy the skill folder (skills/_canonical/pods/development-team in mvschwarz/openrig) into .claude/skills/development-team in your project. Claude Code loads it when a task matches its description.

How do I install Development Team in Codex?

Run `npx skills add mvschwarz/openrig --skill development-team -a codex`. Or copy the skill folder (skills/_canonical/pods/development-team in mvschwarz/openrig) into .agents/skills/development-team in your project. Codex loads it when a task matches its description.

Can I use Development Team in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill development-team -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/development-team, .gemini/skills/development-team, .github/skills/development-team and .opencode/skills/development-team in your project.

What does Development Team need to run?

SKILL.md names no scripts, command-line tools or credentials: Development Team is instructions for the agent only.

Does Development Team access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Development Team safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Development Team use?

Development Team is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Development Team use?

About 721 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Development Team?

Skills that share tags, products or a category with Development Team: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Development Team?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 5,854 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 8, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.