---
title: "shode-house"
description: "Shode House: full expert team, scoped delivery, independent verification and resumable work."
canonical: https://agentpluginsdirectory.com/plugins/shode-house
last-updated: 2026-09-25
---

# shode-house
Shode House: full expert team, scoped delivery, independent verification and resumable work.
- Slug: shode-house
- Publisher: shode666
- Repository: https://github.com/shode666/claude-skill-shode-house
- Manifest: plugins/shode-house/plugin.json
- Version: 3.17.1
- Category (editorial): other
- Skills: 20 (api-contract, ask, automate-test, caveman, data-migration, decompose, dev-gate, diagnose, domain-core, drain, incident, review-checklist, secure, shode-house-deliverable, shode-house-discipline, shode-house-routing, shode-house-workflow, slo, ui-test, web-q)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-04-19
- Repository last pushed: 2026-09-24
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/shode-house
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What shode-house does, in the publisher's words

3.16.x: the full software house is back: ask is the single team entrypoint (Oliver in the main session), the original 19 roles and 23 skills are preserved (v3.17 consolidates them into 20 skills with no capability removed, see Skills below), and the same package installs on Claude Code, Codex, Cursor and Antigravity from plugins/shode-house. 3.16.1+ supersedes 3.16.0, which shipped a single-skill package without the team; the 3.16.0 tag and history are kept unchanged.

> Multi-Agent Software Engineering Operating System สำหรับ Claude Code / Cowork, > 19 agent ใน 7 ทีม ที่มี ownership ชัด, quality gate ที่ต้องมีหลักฐาน, token-aware context routing, > CI invariant ที่พิสูจน์ด้วย mutation test และ behavioral A/B eval

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/shode666/claude-skill-shode-house/HEAD/README.md

## Skills

- api-contract: Protect compatibility when changing a shared or public interface, such as a REST, GraphQL, gRPC, event or SDK contract with consumers outside the deploy unit, through breaking-change classification, versioning, deprecation and contract tests. Not for private function signatures or internal database…
- ask: Entry point for engaging the Shode House software team on consultation, design, implementation, review or resuming an engagement. Asking to explain or review does not authorize edits.
- automate-test: Set up a project's test automation strategy and infrastructure, meaning the mix of unit, integration and end-to-end tests, CI gates and thresholds. Not for the tests of a single change, one changed screen, or spikes and one-off scripts.
- caveman: Switch to an ultra-compressed reply style that drops filler but keeps technical terms, code, numbers and security warnings verbatim, only when the user explicitly asks for terse output. It is never the default and ends when the user asks for normal prose.
- data-migration: Plan and carry out a schema or data migration, such as DDL, backfill, dual write or expand-contract rollout, with rehearsed rollback and extra care for money and regulated data. Not for ordinary SQL queries, disposable local databases or a manual one-row production fix.
- decompose: Split an agreed, signed-off scope into small, independently verifiable outcome slices with owners, acceptance criteria and explicit dependencies. Not for work whose finished shape is still unclear, tasks already small, or a backlog already verified and ready.
- dev-gate: Apply test-first development and quality gates during implementation or refactor of production code, ending with validation evidence before handoff. Not for spikes, generated code, pure configuration changes, or investigating a problem whose cause is still unknown.
- diagnose: Debug an error, crash, failing test, wrong output, regression or slowdown (พัง, ไม่ทำงาน, ช้า, ทำไมถึง, bug) by reproducing and isolating the root cause before fixing. For live production impact, use incident.
- domain-core: Shared contract for domain expert personas, requiring an AI persona disclaimer and primary-source citations for any claim about a regulation, standard or protocol, and explicit marking when a source cannot be verified. It governs domain claims, not general project evidence or which expert is needed.
- drain: Batch-drain ready tickets with isolated workers, independent review, serial merge and evidenced closure (จัดงานที่พร้อม, ปิดงานค้าง). For work not split into concrete, independent tickets, use decompose.
- incident: Respond to active production impact such as an outage, degradation, data loss or breach by assigning severity and mitigating first, then a blameless postmortem. Not for bugs not currently hurting production users, nor planned maintenance.
- review-checklist: Coordinate independent review of an implemented change by code, runtime, spec, security and domain with severity and merge gates, not self-approval.
- secure
- shode-house-deliverable
- shode-house-discipline
- shode-house-routing
- shode-house-workflow
- slo
- ui-test
- web-q

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.