gsd-ag 1.0.0

package/.agent/workflows/verify.md

@@ -0,0 +1,263 @@
+---
+description: The Auditor — Validate work against spec with empirical evidence
+argument-hint: "<phase-number>"
+---
+
+# /verify Workflow
+
+<role>
+You are a GSD verifier. You validate implemented work against spec requirements using empirical evidence.
+
+**Core principle:** No "trust me, it works." Every verification produces proof.
+
+**Core responsibilities:**
+- Extract testable deliverables from phase
+- Walk through each requirement
+- Collect empirical evidence (commands, screenshots)
+- Create verification report
+- Generate fix plans if issues found
+</role>
+
+<objective>
+Confirm that implemented work meets spec requirements with documented proof.
+
+The verifier checks the CODEBASE, not SUMMARY claims.
+</objective>
+
+<context>
+**Phase:** $ARGUMENTS (required — phase number to verify)
+
+**Required files:**
+- `.gsd/SPEC.md` — Original requirements
+- `.gsd/ROADMAP.md` — Phase definition with must-haves
+- `.gsd/phases/{phase}/*-SUMMARY.md` — What was implemented
+</context>
+
+<process>
+
+## 1. Load Verification Context
+
+Read:
+- Phase definition from `.gsd/ROADMAP.md`
+- Original requirements from `.gsd/SPEC.md`
+- All SUMMARY.md files from `.gsd/phases/{phase}/`
+
+---
+
+## 2. Extract Must-Haves
+
+From the phase definition, identify **must-haves** — requirements that MUST be true for the phase to be complete.
+
+```markdown
+### Must-Haves for Phase {N}
+1. {Requirement 1} — How to verify
+2. {Requirement 2} — How to verify
+3. {Requirement 3} — How to verify
+```
+
+---
+
+## 3. Verify Each Must-Have
+
+For each must-have:
+
+### 3a. Determine Verification Method
+
+| Type | Method | Evidence |
+|------|--------|----------|
+| API/Backend | Run curl or test command | Command output |
+| UI | Use browser tool | Screenshot |
+| Build | Run build command | Success output |
+| Tests | Run test suite | Test results |
+| File exists | Check filesystem | File listing |
+| Code behavior | Run specific scenario | Output |
+
+### 3b. Execute Verification
+
+Run the verification command/action.
+
+// turbo
+```bash
+# Example: Run tests
+npm test
+```
+
+### 3c. Record Evidence
+
+For each must-have, record:
+- **Status:** PASS / FAIL
+- **Evidence:** Command output, screenshot path, etc.
+- **Notes:** Any observations
+
+---
+
+## 4. Create Verification Report
+
+Write `.gsd/phases/{phase}/VERIFICATION.md`:
+
+```markdown
+---
+phase: {N}
+verified_at: {timestamp}
+verdict: PASS | FAIL | PARTIAL
+---
+
+# Phase {N} Verification Report
+
+## Summary
+{X}/{Y} must-haves verified
+
+## Must-Haves
+
+### ✅ {Must-have 1}
+**Status:** PASS
+**Evidence:** 
+```
+{command output or description}
+```
+
+### ❌ {Must-have 2}
+**Status:** FAIL
+**Reason:** {why it failed}
+**Expected:** {what should happen}
+**Actual:** {what happened}
+
+## Verdict
+{PASS | FAIL | PARTIAL}
+
+## Gap Closure Required
+{If FAIL, list what needs to be fixed}
+```
+
+---
+
+## 5. Handle Results
+
+### If PASS (all must-haves verified):
+
+Update `.gsd/STATE.md`:
+```markdown
+## Current Position
+- **Phase**: {N} (verified)
+- **Status**: ✅ Complete and verified
+```
+
+Output:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► PHASE {N} VERIFIED ✓
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+{X}/{X} must-haves verified
+
+All requirements satisfied.
+
+───────────────────────────────────────────────────────
+
+▶ Next Up
+
+/execute {N+1} — proceed to next phase
+
+───────────────────────────────────────────────────────
+```
+
+### If FAIL (some must-haves failed):
+
+**Create gap closure plans:**
+
+For each failed must-have, create a fix plan in `.gsd/phases/{phase}/`:
+
+```markdown
+---
+phase: {N}
+plan: fix-{issue}
+wave: 1
+gap_closure: true
+---
+
+# Fix Plan: {Issue Name}
+
+## Problem
+{What failed and why}
+
+## Tasks
+
+<task type="auto">
+  <name>Fix {issue}</name>
+  <files>{files to modify}</files>
+  <action>{specific fix instructions}</action>
+  <verify>{how to verify the fix}</verify>
+  <done>{acceptance criteria}</done>
+</task>
+```
+
+Output:
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► PHASE {N} GAPS FOUND ⚠
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+{X}/{Y} must-haves verified
+{Z} issues require fixes
+
+Gap closure plans created.
+
+───────────────────────────────────────────────────────
+
+▶ Next Up
+
+/execute {N} --gaps-only — run fix plans
+
+───────────────────────────────────────────────────────
+```
+
+---
+
+## 6. Commit Verification
+
+```bash
+git add .gsd/phases/{phase}/VERIFICATION.md
+git commit -m "docs(phase-{N}): verification report"
+```
+
+</process>
+
+<evidence_requirements>
+
+## Forbidden Phrases
+
+Never accept these as verification:
+- "This should work"
+- "The code looks correct"
+- "I've made similar changes before"
+- "Based on my understanding"
+- "It follows the pattern"
+
+## Required Evidence
+
+| Claim | Required Proof |
+|-------|----------------|
+| "Tests pass" | Actual test output |
+| "API works" | Curl command + response |
+| "UI renders" | Screenshot |
+| "Build succeeds" | Build output |
+| "File created" | `ls` or `dir` output |
+
+</evidence_requirements>
+
+<related>
+## Related
+
+### Workflows
+| Command | Relationship |
+|---------|--------------|
+| `/execute` | Run before /verify to implement work |
+| `/execute --gaps-only` | Fix issues found by /verify |
+| `/debug` | Diagnose verification failures |
+
+### Skills
+| Skill | Purpose |
+|-------|---------|
+| `verifier` | Detailed verification methodology |
+| `empirical-validation` | Evidence requirements |
+</related>

package/.agent/workflows/web-search.md

@@ -0,0 +1,121 @@
+---
+description: Search the web for information to inform decisions
+argument-hint: "<query> [--domain <site>]"
+---
+
+# /web-search Workflow
+
+<objective>
+Search the web to gather information for technical decisions, API documentation, library comparisons, or any research need.
+</objective>
+
+<when_to_use>
+- Evaluating libraries or frameworks
+- Finding API documentation
+- Checking current best practices
+- Researching error messages
+- Comparing implementation approaches
+- Getting up-to-date information on tools/services
+</when_to_use>
+
+<process>
+
+## 1. Formulate Query
+
+Parse the user's request into a focused search query.
+
+**Good queries:**
+- Specific: "Next.js 14 app router authentication best practices"
+- Targeted: "Prisma vs Drizzle ORM comparison 2024"
+- Actionable: "how to fix CORS error Express.js"
+
+**Bad queries:**
+- Too broad: "how to code"
+- Too vague: "best database"
+
+---
+
+## 2. Execute Search
+
+Use the `search_web` tool with:
+- Query: The formulated search query
+- Domain (optional): Prioritize specific site (e.g., `docs.python.org`)
+
+---
+
+## 3. Analyze Results
+
+From the search results:
+1. **Extract key information** relevant to the user's need
+2. **Note sources** for citations
+3. **Identify patterns** across multiple results
+4. **Flag contradictions** or outdated information
+
+---
+
+## 4. Summarize Findings
+
+Present findings clearly:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► WEB SEARCH RESULTS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Query: {query}
+
+───────────────────────────────────────────────────────
+
+KEY FINDINGS
+────────────
+• {finding 1}
+• {finding 2}
+• {finding 3}
+
+RECOMMENDATION
+──────────────
+{actionable recommendation based on findings}
+
+SOURCES
+───────
+• {source 1}
+• {source 2}
+
+───────────────────────────────────────────────────────
+```
+
+---
+
+## 5. Offer Next Steps
+
+Based on findings:
+- Suggest follow-up searches if needed
+- Recommend adding to RESEARCH.md for project context
+- Offer to implement based on findings
+
+</process>
+
+<integration>
+## Integration with GSD
+
+**During /research-phase:**
+Use `/web-search` to gather information for RESEARCH.md.
+
+**During /plan:**
+Use `/web-search` when discovery level 1-3 indicates research needed.
+
+**During /debug:**
+Use `/web-search` to find solutions to error messages.
+</integration>
+
+<related>
+## Related
+
+### Workflows
+| Command | Relationship |
+|---------|--------------|
+| `/research-phase` | Uses web-search for phase research |
+| `/plan` | May trigger web-search for discovery |
+| `/debug` | Search for error solutions |
+
+</related>

package/.agent/workflows/whats-new.md

@@ -0,0 +1,80 @@
+---
+description: Show recent GSD changes and new features
+---
+
+# /whats-new Workflow
+
+<objective>
+Display recent changes, new features, and improvements to GSD for Antigravity.
+</objective>
+
+<process>
+
+## 1. Read CHANGELOG.md
+
+```bash
+# Read the latest version section from CHANGELOG.md
+head -50 CHANGELOG.md
+```
+
+## 2. Display Recent Changes
+
+Display the latest version(s) from CHANGELOG.md:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ GSD ► WHAT'S NEW
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+VERSION 1.2.0 — 2026-01-17
+══════════════════════════
+
+🌍 CROSS-PLATFORM SUPPORT
+
+• All 16 workflow files now have Bash equivalents
+• README with dual-syntax Getting Started
+• /web-search workflow for research
+
+───────────────────────────────────────────────────────
+
+VERSION 1.1.0 — 2026-01-17
+══════════════════════════
+
+📚 TEMPLATE PARITY & EXAMPLES
+
+• 14 new templates (DEBUG.md, UAT.md, etc.)
+• Examples directory with walkthroughs
+• /add-todo and /check-todos workflows
+• Cross-references between workflows
+
+───────────────────────────────────────────────────────
+
+VERSION 1.0.0 — 2026-01-17
+══════════════════════════
+
+🎉 INITIAL RELEASE
+
+Full port of GSD methodology to Google Antigravity.
+• 24 workflows, 8 skills, 14 templates
+• 4 core rules: Planning Lock, State Persistence,
+  Context Hygiene, Empirical Validation
+
+───────────────────────────────────────────────────────
+
+📚 Full changelog: CHANGELOG.md
+
+───────────────────────────────────────────────────────
+```
+
+</process>
+
+<related>
+## Related
+
+### Workflows
+| Command | Relationship |
+|---------|--------------|
+| `/update` | Update GSD to latest version |
+| `/help` | List all commands |
+
+</related>

package/.gemini/GEMINI.md

@@ -0,0 +1,67 @@
+# GSD Methodology — Mission Control Rules
+
+> **Get Shit Done**: A spec-driven, context-engineered development methodology.
+> 
+> These rules enforce disciplined, high-quality autonomous development.
+
+---
+
+## Canonical Rules
+
+**All canonical rules are in [PROJECT_RULES.md](../.gsd/PROJECT_RULES.md).**
+
+This file provides Gemini-specific integration. For the complete methodology, see PROJECT_RULES.md.
+
+---
+
+## Core Principles
+
+1. **Plan Before You Build** — No code without specification
+2. **State Is Sacred** — Every action updates persistent memory
+3. **Context Is Limited** — Prevent degradation through hygiene
+4. **Verify Empirically** — No "trust me, it works"
+
+---
+
+## Quick Reference
+
+```
+Before coding    → Check SPEC.md is FINALIZED
+Before file read → Search first, then targeted read
+After each task  → Update STATE.md
+After 3 failures → State dump + fresh session
+Before "Done"    → Empirical proof captured
+```
+
+---
+
+## Workflow Integration
+
+These rules integrate with the GSD workflows:
+
+| Workflow | Rules Enforced |
+|----------|----------------|
+| `/map` | Updates ARCHITECTURE.md, STACK.md |
+| `/plan` | Enforces Planning Lock, creates ROADMAP |
+| `/execute` | Enforces State Persistence after each task |
+| `/verify` | Enforces Empirical Validation |
+| `/pause` | Triggers Context Hygiene state dump |
+| `/resume` | Loads state from STATE.md |
+
+---
+
+## Gemini-Specific Tips
+
+For Gemini-specific enhancements, see [adapters/GEMINI.md](../.gsd/adapters/GEMINI.md).
+
+Key recommendations:
+- **Flash** for quick iterations and simple edits
+- **Pro** for complex planning and analysis
+- Large context is available but **search-first** still applies
+
+---
+
+*GSD Methodology adapted for Google Antigravity*
+*Canonical rules: [PROJECT_RULES.md](../.gsd/PROJECT_RULES.md)*
+*Source: https://github.com/glittercowboy/get-shit-done*
+