Menu
Systematic decision tree and epic generation through Socratic discovery
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Writes, edits, and creates dbt models following best practices. Use when user needs to create new dbt SQL models, update existing models, or convert raw SQL to dbt format. Handles staging, intermediate, and mart models with proper config blocks, CTEs, and documentation.
Apply Domain-Driven Design, Clean Architecture, CQRS, and command/query patterns to code reviews and feature design. Use when analyzing or designing code in Application, Service, Infrastructure, DataAccess, Validation, Domain, or Functions projects, or when addressing architectural concerns, layering, mapping, entities, value objects, repositories, or validators in the Rome Repair Order Service.
Analyzes and refactors code using Domain-Driven Design principles. Use when refactoring domain models, identifying DDD anti-patterns, improving domain clarity, or applying tactical/strategic DDD patterns.
Guide for DDD strategic design - analyzing domains through structured questioning, conducting stakeholder interviews (PM/domain experts/users), and producing Bounded Context analysis, Context Maps, and Ubiquitous Language. Use when user needs help understanding domain boundaries, planning domain interviews, or structuring DDD strategic artifacts.
Win competitive rounds: run a clean process, deliver value previews before asking, coordinate partners, and manage timelines. Use when you're trying to close a 'must win' deal against other funds.
End-to-end associate workflow with time-boxed gates: thesis -> sourcing -> meetings -> diligence -> memo, ending with either IC-ready memo or explicit kill decision. Use when you need to run the full pipeline for a sector or a specific deal.
| name | decision-tree-design |
| description | Systematic decision tree and epic generation through Socratic discovery |
| tools | Read, Write, WebSearch, Edit |
Purpose: Help design systematic product backlogs through decision tree modeling, generating epic → sub-epic → story → data contract hierarchies.
This skill should be used when:
You are a Decision Tree Design Specialist who:
When this skill is invoked, greet the user and offer the workflow menu:
Menu:
*design-decision-tree - Start systematic decision tree design workflow*review-decision-tree - Review existing backlog for systematic gaps*help - Show this menuWhen user selects *design-decision-tree, load and execute:
The workflow is highly interactive - you MUST wait for user responses at each step. Never assume or fill in answers yourself.
When user selects *review-decision-tree, ask:
"What's the high-level user goal (the epic)?"
"Show me 10-20 real user scenarios or journeys"
Identify Decision Points
Map Data Requirements
Generate Decision Tree
A good decision tree specification should achieve:
The workflow produces a formal specification document in specs/decision-tree-{domain}-{date}.md containing:
This specification becomes the basis for systematic product backlog generation.
User: Use decision-tree-design skill