메뉴
Investigate why code was written a certain way. Use when tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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-archaeology |
| description | Investigate why code was written a certain way. Use when tracing decision history through git blame, commit logs, PRs, and issues to understand the reasoning behind code changes. |
| allowed-tools | ["Bash(git log:*)","Bash(git show:*)","Bash(git blame:*)","Bash(git diff:*)","Bash(gh pr list:*)","Bash(gh pr view:*)","Bash(gh issue list:*)","Bash(gh issue view:*)","Bash(gh search:*)","Bash(gh api:*)","Read","Grep","Glob"] |
Read-only operations only.
For gh api: GET requests only. No -X POST/PUT/PATCH/DELETE or -f/-F flags.
git blame → introducing commit#123 referencesFor detailed commands: See references/commands.md
git blame -L <start>,<end> <file> # Find who changed lines
git log -S "code" --oneline # Find when code was added
gh pr list --search "<sha>" --state all # Find PR for commit
## Decision Archaeology Report
### Target
- File: [path/to/file]
- Lines: [XX-YY]
### Timeline
#### [Date] Commit: [short-sha]
- Author: [name]
- Message: [commit message]
- PR: #[number] [title]
- Related Issue: #[number]
### Decision Rationale
[Summary of why, based on PR discussions, issue context, commit messages]
### Key References
- PR #[number]: [URL]
- Issue #[number]: [URL]
- Commit: [sha]
git blame to find introducing commit#123 references