Skip to content

feat(gravity-flow-abilities): add Gravity Flow abilities skill and refine Gravity Forms skill - #4

Merged
faction23 merged 21 commits into
mainfrom
skill/gravity-flow-abilities
Aug 4, 2026
Merged

feat(gravity-flow-abilities): add Gravity Flow abilities skill and refine Gravity Forms skill#4
faction23 merged 21 commits into
mainfrom
skill/gravity-flow-abilities

Conversation

@faction23

Copy link
Copy Markdown
Contributor

Description

Closes: N/A - new skill authored directly, no tracking issue

  • Adds the new gravity-flow-abilities skill (SKILL.md plus feasibility, processing, and status-reference docs) covering workflow step CRUD, approval policies, reassignment recipes, destructive-safety guardrails, and consultation/feasibility guidance.
  • Updates gravity-forms-abilities: documents notification/confirmation write abilities, requires explicit phoneFormat with all valid values, notes the GF 3.0 international phone value shape, fixes entries-search to use form_ids, and corrects MCP endpoint references.
  • Adds change_log.txt entries and ignores the local Claude settings file.

Testing instructions

  1. Run ./scripts/validate-skills.sh and confirm all skills pass.
  2. Review skills/gravity-flow-abilities/SKILL.md frontmatter (name matches directory, description present).
  3. Spot-check the reference docs render correctly and internal links resolve.

Checklist:

  • I've checked the error log to ensure my code doesn't throw any errors.
  • My code follows the WordPress coding standards and inline documentation standards.
  • My code follows the accessibility standards.
  • This PR has a related issue.
  • This PR has a related test.
  • I have considered what will happen when an existing user updates to this branch.
  • I have added a "Documentation Needed" label to this PR (if necessary).

faction23 added 21 commits July 27, 2026 10:30
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.
@faction23
faction23 merged commit 0d0ecb5 into main Aug 4, 2026
1 check passed
@faction23
faction23 deleted the skill/gravity-flow-abilities branch August 4, 2026 20:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant