원클릭으로
ds-grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Interview the user relentlessly about a plan or design until reaching shared understanding.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Design a target architecture for a new system — module boundaries, dependency rules, seams, and build order — from its requirements. Reports a blueprint; changes nothing.
Analyze an existing codebase's architecture and produce a sequenced refactoring plan — assess module boundaries, dependency structure, and layering, then lay out ordered, risk-tagged steps. Language-agnostic. Reports a plan; changes nothing.
Turn a goal or another command's output into an ordered task roadmap.
Find the root cause of a failure with the scientific method — reproduce, isolate, fix, then prove it.
Run an extremely strict maintainability + single-source-of-truth review of code changes — abstraction quality, file sprawl, spaghetti-condition growth, and duplicate/competing implementations. Reports findings by default; `--fix` applies the mechanical, unambiguous ones — structural/code-judo restructurings rest on judgment and stay reported.
Drive implementation with tests, one vertical slice at a time.
| name | ds-grill-me |
| description | Interview the user relentlessly about a plan or design until reaching shared understanding. |
| disable-model-invocation | true |
When invoked, stress-test every aspect of the plan. Walk down each branch of the decision tree, resolving dependencies between decisions one at a time.
If invoked with --record, append each resolved decision worth keeping to .project/DECISIONS.md if .project/ exists, else DECISIONS.md in the current directory, as the interview proceeds. Record the ones that are hard to reverse, surprising without context, or the product of a real trade-off — skip the trivial and the self-evident. One entry per decision: the question, the chosen answer, and a one-line rationale. Plain Markdown, no fixed schema. Without the flag, keep decisions in the conversation only.
End when no unresolved decision branches remain. Summarize the resolved plan. If --record was passed, also report the path to the updated DECISIONS.md.