agentleFS
odere-proodere-pro/claude-software-3-0-marketplace/.claude/teams/CLAUDE.md

claude-software-3-0-marketplace / teams

CLAUDE.md2 starsChanged 5 months agoMITView on GitHub

Never shipped; never loaded into an end-user session. This layer holds reusable, spawnable agent teams for developing the registry. A team is a folder with a shared brief plus a roster of auto-discovered agent definitions in .claude/agents/. - registry-dev/ — the engineering team that implements the brainstorm roadmap (docs/plan/) behind the gate suite. Its nine roles are spawnable agents named registry-dev-* in .claude/agents/. Entry point: registry-dev-manager. - TEAM-BRIEF.md — shared context every teammate reads first (mission, non-negotiables, lanes, phase sequencing,…

The file

We split this CLAUDE.md into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Never shipped; never loaded into an end-user session.

    line 3

≈ “Common” is an estimate: at least 1 in 5 of the 27,641 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

.claude/teams/ — author-only spawnable teams

Never shipped; never loaded into an end-user session. This layer holds reusable, spawnable agent teams for developing the registry. A team is a folder with a shared brief plus a roster of auto-discovered agent definitions in .claude/agents/.

Map

  • registry-dev/ — the engineering team that implements the brainstorm roadmap (docs/plan/) behind the gate suite. Its nine roles are spawnable agents named registry-dev-* in .claude/agents/. Entry point: registry-dev-manager.
    • TEAM-BRIEF.md — shared context every teammate reads first (mission, non-negotiables, lanes, phase sequencing, working agreement, Definition of Done).
    • BACKLOG.md — the assignable work breakdown (phase → lane → item), filled from the roadmap.
    • README.md — roster, prerequisites, the launch kickoff prompt, workflow, DoD summary.

How it relates

This is the implementation half of the two-team apparatus. The ideation half lives in docs/brainstorm/ and produces the roadmap this team consumes. See ../../docs/teams.md.

Prerequisites

Agent Teams enabled: CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 in ~/.claude/settings.json (read at startup — restart Claude Code after enabling). The registry-dev-* role files are auto-discovered as agent types, so any teammate can be spawned directly; the Delivery Lead is the entry point.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.