Fluent Commerce Logo
Docs

Feature Statuses Across Workspace

Use Case

Author:

Fluent Commerce

Changed on:

31 Mar 2026

Problem

Potential Problems:No consolidated view across concurrent features: When multiple features are in flight at the same time, understanding the status of each one requires opening individual files or relying on memory, which is error-prone and time-consuming.Features stalling without anyone noticing: Work that has been sitting in a planning state for days without progressing can easily go unnoticed until it becomes a delivery risk, particularly in busy teams juggling multiple workstreams.Skipped approval gates going undetected: A feature that has moved into active development without a formally approved plan represents a process gap that can lead to misaligned implementation and costly rework later.Broken dependencies between features: When one feature references another as its foundation, and that referenced feature no longer exists or has moved, the dependent feature can proceed on a false assumption without any warning.Slow session recovery after context switches: Returning to a workspace after time away requires reconstructing where each feature stands, which wastes time and increases the risk of resuming work in the wrong place or wrong order.No filtering or prioritisation across the feature backlog: Without the ability to quickly isolate features by status, identifying what needs immediate attention versus what is progressing normally requires manual review of every feature individually.
You have multiple features in various lifecycle stages and need a dashboard view.

Solution Overview

Getting a dashboard view of all features in a workspace begins with a single request that scans every feature tracked in the account and compiles their current state into a consolidated table. For each feature, this shows the retailer it belongs to, its overall lifecycle status, the state of its specification and plan, the revision number, and the next action required to move it forward. This gives an immediate, at-a-glance picture of the entire workspace without needing to open any individual feature files.The dashboard also automatically highlights items that warrant attention. Features that have been sitting in a planning state for more than a week are flagged, as are features that appear to have progressed into active development without a formally approved plan. Any features that reference a dependency on another feature that no longer exists are also surfaced, preventing work from continuing on an outdated assumption.When the full list is too broad, it can be filtered to show only the features in a particular state, making it straightforward to focus on what is actively in progress or what is blocked.The tool is entirely read-only, meaning it can be run at any point without any risk of affecting the environment or triggering any workflow. This makes it particularly well-suited as a starting point when returning to a workspace after time away, providing an accurate, up-to-date summary of where everything stands so work can resume confidently from the right place.

Solution