cascade-analyze-feature-scope

Feature scope analysis identifies and categorizes features from per-frame Figma analyses, epic context, and references into a structured view. It organizes features by user workflow to guide questions, shell stories, and Jira storytelling.

To group Figma frame analyses by user workflow, run the scope analysis process after all inputs are available. It consumes per-frame analyses and epic context to output a structured scope-analysis artifact with sections and evidence.

Yes, you can use Confluence and Google Docs references to guide feature scoping. The scope analysis process consumes epic context and reference materials alongside Figma frame analyses to generate a comprehensive scope map organized by user workflows.

The best way to translate Figma designs into structured Jira epics is automated scope analysis. It translates per-frame analyses and epic context into a structured view of features organized by user workflows for consistent downstream work.

Yes, you need per-frame Figma analyses before running scope analysis. The process requires all inputs, including frame analyses, epic context, and reference docs, to be available to generate the scope-analysis artifact.

Scope analysis needs to regenerate when inputs are refreshed to support self-healing updates. This ensures the scope-analysis artifact accurately reflects the latest per-frame analyses, epic context, and reference materials.