agentleFS
kv0906kv0906/pm-kit/.claude/skills/interview/SKILL.md

interview

Skill138 starsChanged 7 months agoMITView on GitHub

Interview user about a spec file and write detailed requirements. Use when user asks to "interview me about this spec", "brainstorm this PRD", "review spec with questions", or wants structured requirements gathering for a document.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 70 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask ONE focused question at a time

    line 45
  2. Distinctive:

    Wait for the user's response before asking the next question

    line 46
  3. Distinctive:

    Avoid obvious questions — dig into specifics and edge cases

    line 47
  4. Distinctive:

    After the interview is complete:

    line 67
  5. Distinctive:

    Write the finalized, enriched spec back to the original file

    line 69

“Common” is measured: kept by at least 6 in 10 of the 70 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interview - Spec Brainstorming

You are an interviewer who conducts in-depth, structured interviews about spec files to surface hidden requirements, edge cases, and design decisions.

Think step by step. Before asking any questions, first analyze the spec thoroughly.

Input

The user will provide a path to a spec file. Read it fully before beginning.

Interview Process

Conduct an in-depth interview about the spec. Ask non-obvious, probing questions across these dimensions:

Technical Implementation

  • Architecture decisions and tradeoffs
  • Edge cases and failure modes
  • Performance implications
  • Security considerations
  • Integration points with existing systems

UI/UX

  • User mental models and expectations
  • Accessibility requirements
  • Error states and recovery flows
  • Progressive disclosure needs

Business & Product

  • Success metrics and validation criteria
  • Phased rollout considerations
  • Backwards compatibility requirements

Constraints & Tradeoffs

  • Time vs quality tradeoffs
  • Build vs buy decisions
  • Technical debt implications

Rules

  1. Ask ONE focused question at a time
  2. Wait for the user's response before asking the next question
  3. Avoid obvious questions — dig into specifics and edge cases
  4. Challenge assumptions and explore alternatives
  5. Take notes on key decisions and rationale throughout

Pipeline

READ SPEC → ANALYZE → INTERVIEW (one question at a time) → SUMMARIZE → WRITE BACK
PhaseAction
1. ReadRead the spec file the user provides
2. AnalyzeIdentify gaps, ambiguities, and areas needing depth
3. InterviewAsk probing questions one at a time, wait for answers
4. SummarizeCompile all decisions and requirements
5. WriteUpdate the spec file with finalized requirements

Completion

After the interview is complete:

  1. Summarize all decisions and requirements discovered during the interview
  2. Write the finalized, enriched spec back to the original file

Download now (ZIP)

  • Other versions83 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 83

    1. claude-code-best/claude-code★ 23ksame name
    2. Q00/ouroboros★ 6.3ksame name
    3. Hisn00w/ASu-skills★ 6.1ksame name
    4. boshu2/agentops★ 450same name
    5. genkovich/sdd★ 187same name
    6. jvm-skills/jvm-skills★ 140same name
    7. tobieapb/claude-interactive-documentation-workflow★ 105same name
    8. panaversity/claude-code-skills-lab★ 57same name
    9. roman01la/skills-agents★ 48same name
    10. mehrad-dm/mastermind★ 23same name

    73 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use fetch-library-docs, contributor and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • Rehan-Ul-HaqSkill

      fetch-library-docs

      Fetches official documentation for external libraries and frameworks (React, Next.js, Prisma, FastAPI, Express, Tailwind, MongoDB, etc.) with 60-90% token savings via content-type filtering. Use this skill when implementing features using library APIs, debugging library-specific errors, troubleshooting configuration issues, installing or setting up frameworks, integrating third-party packages, upgrading between library versions, or looking up correct API patterns and best practices. Triggers automatically during coding work - fetch docs before writing library code to get correct patterns, not after guessing wrong.

      Also in 4 projects that use this

    • NimbleBrainIncSkill

      contributor

      Get started contributing to NimbleBrain open source — find an integration to build, set up your environment, propose an idea, or check on your work. Use when onboarding as a contributor. Triggers include "I'm a new contributor", "what should I build", "show me open issues", "file an issue".

      Also in 3 projects that use this

    • muhammad-anas35Skill

      skill-creator-pro

      Creates production-grade, reusable skills that extend Claude's capabilities. This skill should be used when users want to create a new skill, improve an existing skill, or build domain-specific intelligence. Gathers context from codebase, conversation, and authentic sources before creating adaptable skills.

      Also in 4 projects that use this

    • mjunaidcaSkill

      browsing-with-playwright

      Browser automation using Playwright MCP. Navigate websites, fill forms, click elements, take screenshots, and extract data. Use when tasks require web browsing, form submission, web scraping, UI testing, or any browser interaction. NOT when only fetching static content (use curl/wget instead).

      Also in 4 projects that use this

    • donatassimkusSkill

      offer

      Offer design, pricing strategy, and business model architecture. Invoke when asked about making an offer better, pricing a product or service, naming an offer, raising prices, generating fast cash, increasing lifetime value, finding the right customer, qualifying buyers, or designing a business model where customers pay for their own acquisition. Use when someone says their offer isn't converting, they need to charge more, they want to add bonuses or guarantees, or they need a money model for their business.

      Also in 3 projects that use this

    • galandoSkill

      teach-me

      Comprehension companion — incrementally teach the user every change, confirm mastery before advancing, and quiz to close gaps. Keeps the human engaged across all phases.

      Also in 7 projects that use this

  • In this repository41 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.