spec-interview

深度访谈以完善技术规格或用户指定的文档说明书。当存在 plan.md 或者用户指定文档需要通过系统性提问来完善需求时使用,涵盖技术实现、UI/UX设计、边缘情况、风险考量、权衡取舍和架构决策。触发词包括"帮我完善这个plan"、"问我关于项目的问题",或当草稿规格需要全面细化时。

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 9, 2026

When & Why to Use This Skill

The spec-interview skill acts as a virtual technical architect that transforms vague project drafts into comprehensive, production-ready technical specifications. By conducting deep, systematic interviews, it probes into technical implementation details, UI/UX requirements, edge cases, and architectural trade-offs, ensuring that the final documentation is robust and minimizes development risks.

Use Cases

  • Requirement Refinement: Transform a brief 'plan.md' or a rough project idea into a detailed technical specification by answering targeted questions about system behavior and constraints.
  • Edge Case Discovery: Identify potential technical debt and overlooked scenarios early in the design phase through probing questions that challenge the initial project scope.
  • Architectural Decision Making: Use the interview process to evaluate and document the rationale behind specific technology stacks, trade-offs, and system architectures before writing a single line of code.
  • UI/UX Alignment: Ensure the technical backend aligns with user experience goals by detailing interface interactions and design requirements during the specification phase.
namespec-interview
description深度访谈以完善技术规格或用户指定的文档说明书。当存在 plan.md 或者用户指定文档需要通过系统性提问来完善需求时使用,涵盖技术实现、UI/UX设计、边缘情况、风险考量、权衡取舍和架构决策。触发词包括"帮我完善这个plan"、"问我关于项目的问题",或当草稿规格需要全面细化时。

规格访谈技能

通过深入、探究式的访谈,将草稿规格说明转化为完整的技术文档。

阅读 plan.md 或者用户指定文档,并使用 AskUserQuestionTool 对我进行详尽的访谈。访谈内容可以涵盖任何方面:技术实现、UI 与 UX、潜在顾虑、权衡取舍等,但请确保提出的问题具有深度,而非显而易见。

请保持深度并持续提问,直到访谈完全结束,最后将完善后的规格说明(spec)写入该文件中。