feat(gravity-flow-abilities): add Gravity Flow abilities skill and refine Gravity Forms skill - #4
Merged
Merged
Conversation
…covery, deep doc links
Flow contributes its tools to Gravity Forms' single MCP endpoint (no separate Flow endpoint). Gating and skill download move to Forms → Settings → MCP, in the Gravity Flow metabox. Also document steps-update is_active as the reversible deactivate — the safe alternative to permanent steps-delete.
…configurable Two gaps surfaced by the phase-c validation pass: - Never conclude a form/workflow/step doesn't exist from a single system-info read — confirm with steps-list/status-search first (system-info is a summary). - The unanimous vs any approval policy is a configurable step setting; when a workflow is stuck on it, steps-update the policy is the real remedy, not just restart/re-notify.
…ties Add the 7 new tools to routing + access-mode groups (catalog 25->32), a Notifications & Confirmations workflow section (read-before-write, per-type required fields, default-confirmation-protected, conditional routing), and correct the stale 'via forms-update' guidance to the dedicated targeted tools.
Close the dominant residual failure across the scenario suite (agents producing a sound design but creating nothing, over-blocking a whole build on a single hand-off-able detail like an assignee identity). For build requests: create the structure with a defensible placeholder and hand off ONLY the unknown detail with the exact steps-update to finalize — a plan with nothing created fails a build request; distinct from pure feasibility questions.
From the validation loop: name the gravityflow_status_view_all capability where view-all is discussed (S-076); warn that notification recipients must be valid assignee keys — no 'submitter' token, and bad recipients save silently and email no one (S-063/S-067); and add a principle to enumerate steps for any workflow- content edit rather than stopping at form-level settings (S-032/S-069).
…shape The phone field's phoneFormat:'formatted' mode stores its value as a JSON object (country/national/formatted/e164), not a plain string. Document how that affects creating the field and reading/writing/submitting entry values via the abilities.
…nt all valid values The phone reference was missing the 'formatted' value and SKILL.md told agents to omit phoneFormat for standard phones — but API-created fields skip the editor's normalization, so an omitted or invented format broke form rendering. Document the three valid values (plus defaultCountry and showCountryCode) and instruct agents to always set phoneFormat explicitly.
…at_options, and MCP endpoint corrections Add the observed phone failure to the Key Pitfalls table and the form-creation workflow steps, point agents at the format_options key system-field-types now returns, soften the backfill claim to older GF versions (3.0.x now normalizes server-side), and correct the shared MCP endpoint path and meta-tool names to the mcp-adapter-* forms observed live. Bump skill to 1.0.3 with changelog.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Closes: N/A - new skill authored directly, no tracking issue
gravity-flow-abilitiesskill (SKILL.md plus feasibility, processing, and status-reference docs) covering workflow step CRUD, approval policies, reassignment recipes, destructive-safety guardrails, and consultation/feasibility guidance.gravity-forms-abilities: documents notification/confirmation write abilities, requires explicitphoneFormatwith all valid values, notes the GF 3.0 international phone value shape, fixesentries-searchto useform_ids, and corrects MCP endpoint references.change_log.txtentries and ignores the local Claude settings file.Testing instructions
./scripts/validate-skills.shand confirm all skills pass.skills/gravity-flow-abilities/SKILL.mdfrontmatter (name matches directory, description present).Checklist: