{
  "markdown": "# 10x-Team\n\nA Claude Code plugin that gives you an entire engineering team as AI skills. 12 specialized roles — CTO, Architect, SRE, Security Engineer, and more — that share context, track decisions, and hand off work to each other.\n\nOne developer. A full team's coverage.\n\n## Install\n\nFrom within Claude Code:\n\n```\n/plugin marketplace add Jaan-Mustafa/10x-Team\n/plugin install 10x-Team@10x-Team-dev\n/reload-plugins\n```\n\n## Available Skills\n\n### Full Team\n\n| Skill | Use When |\n|-------|----------|\n| `/10x-team` | **Building projects end-to-end** — brainstorms first, then moves through strategy, design, planning, implementation, testing, and deployment with hard gates at every phase |\n\n### Individual Roles\n\n| Skill | Role | Use When |\n|-------|------|----------|\n| `/cto` | Chief Technology Officer | Build vs buy, business case, technical strategy |\n| `/product-manager` | Product Manager | Feature prioritization, user stories, roadmap |\n| `/principal-architect` | Principal Architect | System design, architecture decisions |\n| `/staff-engineer` | Staff Engineer | Cross-team technical decisions, code quality |\n| `/senior-engineer` | Senior Engineer | Implementation guidance, code review |\n| `/sde` | Software Development Engineer | Hands-on coding, debugging |\n| `/devops-engineer` | DevOps Engineer | CI/CD, infrastructure, deployment |\n| `/sre` | Site Reliability Engineer | Reliability, monitoring, incident response |\n| `/security-engineer` | Security Engineer | Security review, threat modeling |\n| `/dba` | Database Administrator | Schema design, query optimization |\n| `/qa-engineer` | QA Engineer | Testing strategy, test plans |\n| `/engineering-manager` | Engineering Manager | Team processes, sprint planning, delivery |\n\n## How Roles Communicate\n\nSkills share context across conversations through file-based project state in `.10x/`.\n\n### Setup\n\n```\n/init-project\n```\n\n### State Structure\n\n```\n.10x/\n├── status.md              # Current phase, task progress, blockers\n├── handoff.md             # Context passed from one role to the next\n├── decisions/             # One file per role\n│   ├── cto.md             # Strategy, build/buy, tech stack\n│   ├── product-manager.md # Requirements, scope, user stories\n│   ├── architect.md       # System design, components, boundaries\n│   ├── staff-engineer.md  # Patterns, standards, cross-cutting\n│   ├── engineering-manager.md # Task breakdown, estimates\n│   ├── senior-engineer.md # Implementation approach\n│   ├── sde.md             # What was built, deviations, tech debt\n│   ├── dba.md             # Schema, migrations, indexing\n│   ├── security.md        # Threat model, vulnerabilities\n│   ├── qa.md              # Test results, bugs, coverage\n│   ├── devops.md          # CI/CD, deploy strategy, rollback\n│   └── sre.md             # SLOs, monitoring, runbooks\n├── specs/                 # Design docs from brainstorming\n└── reviews/               # QA reports + security audits\n```\n\n### How It Works\n\n```\n/cto decides \"Use Razorpay\"\n  → writes decision to .10x/decisions/cto.md\n  → writes handoff context for PM and Architect\n\n/principal-architect designs the payment service\n  → reads CTO decision from .10x/decisions/cto.md\n  → designs with full context\n  → writes architecture to .10x/decisions/architect.md\n\n/sde implements the payment webhook\n  → reads ALL decision files\n  → codes with full team context\n  → writes what was built to .10x/decisions/sde.md\n```\n\nEvery role reads its dependencies before acting and writes its decisions after completing work. The orchestrator (`/10x-team`) enforces this with hard gates at every phase transition.\n\n## Usage Examples\n\n```\n> /10x-team Build me a URL shortener with analytics\n\n> /cto Should we build our own payment system or use Razorpay?\n\n> /principal-architect Design a notification service that handles 10M events/day\n\n> /sre Our API latency spiked 3x after the last deploy — help me investigate\n\n> /security-engineer Review this auth flow for vulnerabilities\n\n> /dba We have a 50M row table and this query is slow — optimize it\n```\n\n## Project Structure\n\n```\n10x-Team/\n├── .claude-plugin/\n│   ├── plugin.json              # Plugin manifest\n│   └── marketplace.json         # Marketplace registry\n├── skills/\n│   ├── 10x-team/SKILL.md       # Orchestrator — all 12 roles\n│   ├── cto/SKILL.md\n│   ├── product-manager/SKILL.md\n│   ├── principal-architect/SKILL.md\n│   ├── staff-engineer/SKILL.md\n│   ├── senior-engineer/SKILL.md\n│   ├── sde/SKILL.md\n│   ├── devops-engineer/SKILL.md\n│   ├── sre/SKILL.md\n│   ├── security-engineer/SKILL.md\n│   ├── dba/SKILL.md\n│   ├── qa-engineer/SKILL.md\n│   └── engineering-manager/SKILL.md\n├── commands/\n│   └── init-project.md          # Initialize .10x/ project state\n├── tests/\n│   └── validate-skills.test.js  # Skill structure validation\n└── docs/\n    └── adr/                     # Architecture decision records\n```\n\n## Contributing\n\nContributions are welcome! Whether it's improving an existing skill, adding a new role, fixing bugs, or improving documentation.\n\n### Adding a New Skill\n\n1. Create a folder under `skills/` with a `SKILL.md` file:\n\n```\nskills/my-role/SKILL.md\n```\n\n2. Follow this structure:\n\n```markdown\n---\nname: my-role\ndescription: \"When this skill should be triggered and what it does.\"\n---\n\n# Role Title\n\nOne-line summary of what this skill helps with.\n\n<HARD-GATE>\nWhat must happen BEFORE giving recommendations.\n</HARD-GATE>\n\n## Anti-Pattern: \"Common Mistake Title\"\nWhy skipping the process causes problems.\n\n## Checklist\nOrdered steps the skill must follow.\n\n## Process Flow\nVisual flow of the decision process.\n\n## The Process\nDetailed guidance for each phase.\n\n## Project State Protocol\n### Before You Start (EVERY time)\nRead relevant .10x/decisions/ files.\n### Before You Finish (EVERY time)\nWrite your decisions to .10x/decisions/<role>.md.\n\n## Key Principles\nCore rules that guide the skill's behavior.\n\n## Anti-Patterns to Flag\nCommon mistakes to call out.\n\n## Tone\nHow the skill should communicate.\n```\n\n3. Run tests:\n\n```bash\nnode tests/validate-skills.test.js\n```\n\n4. Reload plugins:\n\n```\n/reload-plugins\n```\n\n### Updating an Existing Skill\n\n1. Edit the `SKILL.md` in `skills/<role>/`\n2. Keep the same structure — frontmatter, hard gate, checklist, process, state protocol, principles\n3. Run tests and reload\n\n### Reporting Issues\n\nFound a bug or have an idea? [Open an issue](https://github.com/Jaan-Mustafa/10x-Team/issues).\n\n## License\n\nMIT\n",
  "bytes": 6445,
  "sha": "d64cba09d9a6efa190144f25c64914c6136431008d901f633cd9e7fe13019449",
  "repo_slug": "jaan-mustafa/10x-team",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_jaan_mustafa_10x_team_10x_team_60868e52/readme"
}