@fluentcommerce/ai-skills 0.1.0 → 0.2.0

package/content/dev/skills/fluent-pre-deploy-check/SKILL.md

@@ -8,13 +8,13 @@ argument-hint: [--profile <profile>] [--retailer <ref>] [--module-path <path>] [
 
 # Pre-Deployment Checklist
 
-Structured deployment gate between "build passes" and "deploy to retailer." Runs 8 phases of validation with 26 individual quality gates, producing a machine-readable pass/fail report that blocks deployment on critical failures.
+Structured deployment gate between "build passes" and "deploy to retailer." Runs 8 phases of validation with 25 individual quality gates, producing a machine-readable pass/fail report that blocks deployment on critical failures.
 
 This skill is the final checkpoint in the Agent-Driven Development (ADD) lifecycle, positioned at Phase 6 (Demo Deployment). It aggregates validation from multiple specialized skills and MCP tools into a single, traceable pre-flight report.
 
 ## Planning Gate
 
-**This skill IS the planning gate for deployment.** Running a pre-deploy check is always safe (read-only analysis). No approval needed to run the check itself. However, if the check result includes a GO verdict and the user asks to proceed with deployment, the deployment skills (`/fluent-module-deploy`, `/fluent-workflow-deploy`) have their own planning gates that apply.
+**This skill IS the planning gate for deployment.** Running a pre-deploy check is always safe (read-only analysis). No approval needed to run the check itself. However, if the check result includes a GO verdict and the user asks to proceed with deployment, the deployment skills (`/fluent-module-deploy`, `/fluent-workflow`) have their own planning gates that apply.
 
 ## Ownership Boundary
 
@@ -91,23 +91,6 @@ Phases are auto-skipped when their inputs are unavailable. The `--skip` flag for
 
 Verify the target environment is accessible, correctly configured, and capable of receiving a deployment.
 
-#### Gate 1.0: CLI Available
-
-**Severity:** HIGH
-
-**Tool:** Bash (`fluent --version`)
-
-**Invocation:**
-```bash
-fluent --version
-```
-
-**Pass criteria:** Command succeeds and returns a version string (e.g., `v2.0.0`).
-
-**Fail criteria:** Command not found or returns an error. Many deployment operations (module install, workflow list/download, verification) require the Fluent CLI. HIGH rather than CRITICAL because MCP tools can handle some operations without CLI, but the standard deployment path requires it.
-
-**Details captured:** CLI version string, CLI path (from `which fluent` or `where fluent`).
-
 #### Gate 1.1: Authentication Valid
 
 **Severity:** CRITICAL
@@ -854,7 +837,7 @@ The checklist report is written as a JSON file with the following structure:
     }
   ],
   "summary": {
-    "totalGates": 26,
+    "totalGates": 25,
     "pass": 22,
     "fail": 2,
     "skip": 1,
@@ -962,7 +945,6 @@ Threshold: CRITICAL
 Timestamp: 2026-02-23T10:30:00Z
 
 Phase 1: Environment Readiness ........................ PASS
-  [PASS] 1.0 CLI available (HIGH) -- fluent v2.0.0
   [PASS] 1.1 Auth valid (CRITICAL) -- admin@hmdev, roles: ADMIN
   [PASS] 1.2 Retailer exists (CRITICAL) -- HM_TEST, ACTIVE
   [PASS] 1.3 Locations exist (HIGH) -- 3 locations (2 WH, 1 STORE)
@@ -1005,7 +987,7 @@ Phase 8: Completeness ................................. PASS
 
 SUMMARY
 -------
-Total: 26 gates | PASS: 25 | FAIL: 1 | SKIP: 0
+Total: 25 gates | PASS: 24 | FAIL: 1 | SKIP: 0
 
 VERDICT: READY
 (Gate 2.4 failed at HIGH but threshold is CRITICAL -- does not block)
@@ -1048,7 +1030,7 @@ Resolve all CRITICAL failures before deployment.
 | `/fluent-settings` | Phase 5 applies settings audit patterns | Input |
 | `/fluent-scope-decompose` | Phase 8 gate 8.1 reads the task list artifact | Input |
 | `/fluent-module-deploy` | Receives the READY verdict to proceed | Output |
-| `/fluent-workflow-deploy` | Receives the READY verdict for workflow-only deploys | Output |
+| `/fluent-workflow` | Receives the READY verdict for workflow-only deploys | Output |
 | `/fluent-session-summary` | All gate executions are tracked for audit trail | Bidirectional |
 | `/fluent-session-audit-export` | Checklist report path recorded in audit document | Output |
 

package/content/dev/skills/fluent-retailer-config/SKILL.md

@@ -12,6 +12,15 @@ Configure Fluent Commerce retailer environments from empty to workflow-ready. Cr
 
 ## Planning Gate
 
+### Pre-flight: Plan Verification
+
+Before proceeding, check for an existing approved plan:
+
+1. **Search** `accounts/<PROFILE>/plans/` for a file with `Status: APPROVED` that covers this retailer configuration
+2. **If multi-artifact work** (retailer config + rules + workflows): STOP. Invoke `/fluent-feature-plan` first — this skill cannot be used for multi-artifact work without a feature plan
+3. **If approved plan found:** Skip to implementation, referencing the plan's relevant sections
+4. **If retailer-config-only work with no plan:** Continue to the Planning Gate below to write a plan for this skill
+
 **Before creating any entities or modifying retailer configuration, write a plan using the template from `PLAN_TEMPLATE.md` in the `fluent-feature-plan` skill.**
 
 **Retailer-config specific emphasis — ensure these are covered:**

package/content/dev/skills/fluent-rule-scaffold/SKILL.md

@@ -12,6 +12,15 @@ Generate new Fluent Commerce Rubix rule classes with proper structure, annotatio
 
 ## Planning Gate
 
+### Pre-flight: Plan Verification
+
+Before proceeding, check for an existing approved plan:
+
+1. **Search** `accounts/<PROFILE>/plans/` for a file with `Status: APPROVED` that covers this rule
+2. **If multi-artifact work** (this rule + workflow changes + settings): STOP. Invoke `/fluent-feature-plan` first — this skill cannot be used for multi-artifact work without a feature plan
+3. **If approved plan found:** Skip to implementation, referencing the plan's §7 (Rules) and §8 (Detailed Design) sections
+4. **If single-rule-only work with no plan:** Continue to the Planning Gate below to write a plan for this skill
+
 **Before scaffolding any rule, write a plan using the template from `PLAN_TEMPLATE.md` in the `fluent-feature-plan` skill.** Every table row must carry a Source column (NEW/EXISTING/MODIFIED/REUSED/OOTB). For NEW rules, provide full pseudo logic.
 
 **If this rule is part of a larger feature** (multiple rules + workflow changes + settings), use `/fluent-feature-plan` first to produce the comprehensive plan. Then reference the approved plan during scaffolding.

package/content/dev/skills/fluent-scope-decompose/SKILL.md

@@ -20,7 +20,7 @@ Other skills own:
 - Workflow editing --> `/fluent-workflow-builder`
 - Build orchestration --> `/fluent-build`
 - Deployment --> `/fluent-module-deploy`
-- Session orchestration across tasks --> `/fluent-dev` agent
+- Session orchestration across tasks --> `fluent-dev` agent
 
 This skill produces the plan; other skills execute it.
 

package/content/dev/skills/fluent-settings/SKILL.md

@@ -12,6 +12,16 @@ Manage Fluent Commerce settings that configure how workflow rules behave at runt
 
 ## Planning Gate
 
+### Pre-flight: Plan Verification
+
+Before proceeding, check for an existing approved plan:
+
+1. **Search** `accounts/<PROFILE>/plans/` for a file with `Status: APPROVED` that covers these settings
+2. **If multi-artifact work** (settings + rules + workflows): STOP. Invoke `/fluent-feature-plan` first — this skill cannot be used for multi-artifact work without a feature plan
+3. **If approved plan found:** Skip to implementation, referencing the plan's §9 (Settings) section
+4. **If settings-only work with no plan:** Continue to the Planning Gate below to write a plan for this skill
+5. **Read-only operations** (audit, discover, list) are always exempt from planning
+
 **Before creating or updating any settings, write a plan using the template from `PLAN_TEMPLATE.md` in the `fluent-feature-plan` skill.** Every setting row must carry a Source column (NEW/EXISTING/MODIFIED). Read-only operations (audit, discover, list) are exempt.
 
 **Settings-specific emphasis — ensure these are covered:**

package/content/dev/skills/fluent-source-onboard/SKILL.md

@@ -150,6 +150,15 @@ plugin.list (compact: true)
 
 ### Phase 2: Planning Gate
 
+#### Pre-flight: Plan Verification
+
+Before proceeding, check for an existing approved plan:
+
+1. **Search** `accounts/<PROFILE>/plans/` for a file with `Status: APPROVED` that covers this onboarding
+2. **If multi-artifact work** (onboarding as part of larger feature): STOP. Invoke `/fluent-feature-plan` first
+3. **If approved plan found:** Skip to implementation, referencing the plan's relevant sections
+4. **If source-onboard-only work with no plan:** Continue to the Planning Gate below
+
 **MANDATORY: Present a restructuring plan before making ANY changes.** Use the template from `PLAN_TEMPLATE.md` in the `fluent-feature-plan` skill as the base structure. Every table row must carry a Source column (NEW/EXISTING/MODIFIED/REUSED/OOTB). Extend with the source-onboard-specific sections below.
 
 Write the plan to: `accounts/<PROFILE>/plans/<YYYY-MM-DD>-source-onboard-<slug>.md`. Set `Status: PENDING`.