Build a Complete Feature End-To-End - Fluent AI Skills
How-to Guide
Author:
Fluent Commerce
Changed on:
31 Mar 2026
Key Points
[Warning: empty required content area]Prerequisites
Steps
Gather Requirements (If Unclear)
`Help me define the use cases for a Return Order feature`The
`/fluent-use-case-discover` wizard runs through 10 phases: - Entity types involved (ORDER, RETURN_ORDER, FULFILMENT) - Business rules (return window, item eligibility, refund policies) - Status lifecycles per entity - Integration points (WMS, ERP, payment gateway) - Environment discovery (if profile connected)Produces a Business Spec saved to `accounts/<PROFILE>/features/return-order/spec.md` with a completeness score.Plan the Feature
`Plan the Return Order feature``/fluent-feature-plan` checks the spec (must be >= 75% completeness), then produces an 18-section plan: - Architecture diagrams (Mermaid state machines + sequence diagrams) - Workflow changes with before/after - Rules inventory: NEW rules get pseudo-logic contracts, OOTB rules get prop configuration - Settings, webhooks, cross-entity impacts - Every artifact tagged as NEW / EXISTING / MODIFIED / REUSED / OOTB - Deployment sequence, risk assessment, test planPlan saved to `accounts/<PROFILE>/features/return-order/plan.md`.Waits for your approval. You can ask questions, request changes, or approve.Your workspace after steps 1-2:`accounts/<PROFILE>/features/return-order/`status.json ← status: PLANNING, plan: PENDING (or APPROVED after you approve)
spec.md ← business requirements with completeness score
plan.md ← 18-section implementation plan with Mermaid diagrams
assets/ ← screenshots, recordings, visual evidence (linked from spec/plan)
You can close your IDE here. When you come back, the AI reads
`status.json`, sees `plan: "APPROVED"` and `next: "/fluent-rule-scaffold"`, and picks up at Step 3.Scaffold the Module (If New)
`Create a new module called my-returns``/fluent-module-scaffold` generates the full Maven project: POMs, `module.json`, directory structure, build scripts, `.gitignore`.Scaffold Custom Rules
`Create the rules from the plan``/fluent-rule-scaffold` generates each rule from the plan: Java class with SDK boilerplate, test skeleton, wired into `module.json`. Each rule emits `-> READY: <path>` and `-> NEXT: /fluent-build` on completion.Generate or Repair Rule Tests
`Generate tests for ValidateReturnWindow``/fluent-rule-test` generates comprehensive JUnit 5 tests for existing rules: happy path, edge cases, error scenarios, and mock setups. If tests already exist but are broken, it diagnoses and repairs them. Uses `RuleExecutor` or `TestExecutor` patterns from `rule-test-patterns.md`.Build the Workflow
`Build the RETURN_ORDER::DEFAULT workflow from the plan``/fluent-workflow-builder` creates the workflow JSON with rulesets, states, triggers, and validates all references. Then `/fluent-workflow-analyzer` runs automatically to catch orphaned rulesets or trigger conflicts.Build and Package
`Build the module``/fluent-build` bumps the version, runs `mvn clean install`, packages the ZIP. If compilation fails, reports the error and suggests fixes.Pre-Deploy Quality Gates
`Run pre-deploy checks``/fluent-pre-deploy-check` runs 35+ gates across 9 phases: environment readiness, module integrity, workflow validity, connection topology, settings completeness, target verification, risk assessment, completeness, and frontend bundle. Reports READY or BLOCKED with specific blockers.Deploy Module + Workflow
`Deploy everything to MY_RETAILER``/fluent-module-deploy` installs the module ZIP. `/fluent-workflow-deploy` uploads the workflow JSON (tries MCP first, falls back to REST API). Both verify the deployed version matches.End-to-End Test
`Run the E2E test from the plan``/fluent-e2e-test` creates test entities dynamically (using `/fluent-test-data` discovery), fires events at each step, polls for status transitions, and reports pass/fail per step. On failure, automatically traces the failed event to find the root cause.Fix Loop (If Needed)
If a test fails, the agent diagnoses the issue (wrong prop value? missing setting? rule bug?), applies the fix, rebuilds, redeploys, and re-tests. This loop continues until all tests pass or an unresolvable blocker is hit.
