description: "Unified Global Workflow for Meta-Engineering: Research, Rules, Skills, and Flow Optimization."

Global Meta-Engineering Workflow (/global-flow)

Use this workflow to optimize the Antigravity Flow itself. This is not just for RAG or research; it is the master protocol for creating Automations, Skills, and Rules to improve how work gets done across all projects.

1. Define Optimization Objective

State the specific "Flow Friction" or "Capability Gap": - Automation: "How to automate the versioning of CHANGELOG.md?" - Skill: "Create a global 'Knowledge Engine' skill for grounded interpretations." - Rule: "Enforce a 'Double-Audit' rule before any API-heavy execution."

2. Consult "System DNA" (Global Rules)

Read the master coordination rules to understand current constraints: - .cursor/rules/ag.mdc (Lead Coordinator Rules) - .cursor/rules/agent-roles.mdc (Multi-Agent System Personas)

3. Meta-Technical Search

Use search_web with agentic-engineering keywords for Gemini 2.5 Flash: - Prompt Engineering: "Chain of Thought" for Gemini 2.5 Flash - Optimizing Gemini 2.5 Flash performance: Context limits and speed - Patterns: "Autonomous Agent State Management" using Gemini native functions

4. The "Trilateral Analysis" (Inherit vs. Missing vs. Rejected)

Analyze the findings to decide the global path:

• Inherit (Adopt): Universal prompt patterns or architectural constraints that we should implement immediately (e.g., "Always use deterministic parsers for data entry").
• Missing (Plan): Features or capabilities the source has (like NotebookLM's UI) that we want but have not yet implemented. Document these in FUTURE_ROADMAP.md.
• Rejected (Omit): Features the source has (e.g., "Full PDF Upload") that we will NOT implement due to infrastructure limits, logic complexity, or privacy constraints. Explain WHY.

5. Create Implementation Plan

MANDATORY: Before any files are modified or new rules are created, you must generate a structured implementation_plan.md for the user. - Detail the specific changes (Rule, Skill, or Workflow). - Explain the logic (Why and How). - CRITICAL: Wait for explicit user approval before proceeding to step 6.

6. Implement Agentic Update

Once the plan is approved, execute the optimization: - New Rule: Update .cursor/rules/ to change agent behavior. - New Skill: Create a SKILL.md in .agents/skills/ to give agents new "muscles." - New Workflow: If the process is complex and repeatable, create a sub-workflow.

7. Pulse Checkpoint (Synchronization)

MANDATORY: After ANY agentic update (Rule, Skill, or Workflow): - Sync: Execute the v-sync-logger skill to update the "4-Doc Rule" (CHANGELOG, PROJECT_STATUS, APP_CONTEXT). - Checkpoint: Ensure an automated Git commit is performed with the "Pulse:" prefix to maintain a professional audit trail. - Verify: Confirm the new capability is immediately visible to all agent roles.