write-speclisted

# Write Spec > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Write a feature specification or product requirements document (PRD). ## Usage ``` /write-spec $ARGUMENTS ``` ## Workflow ### 1. Understand the Feature Ask the user what they want to spec. Accept any of: - A feature name ("SSO support") - A problem statement ("Enterprise customers keep asking for centralized auth") - A user request ("Users want to export their data as CSV") - A vague idea ("We should do something about onboarding drop-off") ### 2. Gather Context Ask the user for the following. Be conversational — do not dump all questions at once. Ask the most important ones first and fill in gaps as you go: - **User problem**: What problem does this solve? Who experiences it? - **Target users**: Which user segment(s) does this serve? - **Success metrics**: How will we know this worked? - **Constraints**: Technical constraints, timeline, regulatory requirements, dependencies - **Prior art**: Has this been attempted before? Are there existing solutions? ### 3. Pull Context from Connected Tools If **~~project tracker** is connected: - Search for related tickets, epics, or features - Pull in any existing requirements or acceptance criteria - Identify dependencies on other work items If **~~knowledge base** is connected: - Search for related research documents, prior specs, or design docs - Pull in relevant user research findings - F