I have created a workflow.md file to use with Antigravity as below, can anyone help me, I'm new to this field

Cesc Ng — Sat, 28 Mar 2026 17:16:33 +0000

🚀 CESC AI WORKFLOW v3 (PHASE + FINALIZE MODE)

AI Agent must create real folders and files for each command, with structured phases, execution traceability, and finalization support.

⚠️ CORE PRINCIPLES

MUST create real files in project
MUST create folder if not exist
MUST NOT only return text
If cannot create file → return FULL file content ready to paste

📁 DIRECTORY STRUCTURE

/docs
├── requirements/
├── brainstorm/
├── plan/
├── execution/
├── review/
├── refactor/
├── testing/
├── docs/
└── final/

📁 FILE NAMING (MANDATORY)

Format:

YYYY-MM-DD_HHmm_[feature]_[type].md

Rules:

Always include timestamp
Feature = kebab-case (auth-system, payment-flow)
Auto detect from:
- "Feature: xxx"
- or infer from context

🧠 GLOBAL DOCUMENT HEADER (NEW)

Every file MUST include:

Status: DRAFT | IN_PROGRESS | FINAL
Version: v1
Feature: <feature-name>
Updated: YYYY-MM-DD HH:mm

🧩 PHASE + STEP STRUCTURE (MANDATORY IN /plan)

## Phase 1: <name>

### Step 1.1: <step name>
- Description
- Output
- Dependencies

### Step 1.2: <step name>
...

Rules:

Phase = milestone (setup, core, optimize…)
Step = atomic, implementable immediately
Each step MUST define:
- Output (file/code/module)
- Clear scope (small enough)

🔒 FINALIZE MODE (NEW)

Command:

/[command] end

Example:

/plan end

FINALIZE RULES

MUST create new file:

YYYY-MM-DD_HHmm_[feature]_[command]-final.md

MUST update:

Status: FINAL

MUST:
- Remove ambiguity
- Remove duplicated logic
- Ensure all steps executable
MUST include:

## ✅ Final Checklist
- [x] All steps actionable
- [x] No missing dependency
- [x] Clear execution order

🔗 TRACEABILITY (MANDATORY)

All docs must link together.

Example:

Plan:

Step 2.1 → execution-step-2.md

Execution:

Source Plan:
- Phase 2 - Step 2.1

Testing:

Covering:
- execution-step-2.md

🧠 COMMANDS

/brainstorm

Folder:

/docs/brainstorm/

File:

YYYY-MM-DD_HHmm_[feature]_brainstorm.md

Content:

Problem
Scope
- In scope
- Out of scope
Ambiguities
Unknowns (Need clarification)
Assumptions
Solutions
Tech stack

/plan

Folder:

/docs/plan/

File:

YYYY-MM-DD_HHmm_[feature]_plan-v{n}.md

Content:

Phase + Step breakdown
Execution Strategy
- Parallel / Sequential
- Estimated complexity
Dependencies
Risks

Additional:

## Phase Summary

| Phase | Goal | Risk |

Versioning:

v1 → v2 → v3...
Iterate until user says: "Plan is clean"

/execute

Folder:

/docs/execution/

File:

YYYY-MM-DD_HHmm_[feature]_execution-step-{n}.md

Rules:

Only implement selected step

Support:
/execute step=1,2

Content:

Source Plan:
- Phase X - Step Y
Code
Short explanation

/review

Folder:

/docs/review/

File:

YYYY-MM-DD_HHmm_[feature]_review.md

Content:

Critical issues
Major issues
Minor issues
Suggestions

Additional:

## Coverage Check
- Missing cases?
- Missing edge cases?

Verdict:

LGTM
NEED FIX

/refactor

Folder:

/docs/refactor/

File:

YYYY-MM-DD_HHmm_[feature]_refactor.md

Content:

Improved code
Changes made
Reasoning

Additional:

## Impact Analysis
- Performance
- Readability
- Maintainability

🧪 TESTING

/testcase

Folder:

/docs/testing/

File:

YYYY-MM-DD_HHmm_[feature]_testcases.md

Content:

Test scenarios
Input / Expected Output
Edge cases
Priority

Additional:

## Test Pyramid
- Unit
- Integration
- E2E

/test

Folder:

/docs/testing/

File:

YYYY-MM-DD_HHmm_[feature]_test-results.md

Content:

Unit tests (Jest / PyTest…)
Passed / Failed
Error logs
Coverage estimate

/report

Folder:

/docs/final/

File:

YYYY-MM-DD_HHmm_[feature]_final-report.md

Content:

Requirement summary
Implementation mapping
Code quality
Test results
Risks
Deployment readiness

Additional:

## Traceability

| Requirement | Plan Step | Code | Test |

📚 DOCUMENTATION

/docs init

Folder:

/docs/docs/

MUST create:

project-overview.md
tech-stack.md
architecture.md
coding-conventions.md
api-contract.md

/docs update

MUST update documentation based on latest implementation

/docs explain

File:

/docs/docs/YYYY-MM-DD_HHmm_{module}_explain.md

🔄 WORKFLOWS

Small Task

/brainstorm
→ /plan
→ /execute
→ /review

Medium Task

/brainstorm
→ /plan
→ /execute
→ /review
→ /refactor

Large Feature

/brainstorm
→ /plan (iterate until clean)
→ /docs init
→ /execute (step-by-step)
→ /review
→ /refactor
→ /testcase
→ /test
→ /docs update
→ /report

⚡ FLAGS

/execute step=1,2
/testcase level=unit
/testcase level=e2e
/review strict=true
/test strict=true

🧬 VERSIONING RULES

Command	Version Rule
/plan	v1 → v2 → v3
/review	overwrite
/refactor	overwrite
/final	new file

🆕 OPTIONAL COMMANDS (ADVANCED)

/sync

Validate consistency across:
- plan
- execution
- test
Detect:
- Missing step
- Missing test
- Dead logic

/status

Generate system state:

Feature: <feature-name>

Plan: vX (DRAFT/FINAL)
Execution: Step X done
Testing: XX%
Risk: Low/Medium/High

/retro

Post-mortem:

## What went well
## What went wrong
## Lessons learned

🎯 FINAL GOAL

Transform AI into:

Architect
Developer
Reviewer
QA Engineer
Tech Lead
Documentation Writer

💡 HARD RULE

Every step MUST produce:

Code OR
File OR
Measurable output

DEV Community: Cesc Ng

I have created a workflow.md file to use with Antigravity as below, can anyone help me, I'm new to this field

🚀 CESC AI WORKFLOW v3 (PHASE + FINALIZE MODE)

⚠️ CORE PRINCIPLES

📁 DIRECTORY STRUCTURE

📁 FILE NAMING (MANDATORY)

🧠 GLOBAL DOCUMENT HEADER (NEW)

🧩 PHASE + STEP STRUCTURE (MANDATORY IN /plan)

🔒 FINALIZE MODE (NEW)

FINALIZE RULES

🔗 TRACEABILITY (MANDATORY)

Example:

🧠 COMMANDS

/brainstorm

Folder:

File:

Content:

/plan

Folder:

File:

Content:

Additional:

Versioning:

/execute

Folder:

File:

Rules:

Content:

/review

Folder:

File:

Content:

Additional:

Verdict:

/refactor

Folder:

File:

Content:

Additional:

🧪 TESTING

/testcase

Folder:

File:

Content:

Additional:

/test

Folder:

File:

Content:

/report

Folder:

File:

Content:

Additional:

📚 DOCUMENTATION

/docs init

Folder:

MUST create:

/docs update

/docs explain

File:

🔄 WORKFLOWS

Small Task

Medium Task

Large Feature

⚡ FLAGS

🧬 VERSIONING RULES

🆕 OPTIONAL COMMANDS (ADVANCED)

/sync

/status

/retro

🎯 FINAL GOAL

💡 HARD RULE