domain
Domain Model Cooking Session
Interview relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.
Ask questions one at a time, waiting for feedback before continuing.
If a question can be answered by exploring the codebase, explore the codebase instead of asking.
Discover project context
Before starting, find and read existing domain documentation. Check these locations (in order):
docs/CONTEXT_MAP.md— if it exists, this is a multi-context project. Read it to understand bounded contexts and their relationships.docs/UBIQUITOUS_LANGUAGE.md— the shared glossary. Read it to understand canonical terms.docs/contexts/*/CONTEXT.md— per-context documentation. Read the ones relevant to the current plan.CLAUDE.md— project-level context.
If none of these exist, that's fine — create them lazily as decisions are made (see below).
More from agentivestack/skills
holistic
Zoom out to see how code, features, or plans fit into the bigger picture. Maps bounded contexts, traces cross-cutting concerns, surfaces hidden dependencies, and identifies systemic risks. Use when you're lost in details, unfamiliar with an area, or need to understand the full impact of a change.
14architect
Surface architectural friction in the codebase and design better module interfaces. Uses parallel sub-agents to explore radically different interface designs. Based on "deep modules" philosophy — small interfaces hiding significant complexity. Use when code feels tangled, hard to test, or hard to navigate.
14tdd
Implement a feature or fix using pragmatic test-driven development. Tracer-bullet approach — one test, one implementation, repeat. Tests verify behavior through public interfaces, not implementation details. Use when implementing a slice from /slice or any work that needs tests.
13slice
Break a spec, plan, or feature into independently-implementable vertical slices (tracer bullets). Each slice cuts through all layers end-to-end. Outputs a task list or GitHub issues. Use after /spec to plan implementation order.
13qa
Interactive QA session where you describe bugs conversationally and the agent files durable GitHub issues using the project's domain language. Explores the codebase in the background for context. Use when reporting bugs, doing QA testing, or filing issues from observations.
13spec
Interview the user to produce a feature spec (PRD), grounded in the project's domain model, context map, and ubiquitous language. Outputs a structured spec document. Use when starting a new feature, enhancement, or significant change.
13