map-feature-scope

Feature scope decomposition breaks a broad feature into bounded sub-features by identifying main surfaces, routes, and entry points to enable parallel exploration. You provide a target URL and feature description to generate a feature map and an e2e-plan outline.

You need feature scope mapping when a requested feature spans multiple routes, tabs, overlays, roles, or primary interactive surfaces. It identifies bounded exploration units, shared state, and blockers before spawning parallel browser subagents.

To generate an e2e-plan outline, provide a target URL and feature scope. The skill maps the feature into bounded sub-features with entry points and dependencies, creating a plan scaffold for downstream browser subagents to run in parallel.

Feature scope decomposition only produces the feature map and e2e-plan outline; it does not generate the final deep exploration evidence, coverage plan, or test specs. It strictly identifies surfaces, blockers, and shared state for downstream tasks.

Yes, scope decomposition applies directly to features spanning routes, tabs, overlays, and roles. It identifies candidate sub-features with entry points and dependencies to set exploration boundaries for parallel execution.

No, feature scope decomposition does not produce final deep exploration evidence, coverage plans, or test specs. It only generates a plan scaffold and feature map to prepare downstream browser subagents for parallel exploration.