speclisted

Write a specification for: $ARGUMENTS Follow this workflow: 1. **Discovery**: ask the user clarifying questions before writing anything. Cover: - **Who** - who is the user/audience for this feature? - **What** - what exactly should it do? What is the expected behavior? - **Why** - what problem does it solve? What is the success metric? - **Constraints** - what technical, time, or scope constraints exist? - **Boundaries** - what is explicitly out of scope? - Ask **one question at a time**, waiting for the answer before asking the next. The list above is the topic checklist to cover across the discovery phase, not a batch to dump in one turn. See `rules/communication.md`. 2. **Draft the spec**: based on the answers, write a specification with these sections: ```markdown # Spec: <title> ## Problem Statement <What problem does this solve and for whom?> ## User Stories - As a <role>, I want <capability> so that <benefit> ## Acceptance Criteria - [ ] <Specific, testable criterion> - [ ] <Specific, testable criterion> ## Non-Functional Requirements - Performance: <latency, throughput targets> - Security: <auth, data handling requirements> - Accessibility: <WCAG level, specific requirements> ## Technical Constraints - <Stack, infrastructure, API compatibility requirements> ## Out of Scope - <Explicitly excluded from this work> ## Open Questions **why-not-mechanizable:** skill workflow guidance; each step requires understanding the surrounding context (rep