mapping-product-features
The mapping-product-features skill turns source evidence into a canonical feature map for a codebase. Use it when an agent needs a fresh inventory of product features, the code that implements them, and a shared record that gloria.dev can keep current.
Skill contract
| Field | Value |
|---|---|
| Slug | mapping-product-features |
| Purpose | Map end-user product features to the code that implements them. |
| Reads | The codebase, reachable product surfaces, and optional docs site vocabulary. |
| Writes | FEATURES.md by default; FEATURE_GAPS.md in docs-spider mode; feature records in gloria.dev when the run updates the feature inventory. |
| Canonical record | Feature entries with slug, name, description, layer, userFacing, aliases, structured details, files, symbols, docUrls, optional screenshots, and analyzedCommit. |
Triggers
The skill uses these trigger phrases:
| Trigger phrase | What it means |
|---|---|
map our product features | Build the feature map from source evidence. |
what features does this codebase implement | Identify the product features the code currently supports. |
build a feature map | Create the canonical feature inventory. |
sync features to gloria.dev | Refresh the shared feature inventory after a scan. |
which code implements <feature> | Map a feature back to the files and symbols that implement it. |
Outputs
It writes these local artifacts:
| Artifact | Mode | What it contains |
|---|---|---|
FEATURES.md | Default | The canonical feature map, grouped by layer and followed by per-feature detail, including structured detail such as What was built. |
FEATURE_GAPS.md | docs-spider | Gaps found while comparing the codebase with the docs site, including docs-only claims without code and code-backed features without docs coverage. |
When the app or docs site is reachable, the skill can also capture screenshots and attach the resulting references to feature records in gloria.dev. Screenshot capture stays optional, so the feature map still completes when those surfaces are unavailable or when the run skips screenshots.
Feature records
Each record keeps the feature inventory stable and searchable.
| Field | Meaning |
|---|---|
slug | Stable feature identifier in kebab-case. |
name | End-user feature name. |
description | Short explanation in user vocabulary. |
layer | Owning part of the product. |
userFacing | Whether people interact with it directly. |
aliases | Phrases a user might say to ask for it. |
details | Structured detail blocks, including What was built. |
files | Implementing file paths. |
symbols | Implementing exported symbols. |
docUrls | Docs pages that match the feature when a docs URL is supplied. |
screenshots | Optional screenshot references captured from the app or docs when those surfaces are reachable. |
analyzedCommit | The commit SHA used for the scan. |
Files and symbols stay sorted, and every entry must match the tree. Docs and product copy contribute vocabulary and coverage links, while screenshots add optional visual references when capture succeeds. Human-authored notes stay outside the fields the skill updates in gloria.dev, so reruns refresh the feature record without overwriting notes added in the dashboard.
Sync handoff
After the skill writes the local Markdown, it syncs the feature map into gloria.dev’s shared feature inventory. That handoff updates the shared feature record, includes any screenshot references the run captured, and removes stale entries so renamed or retired features do not linger. The sync leaves human-authored notes in place.