tech-spec-writer

This skill follows engineering-doctrine and structured-workflow.

Interview (Required)

Before drafting the spec, interview the user to clarify requirements and intent:

• Ask focused questions about goals, scope, constraints, and success criteria.
• Confirm the intended users, workflows, and non-goals.
• Summarize the understanding and get explicit confirmation before writing the spec.

Output Requirements

• Markdown
• Explicit assumptions and open questions
• All requirements testable
• Tables preferred over prose

Required Sections (DO NOT OMIT)

1. Title Page
2. Purpose and Scope
3. Background and Context
4. Assumptions and Constraints
5. Functional Requirements
6. Non-Functional Requirements
7. Architecture Overview
8. Data Models
9. APIs / Interfaces
10. Error Handling
11. Testing Strategy
12. Open Questions

Specifications must be review-proof and suitable for long-term maintenance.