domain-teams

Plugin domain-teams from marketplace monkey-skills in kouko/monkey-skills. Commands read from the repo's manifest — 6 days ago.

Skills (11)

• code-team

  Develop code with primary-source gates (Clean Code / SOLID / TDD / Refactoring / OWASP ASVS / 徳丸本). Use to implement features, fix bugs, refactor, write TECH-SPEC.md / unit tests. Docs → docs-team; test strategy → qa-team; CI/CD → devops-team.

• copywriting-team

  Write persuasive marketing copy from Japanese advertising + Anglo persuasion psychology (PASONA / BEAF / QUEST / PASTOR). Use for landing-page headlines, email campaigns, キャッチコピー, sales letters, product copy, or audits. UI microcopy → design-team.

• design-team

  Design with accessibility and quality review. Use when designing UI, creating wireframes, planning UX strategy, or auditing accessibility. Delivers UI specs, wireframes, design docs. Code → code-team; product specs → planning-team.

• devops-team

  Ship code safely with CI/CD, containers, and IaC, grounded in Google SRE / DORA / 12-Factor. Use to design pipelines, write Dockerfiles, configure deployments, set SLIs/SLOs, or manage infra. App code → code-team; test strategy → qa-team.

• docs-team

  Write documentation and assess codebases with primary-source rigor (Diátaxis). Use for README, API docs, tutorials, how-tos, references, explanations, ADRs, or codebase-health audits. Code → code-team; product specs → planning-team.

• investing-team

  Make defensible investment decisions from primary-source frameworks. Use for Buy/Hold/Sell verdicts, equity memos, portfolio rebalancing, macro regime calls (Investment Clock), or TW equity analysis (三大法人). Business strategy → research-team.

• planning-team

  Cross-domain project planning (企画) from product canon (JTBD / Lean Startup / OKR / 4 Big Risks / BMC). Use when starting a project, defining scope, writing PRODUCT-SPEC.md, or direction changes. Technical specs → code-team; design → design-team.

• qa-team

  Plan and verify tests beyond unit level. Use to design E2E strategies, create test plans, analyze coverage gaps, or plan performance tests. Delivers TEST-PLAN.md + coverage reports. Writing test code → code-team; deployment → devops-team.

• research-team

  Primary-source research with citation verification + confidence calibration. Use for topic research, market/competitive analysis, tech-stack evaluation, OSS license audits, or literature review. Investment verdicts → investing-team; code → code-team.

• skill-team

  Build or modify domain-team skills with convention discipline — primary-source grounding, 3-commit split, 4-tier gates. Use when creating or refactoring a team skill. Generic Claude skills → superpowers:writing-skills.

• using-domain-teams

  Route to the right domain team. Use when starting any domain task — coding, documentation, testing, deployment, research, design, or planning. Do NOT use when you already know which team to invoke. ドメインチーム案内。領域團隊導引。

Subagents (2)

• evaluator

  Generic quality evaluator. Receives an artifact and a checklist or rubric, judges quality. Supports two modes: binary checklist (PASS/FAIL per item) and qualitative flags (red/yellow/green).

• worker

  Generic task executor. Receives a task description, optional protocol, and shared standards. Produces an artifact. Use for code implementation, test writing, documentation, refactoring, and research.

Similar plugins