Gather Requirements Before Building - AI Skills
How-to Guide
Author:
Fluent Commerce
Changed on:
31 Mar 2026
Key Points
[Warning: empty required content area]Prerequisites
Steps
Fluent Use Case Discovery
Situation: Product says "we need curbside pickup" but there are no structured requirements, use cases, or entity definitions.Prompt:
Output: A Business Spec saved to
`Help me define the use cases for curbside pickup``/fluent-use-case-discover` runs an interactive wizard through 10 phases:| Phase | What happens | Output |
| 1. Scope | Define the feature boundary — what's in, what's out | Scope statement |
| 2. Actors | Identify who interacts (customer, store staff, OMS, WMS) | Actor registry |
| 3. Use cases | Walk through each user journey step by step | Structured use case list |
| 4. Environment discovery | Query live environment for existing workflows, rules, entity types (requires connected profile) | Available infrastructure |
| 5. Entity model | Define entities, subtypes, and relationships | Entity relationship diagram |
| 6. Status lifecycles | Map statuses per entity with allowed transitions | State machine diagrams |
| 7. Business rules | Capture validation rules, constraints, edge cases | Rules inventory |
| 8. Integration points | Webhooks, external systems, scheduled jobs | Integration map |
| 9. Settings | Required configuration keys and values | Settings inventory |
| 10. Gap analysis | Compare requirements against existing environment | Completeness score |
`accounts/<PROFILE>/features/curbside-pickup/spec.md` with a completeness score (0-100%). Specs scoring >= 75% can proceed directly to `/fluent-feature-plan`.
