skill-workshop

Use when reviewing concrete backend implementation changes before merge or release for Design Realization and House-Style Conformance with accepted domain decisions, Tactical Design, and ddd-expert guidance.

Use when house-style backend coding must implement accepted Tactical Design, make an unambiguous mechanical change, or repair a Guard finding already covered by accepted authority.

Use when domain discovery must clarify a backend request before Tactical Design, either through scenario/lifecycle/rule analysis or language/authority/context-boundary analysis.

Use when a ddd-expert phase needs to inspect DDD artifacts or apply an already accepted artifact transaction; validates declared phase-operation compatibility, layout, templates, and model-design revisions without making domain or tactical decisions.

Use when Tactical Design must be created from accepted backend domain facts or an existing Tactical Design needs pre-code evaluation.

Use when a ddd-expert phase needs to inspect DDD artifacts or apply an already accepted artifact transaction; validates declared phase-operation compatibility, layout, templates, and model-design revisions without making domain or tactical decisions.

Use when explicitly maintaining Project Knowledge Base: user asks to ingest/refresh/repair memory, a task is at final handoff/commit/PR/merge, or the KB needs bootstrap or full-refresh

Use to health-check Project Knowledge Base without writing — reports stale references, shape violations, SSOT issues, retrieval cost, split candidates, and suggested ingest targets

Use when explicitly maintaining Project Knowledge Base: user asks to ingest/refresh/repair memory, a task is at final handoff/commit/PR/merge, or the KB needs bootstrap or full-refresh

Use to health-check Project Knowledge Base without writing — reports stale references, shape violations, SSOT issues, retrieval cost, split candidates, and suggested ingest targets

Use when writing tests, adding coverage, fixing flaky tests, reviewing test quality, choosing verification evidence, deciding between unit/integration/E2E/check/dry-run/smoke/manual validation, planning regression cases from architecture docs or sequence diagrams, preparing hand-off evidence, or reporting skipped/unrun/flaky verification risk. Covers business rules, state machines, APIs, async flows, service boundaries, mocking strategy, and evidence hand-off gates.

Use when writing tests, adding coverage, fixing flaky tests, reviewing test quality, choosing verification evidence, deciding between unit/integration/E2E/check/dry-run/smoke/manual validation, planning regression cases from architecture docs or sequence diagrams, preparing hand-off evidence, or reporting skipped/unrun/flaky verification risk. Covers business rules, state machines, APIs, async flows, service boundaries, mocking strategy, and evidence hand-off gates.

Use before designing, implementing, refactoring, or reviewing architecture, REST APIs, database schemas, backend services, DDD/Clean Architecture code, frontend React/Next.js code, or browser QA flows. Loads applicable design pattern standards and requires stating applicable, non-applicable, and conflicting patterns.

Use before designing, implementing, refactoring, or reviewing architecture, REST APIs, database schemas, backend services, DDD/Clean Architecture code, frontend React/Next.js code, or browser QA flows. Loads applicable design pattern standards and requires stating applicable, non-applicable, and conflicting patterns.

Use before exploring the codebase, planning, architecture decisions, broad search, or answering project questions — reads Project Knowledge Base and answers from it without writing