Fluent Commerce Logo
Docs

Map What's Been Built on an Account - Fluent AI Skills

How-to Guide

Author:

Fluent Commerce

Changed on:

31 Mar 2026

Key Points

[Warning: empty required content area]

Steps

Step arrow right iconFeature Inventory Generation

Situation: You're onboarding to a new Fluent Commerce account and need to understand the full implementation — what features exist, how they connect, and where the gaps are.Prompt:
`What has been built here? Give me a feature inventory`
`/fluent-implementation-map` runs a 5-phase analysis:
  • Inventory Collection — queries workflows (`workflow_list`), custom rules (`plugin_list`), settings (`graphql_query`), and local source code to build the raw inventory
  • Feature Identification — clusters workflows into logical features using subtype alignment, cross-entity events, shared custom rules, and naming conventions
  • Flow Mapping — traces cross-feature dependencies and generates Mermaid diagrams (feature dependency graph + entity lifecycle sequence)
  • Gap Analysis — identifies missing workflows, orphaned rules, webhook health issues, dead-end risks, and OOTB coverage gaps
  • Report Generation — produces the master document plus per-feature summaries

Step arrow right iconFeature Output

Output at `accounts/<PROFILE>/analysis/implementation-map/`:
`implementation-map.md              ← Master document with executive summary, feature table, diagrams`
inventory.json                     ← Machine-readable inventory (workflows, features, gaps, modules)
gaps.md                            ← All identified gaps with severity and remediation
features/
 home-delivery.md                 ← Per-feature summary with workflows, rules, webhooks
 click-collect.md
 inventory-management.md
 ...
diagrams/
 feature-dependency.mmd           ← Cross-feature dependency flowchart
 entity-flow.mmd                  ← Entity lifecycle sequence diagram

Each feature gets a customisation depth score (0-4: OOTB → Configured → Extended → Custom → Bespoke) and a confidence rating (HIGH/MEDIUM/LOW) based on evidence quality.Read-only — no planning gate, no environment changes. Great as a first step before `/fluent-feature-explain` on specific features.