fellowship-dev/dogfooded-skills

spec-plan

Use when stress-testing a plan, getting grilled on a design, or before writing a PRD.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/fellowship-dev/dogfooded-skills --skill spec-plan

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

<!-- 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:

bash
gh issue view ISSUE_NUMBER --repo ORG/REPO --json body,title,comments

Read 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:

bash
cat project-instructions.md  # or equivalent project instructions file
cat README.md

2. 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:

text
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

Related by task

from this repository

More skills

All skills