elicit-requirementslisted

# Elicit Requirements — Structured Pre-Feature Clarification Run this before writing any new feature to avoid scope creep, missed edge cases, and mid-implementation discoveries that force rewrites. ## Elicitation Workflow Work through these sections with the user. Ask grouped questions — do not ask one at a time. --- ### 1. Problem Statement Ask: - What problem are we solving, and for whom? - What triggers this feature? (user action, external system push, scheduled job, webhook) - What is the expected outcome when it works correctly? - What is the expected behaviour when it fails? --- ### 2. User Roles and Stakeholders Ask: - Which user roles interact with this directly? (admin, developer, end user, external system) - Which roles are indirectly affected? (e.g., reports they see change, notifications they receive) - For integration features: which external system is involved? (identify from project context or ask) --- ### 3. Technical Constraints For integration or API features, always clarify: | Constraint | Questions | |---|---| | System | Which external system? | | Direction | INBOUND (system pushes to us) or OUTBOUND (we push to system)? | | Trigger | API call, webhook, scheduled job, file arrival? | | Data format | JSON? XML? CSV? Other? | | Auth | JWT? API key? mTLS? None (internal only)? | | Error handling | Retry? Dead-letter queue? Alert? Silent fail? | | Idempotency | Must duplicate calls be safe? | --- ### 4. Acceptance Criteria For each piece of fun