Skip to content

secondsky/claude-skills / plugins/plan-interview/skills/plan-interview

plan-interview

Unverified

Adaptive interview-driven spec generation. Use when converting rough plans into comprehensive specifications, needing structured requirements gathering, or transforming ideas into implementation-ready documentation.

Plan Interview Skill

Transform rough plans into comprehensive, implementation-ready specifications through adaptive, structured interviews.

When to Use

  • Converting a plan or idea into a detailed specification
  • Gathering requirements through structured questioning
  • Transforming rough documentation into implementation-ready specs
  • Ensuring all edge cases, risks, and stakeholders are considered before implementation

Available Components

Command: /plan-interview:interview [plan-file]

Adaptive interview that calibrates depth based on plan complexity:

ComplexitySignalsQuestions
SimpleSingle feature, clear scope10-15
ModerateMulti-component, some integrations18-23
ComplexCross-system, many stakeholders22-28

Usage:

/plan-interview:interview docs/feature-plan.md
# Output: docs/feature-plan-spec.md

Agent: spec-reviewer

Autonomous quality analysis of specifications across 4 dimensions:

  • Completeness (25 pts) - All sections populated?
  • Consistency (25 pts) - No contradictions?
  • Clarity (25 pts) - No ambiguous language?
  • Edge Cases (25 pts) - Error handling defined?

Triggers when you say "review my spec" or "check specification quality".

Interview Phases

  1. Foundations & Scope - Stakeholders, success criteria, constraints, MVP scope
  2. Technical Deep-Dive - Architecture, data models, scalability, security
  3. User Experience - Personas, flows, cognitive load, error recovery
  4. Risks & Tradeoffs - Risk categorization, blast radius, contingency plans
  5. Operationalization - Testing, deployment, monitoring
  6. Wrap-Up (optional) - Only for complex plans with remaining gaps

Interview Philosophy

Core Principle: Depth over breadth. Better to deeply understand critical aspects than superficially cover everything.

Key Techniques:

  • Non-obvious questions - Skip what the plan already answers
  • Edge probing - What happens in unusual cases?
  • Assumption surfacing - Make implicit beliefs explicit
  • Contradiction detection - Flag when answers don't align
  • Adaptive depth - Probe deeper on complex areas, move faster on clear ones

Spec Output Structure

Generated specs include:

  • Overview (problem, solution, success criteria, stakeholders)
  • Functional and non-functional requirements
  • Technical design (architecture, data models, APIs, security)
  • User experience (personas, flows, states, edge cases)
  • Risks and mitigations (risk register, tradeoffs, contingency plans)
  • Implementation notes (key decisions, dependencies, migration)
  • Operationalization (testing, deployment, monitoring)
  • Open questions and out-of-scope items
  • Phasing (MVP vs future)

References

Load these for deeper guidance during interviews:

  • references/phase-1-clarifications.md - Foundations questions and pitfalls
  • references/phase-2-technical.md - Architecture discussion patterns
  • references/phase-3-ux.md - Persona development, UX patterns
  • references/phase-4-risks.md - Risk assessment frameworks
  • references/interview-techniques.md - Cross-cutting interview skills
  • references/example-spec.md - Annotated high-quality spec example
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 463kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 196kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 196kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 196kUpdated Claude CodeCodexVerifiedInstall