Feature Mapper

Overview

This skill transforms app exploration output into structured feature documentation with role-aware access details. It produces a feature matrix that maps feature availability and actions by role, then saves the result in a standardized artifact format. It can run from app-explorer artifacts or from manual feature descriptions provided by the user.

References

• references/chrome-mcp-compat.md
• references/output-format.md
• references/feature-categorization.md
• references/role-diff-algorithm.md

Prerequisites

• Input source is one of:
  • App exploration output under .claude/artifacts/exploration-*/
  • Manual feature descriptions supplied by the user
• This skill processes data only. It does not require browser automation and does not run Chrome MCP tools.

Input Detection

1. Check for exploration artifacts at .claude/artifacts/exploration-*/.
2. If found, read available exploration files and proceed with extraction.
3. If not found, request one of:
   • User runs app-explorer first, or
   • User provides manual feature descriptions
4. Accept both single-role and multi-role input:
   • Single-role: build features and role access for one role
   • Multi-role: build features plus role comparison output

Feature Extraction Workflow

Step 1: Read Input

• Parse exploration data fields such as pages, elements, and navigation_edges.
• For manual input, normalize into the same internal shape: page context, UI elements, and role labels when available.

Step 2: Group by Page

• Treat each page URL as a potential feature area.
• Merge closely related routes when they belong to one feature flow.

Step 3: Identify Features

• Group related UI elements into logical features.
• Example: user table + search input + create button + delete buttons -> User Management with sub-capabilities.

Step 4: Categorize

• Assign one primary category per feature using references/feature-categorization.md.
• Allowed categories: crud, form, dashboard, settings, search, auth, media, messaging, reporting, navigation, other.

Step 5: Extract Actions

• Derive action names from controls and semantics.
• Typical mappings:
  • Create button -> create
  • Search input -> search
  • Table/list -> view
  • Delete control -> delete
  • Save/edit flow -> edit

Step 6: Build Feature Entries

For each feature, produce:

• id: kebab-case stable identifier
• name: human-readable feature title
• description: concise purpose
• url: primary entry URL
• category: one allowed value
• actions: deduplicated action array
• ui_elements: mapped references to source elements
• roles: role-specific accessibility and available actions

Role-Based Analysis

When multi-role data is present, apply references/role-diff-algorithm.md:

1. Compare page inventories per role to identify exclusive and shared pages.
2. Compare element inventories for shared pages to detect role-only controls.
3. Compare actions per shared feature to identify permission differences.
4. Populate each feature's roles object:
   • accessible (boolean)
   • available_actions (array)
   • restricted_elements (array, optional)
5. Build role_comparison entries containing:
   • exclusive features per role
   • shared features
   • action differences

If only one role is available, skip pairwise role comparison and mark all extracted features against that role only.

Iterative Refinement Loop

1. Present the initial feature map draft.
2. Ask: Does this look correct? Should I add, modify, or remove any features?
3. If user updates are provided, revise feature boundaries, categories, actions, or role mappings.
4. Re-present until approved.
5. Save final output once approved.

Output

• Save output to .claude/artifacts/feature-map-{timestamp}/.
• Follow references/output-format.md schema exactly.
• Ensure IDs are kebab-case and stable because downstream tool generation depends on them.

Troubleshooting

• No exploration data found: ask user to run app-explorer or provide manual feature descriptions.
• Unclear feature boundaries: fall back to URL-based grouping (each unique page path as one feature area).
• Single role only: skip role comparison; keep role access populated for the available role.

Scope Guardrails

• Do not perform accessibility auditing.
• Do not generate test cases.
• Do not re-explore the application.
• Do not invoke browser tools from this skill.