harness-ddd-question
Asks questions to clarify DDD structures. Use this to bridge gaps in event storming.
Install
mkdir -p .claude/skills/harness-ddd-question && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18836" && unzip -o skill.zip -d .claude/skills/harness-ddd-question && rm skill.zipInstalls to .claude/skills/harness-ddd-question
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
이벤트 스토밍에 없는 DDD 구조 매핑을 질문으로 만드는 L3 skill이다.Key capabilities
- →Identify structural mapping ambiguities in DDD
- →Formulate questions about DDD attributes and types
- →Formulate questions about DDD Entities and Value Objects
- →Formulate questions about DDD Behaviors and Aggregates
- →Formulate questions about Bounded Contexts and communication methods
How it works
This skill analyzes domain-driven design (DDD) structures to identify ambiguities in mapping concepts and generates clarifying questions.
Inputs & outputs
When to use harness-ddd-question
- →Clarify DDD aggregate definitions
- →Validate bounded context boundaries
- →Resolve ambiguity in domain modeling
About harness-ddd-question
Identifies ambiguity in domain model mappings and provides focused questions to resolve them. It uses event storming as a foundation for clarity.
이벤트 스토밍에 없는 DDD 구조 매핑을 질문으로 만드는 L3 skill이다.
When not to use it
- →When new business policies or success/failure criteria are needed
- →When implementation or technical strategy questions are asked
- →When the user asks for more than three questions at a time
Limitations
- →Limited to a maximum of three questions at a time
- →Does not address new business policies, success/failure criteria, or validation rules
- →Does not address implementation or technical strategy questions
How it compares
This skill provides specific questions to resolve DDD structural ambiguities, guiding the user towards clearer domain models compared to general discussions.
Compared to similar skills
harness-ddd-question side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| harness-ddd-question (this skill) | 0 | 14d | No flags | Advanced |
| brainstorming | 93 | 4mo | Review | Beginner |
| create-plan | 36 | 7mo | Review | Beginner |
| project-planner | 32 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by omegafrog
View all by omegafrog →You might also like
brainstorming
obra
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
create-plan
antinomyhq
Generate detailed implementation plans for complex tasks. Creates comprehensive strategic plans in Markdown format with objectives, step-by-step implementation tasks using checkbox format, verification criteria, risk assessments, and alternative approaches. Use when users need thorough analysis and structured planning before implementation, when breaking down complex features into actionable steps, or when they explicitly ask for a plan, roadmap, or strategy. Strictly planning-focused with no code modifications.
project-planner
adrianpuiu
Comprehensive project planning and documentation generator for software projects. Creates structured requirements documents, system design documents, and task breakdown plans with implementation tracking. Use when starting a new project, defining specifications, creating technical designs, or breaking down complex systems into implementable tasks. Supports user story format, acceptance criteria, component design, API specifications, and hierarchical task decomposition with requirement traceability.
confidence-check
SuperClaude-Org
Pre-implementation confidence assessment (≥90% required). Use before starting any implementation to verify readiness with duplicate check, architecture compliance, official docs verification, OSS references, and root cause identification.
system-design
lagz0ne
Use when designing, architecting, or planning a new system from requirements or ideas - transforms concepts into navigable design catalog using EventStorming methodology, Mermaid diagrams, and progressive elaboration through 5 phases (Requirements, Big Picture, Processes, Data/Flows, Integration)
spec-kit-workflow
jmanhype
Guides specification-driven development workflow. Automatically invoked when discussing new features, specifications, technical planning, or implementation tasks. Ensures proper workflow phases (specify → clarify → plan → checklist → tasks → analyze → implement).