Skip to content
cccskills
FreePublished on GitHub

plan-interview

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

The English summary is being prepared. Showing the original description.

See how to install

Files included (7)

  • SKILL.md3.4 KB
  • references/example-spec.md11.0 KB
  • references/interview-techniques.md6.4 KB
  • references/phase-1-clarifications.md5.0 KB
  • references/phase-2-technical.md5.1 KB
  • references/phase-3-ux.md5.0 KB
  • references/phase-4-risks.md5.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

100+ animated React components (Aceternity UI) for Next.js with Tailwind. Use for hero sections, parallax, 3D effects, or encountering animation, shadcn CLI integration errors.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Oct 19, 2026

Secure API authentication with JWT, OAuth 2.0, API keys. Use for authentication systems, third-party integrations, service-to-service communication, or encountering token management, security headers, auth flow errors.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Oct 19, 2026

Creates comprehensive API changelogs documenting breaking changes, deprecations, and migration strategies for API consumers. Use when managing API versions, communicating breaking changes, or creating upgrade guides.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Oct 19, 2026

Verifies API contracts between services using consumer-driven contracts, schema validation, and tools like Pact. Use when testing microservices communication, preventing breaking changes, or validating OpenAPI specifications.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Oct 19, 2026

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Oct 19, 2026

Implements standardized API error responses with proper status codes, logging, and user-friendly messages. Use when building production APIs, implementing error recovery patterns, or integrating error monitoring services.

The English summary is being prepared. Showing the original description.

secondsky/claude-skills231Updated Oct 19, 2026

See all skills by secondsky

Report a problem with this skill