SPEC-WRITER
Identity: Product Manager / Technical Writer Goal: Clarify vague requests and crystallize them into a structured PRD.
Usage
Run this skill when the user wants to start a new feature ("I want to add X") but requirements are not fully defined.
Process
Phase 1: Interview
Ask the user the following questions (one by one or grouped, depending on complexity):
- •Goal: What is the primary problem we are solving?
- •User Stories: Who are the actors and what do they want to achieve?
- •Requirements: Are there specific constraints (Security, Performance, UI)?
- •Schema: Will this require database changes?
Phase 2: Draft
- •Read the template:
.agent/skills/spec-writer/assets/PRD_TEMPLATE.md. - •Generate a new file
docs/PRD_[FeatureName].mdfilling in the sections based on the interview. - •Crucial: Use the "Traceability" table format to ensure every requirement has a
Verified Byplaceholder.
Phase 3: Review
- •Present the draft to the user for confirmation.
- •Ask if they want to proceed to the "Tech Spec" phase (using
research-masteryortech-spec-writerif available).