사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/fellowship-dev/dogfooded-skills --skill spec-plan시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
<!-- Original "grill me" concept by Matt Pocock (https://x.com/maaboroshi) -->
spec-plan
Interview the user relentlessly about every aspect of a plan until reaching shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one by one.
When to Use
- User wants to stress-test a plan or design
- User says "grill me" or "poke holes in this"
- Before running
issue-to-prd— spec-plan resolves ambiguity, issue-to-prd structures the output - Complex feature with many interacting decisions that need to be resolved sequentially
When NOT to Use
- Requirements are already clear and documented — go straight to
issue-to-prd - User just wants a quick opinion, not a deep interview
- Implementation is already underway
Workflow
1. Read existing context
If the plan originates from a GitHub issue:
gh issue view ISSUE_NUMBER --repo ORG/REPO --json body,title,commentsRead all comments too — treat existing questions and answers as already-resolved branches. Do not re-ask anything already answered.
If no issue, read project context:
cat project-instructions.md # or equivalent project instructions file
cat README.md2. Interview — one question at a time
For each branch of the design tree:
- Ask one question
- Provide your recommended answer with reasoning
- Wait for the user's response
- Incorporate the answer and move to the next branch
Warning: ONE question at a time. This is not issue-to-prd's batched Q1-Qn format. Go deep on each branch before moving to the next.
If a question can be answered by exploring the codebase, explore the codebase instead of asking.
3. Resolve dependencies
When decisions depend on each other, resolve the dependency first:
- Identify which decision blocks others
- Ask about the blocker first
- Then proceed to the dependent decisions
4. Handoff to issue-to-prd (optional)
When all branches are resolved, offer:
All branches resolved. Want me to run issue-to-prd to structure this into a PRD?If yes, the shared understanding from this interview becomes the input; issue-to-prd can skip its clarity assessment and go straight to drafting.
Critical Rules
- One question at a time — depth over breadth
- Always provide your recommended answer — don't just ask, propose
- Never re-ask resolved questions — read issue comments first
- Explore code before asking — if the codebase has the answer, use it
- Start from where the conversation left off — respect prior discussion





