What problem does it solve? Product areas in DefProd often exist without documented user stories, leaving teams without a shared, testable definition of what the software actually does. This Skill reverse-engineers the implemented capabilities of a single product area from the source code and writes them as structured user stories with acceptance criteria via the DefProd MCP server. ## Core Features & Use Cases - Codebase-driven research: Maps an area to its routes, controllers, services, tests, and UI components, then builds a capability matrix of entities, verbs, and variants that acts as a required coverage checklist. - Granularity-enforced story creation: Generates one story per acceptance-test cluster with canonical personas from the product brief, user-observable acceptance criteria, and sequential area-prefixed keys (e.g. AUTH-01). - Add-more and decomposition modes: Detects existing stories, offers add/replace/cancel options, and can split coarse existing stories into fine-grained replacements with tombstoning of retired parents. - Use Case: After defining a BILLING area in DefProd, run the skill against your repo to produce 15-35 verified stories covering listing, editing, state transitions, and permission variants, each ready to drive automated tests. ## Quick Start Ask your AI agent to run /defprod-create-area-stories for your product name and area key, for example: create area stories for the Billing area of my product.