cfsa-antigravity 3.0.2 → 3.1.0

package/template/.codex/skills/prd-templates/references/ideation-index-template.md

@@ -0,0 +1,111 @@
+# Ideation Index — {{PROJECT_NAME}}
+
+> **Pipeline key file.** All downstream workflows read this index to locate ideation documents.
+> This file is the entry point for `/create-prd`, `/decompose-architecture`, `/audit-ambiguity ideation`, and all other workflows that consume ideation output.
+
+## Project Overview
+
+**Problem**: _One-sentence problem statement — who has it, why it matters._
+
+**One-liner**: _Elevator pitch — what the product does in ≤15 words._
+
+## Expansion Mode
+
+- Type: [full | vertical | horizontal | cross-cutting | combination | as-is]
+- Targets: [list of domains/features to focus on, if applicable]
+- Cross-cut Detection: always-on
+- Deep Think Protocol: active
+
+## Structural Classification
+
+- **Project Shape**: [single-surface | multi-surface-shared | multi-product-hub | multi-product-peer]
+- **Hub Surface** _(hub-and-spoke only)_: [surface name that owns shared domains]
+- **Surfaces**: [list of identified surfaces, e.g., "Web (Astro/React), Desktop (Rust/Tauri), Mobile (React Native)" — or "N/A" for single-surface]
+- **Classification Basis**: [how this was determined — "detected from document", "user interview", "inferred from one-liner"]
+
+> **Project Shapes:**
+> - `single-surface` — One platform. Domains are top-level children of `ideation/`.
+> - `multi-surface-shared` — 2+ platforms, same stack, >80% shared logic. Domains at top level with surface annotations.
+> - `multi-product-hub` — 2+ platforms, one is the central platform/API. Hub owns shared domains. Spokes reference via CX.
+> - `multi-product-peer` — 2+ platforms, no primary. `shared/` folder as a peer for cross-surface domains.
+
+## Progress Summary
+
+| Metric | Value |
+|--------|-------|
+| Total surfaces | _N_ |
+| Total domains | _N_ |
+| Total leaf features | _N_ |
+| Max depth reached | _N_ |
+| Leaf nodes at [SURFACE] | _N_ |
+| Leaf nodes at [DEEP] | _N_ |
+| Leaf nodes at [EXHAUSTED] | _N_ |
+| CX entries confirmed | _N_ |
+| Deep Think hypotheses confirmed | _N_ |
+| Deep Think hypotheses rejected | _N_ |
+
+## Document Map
+
+> Downstream workflows: read this table to find the specific file you need.
+
+### Meta Documents
+
+| Document | Path | Status |
+|----------|------|--------|
+| Problem Statement | [problem-statement.md](meta/problem-statement.md) | _status_ |
+| Personas | [personas.md](meta/personas.md) | _status_ |
+| Competitive Landscape | [competitive-landscape.md](meta/competitive-landscape.md) | _status_ |
+| Constraints | [constraints.md](meta/constraints.md) | _status_ |
+
+### Global Cross-Cuts
+
+| Document | Path |
+|----------|------|
+| Global Cross-Cuts | [ideation-cx.md](ideation-cx.md) |
+
+### Structure Map
+
+> **For single-surface projects**, domains are listed directly below.
+> **For multi-product projects**, expand each surface section.
+> Every domain below is a FOLDER containing: `{domain}-index.md`, `{domain}-cx.md`, and child features/sub-domains.
+
+#### _{Surface Name or "Top-Level Domains" for single-surface}_
+
+| # | Domain | Path | Status | Children | Depth | Deep Think |
+|---|--------|------|--------|----------|-------|------------|
+| 01 | _Domain Name_ | [01-slug/](./01-slug/) | `[SURFACE]` | _N children_ | _N levels_ | _N hypotheses_ |
+
+_Repeat surface sections for multi-product projects._
+
+#### Hub-Owned Shared Domains _(hub-and-spoke only)_
+
+_Shared domains live inside the hub surface's domain tree. Listed here for visibility._
+
+| # | Domain | Hub Path | Consumed By | Status |
+|---|--------|----------|-------------|--------|
+| NN | _Domain Name_ | [web/NN-slug/](surfaces/web/NN-slug/) | Desktop, Mobile | `[SURFACE]` |
+
+## Decision Log
+
+Numbered decisions with source references.
+
+| # | Decision | Source | Domain |
+|---|----------|--------|--------|
+| D-01 | _Decision description_ | _Discussion context_ | [domain-index.md](./path) |
+
+## MoSCoW Summary
+
+> Features reference their fractal path. Path format: `{surface}/{domain}.{sub-domain}.{feature}`
+
+### Must Have
+- _Feature 1_ → `web/01.02.01` ([link](./path/01.02.01-feature.md))
+- _Feature 2_ → `desktop/01.01.03` ([link](./path/01.01.03-feature.md))
+
+### Should Have
+- _Feature 3_ → `web/02.01` ([link](./path))
+
+### Could Have
+- _Feature 4_ → `desktop/01.03.02.04` ([link](./path))
+
+### Won't Have (Now)
+- _Feature 5_ — Reason for exclusion

package/template/.codex/skills/prd-templates/references/ideation-meta-template.md

@@ -0,0 +1,126 @@
+# Ideation Meta Document Templates
+
+> These are the templates for the `ideation/meta/` directory.
+> Each meta file captures product-level information that isn't domain-specific.
+
+---
+
+## problem-statement.md
+
+```markdown
+# Problem Statement
+
+## The Problem
+
+_One sentence: what problem exists, who has it, and why current solutions fail._
+
+## Why It Matters
+
+_Market size, pain severity, frequency of occurrence._
+
+## Why Now
+
+_What has changed that makes this solvable or valuable today._
+
+## Root Cause
+
+_The underlying cause, not just the symptom. Why do current solutions fail?_
+```
+
+---
+
+## personas.md
+
+```markdown
+# User Personas
+
+> Every persona must have all 6 fields. Do not proceed to features until all personas
+> are complete. See Vision Rubric Dimension 2.
+
+## Persona: {{Name}}
+
+| Field | Detail |
+|-------|--------|
+| **Name + Role** | _Named role with context — not "a user"_ |
+| **Primary Pain Point** | _Specific friction in one sentence_ |
+| **Current Workaround** | _Exact tool, process, or coping mechanism today_ |
+| **Success Criteria** | _What "solved" looks like, measurable if possible_ |
+| **Switching Trigger** | _What event/threshold makes them switch_ |
+| **Unique Constraint** | _What makes their situation different from other personas_ |
+
+### Workflow
+
+_Primary workflow through the product — step by step._
+
+### Anti-Persona Behavior
+
+_Worst thing they could intentionally do. Worst thing they could accidentally do._
+
+---
+
+_Repeat for each persona (2-4 recommended)._
+```
+
+---
+
+## competitive-landscape.md
+
+```markdown
+# Competitive Landscape
+
+## Top Competitors
+
+| Competitor | What They Do | Strength | Weakness | Our Angle |
+|-----------|-------------|----------|----------|-----------|
+| _Name_ | _Description_ | _Why users choose them_ | _Where they fall short_ | _How we differentiate_ |
+
+## Unique Differentiators
+
+1. _Differentiator 1_ — why this matters to our personas
+2. _Differentiator 2_ — why this is hard to copy
+
+## Moat
+
+_What makes this defensible over time? Network effects, data, expertise, switching costs?_
+```
+
+---
+
+## constraints.md
+
+```markdown
+# Project Constraints
+
+## Budget
+- _Self-funded / VC-backed / enterprise budget_
+- _Monthly infrastructure ceiling_
+
+## Timeline
+- _Launch target_
+- _Phased rollout plan_
+
+## Team
+- _Solo dev / small team / full org_
+- _Skill gaps, if any_
+
+## Compliance
+- _GDPR / PCI / COPPA / HIPAA / SOC 2 / Other_
+- _Age restrictions_
+
+## Performance
+- _Expected scale (users, requests, data volume)_
+- _Latency requirements_
+
+## Project Surfaces
+
+| Surface | Type | Cross-Platform? | Notes |
+|---------|------|----------------|-------|
+| _Web app_ | _SPA / SSR / Static_ | N/A | _Primary surface_ |
+| _Desktop_ | _Tauri / Electron_ | _Yes/No_ | _Offline capability_ |
+| _Mobile_ | _Native / RN / PWA_ | _Yes/No_ | |
+| _API_ | _REST / GraphQL / tRPC_ | N/A | |
+| _CLI_ | _Yes/No_ | _Yes/No_ | |
+
+> Surface classification drives tech stack in `/create-prd`, folder structure in
+> `/decompose-architecture`, and spec shapes downstream.
+```

package/template/.codex/skills/prd-templates/references/infrastructure-report-template.md

@@ -0,0 +1,71 @@
+# Infrastructure Verification Report Template
+
+Use this template when creating the report during `/verify-infrastructure`.
+
+## Initial Report (Step 0.6)
+
+Create at `.memory/wiki/specs/audits/verify-infrastructure-YYYY-MM-DD-HHMM[-auth].md`:
+
+```markdown
+# Infrastructure Verification Report
+
+**Date**: YYYY-MM-DD HH:MM
+**Trigger**: [infrastructure slice | auth slice]
+**Verdict**: ⏳ in-progress
+
+## Results
+
+| # | Check | Status | Notes |
+|---|-------|--------|-------|
+| 0 | Placeholder audit | ⏳ | |
+| 1 | CI/CD config | ⏳ | |
+| 2 | CI/CD green | ⏳ | |
+| 3 | Environment audit | ⏳ | |
+| 4 | Migration check | ⏳ | |
+| 5 | Staging deployment | ⏳ | |
+| 6 | Auth smoke test | ⏳ | |
+| 6.5 | Logging gate | ⏳ | |
+| 6.6 | Error tracking gate | ⏳ | |
+
+## Failures (if any)
+
+None yet.
+
+## Next Steps
+
+In progress.
+```
+
+## Final Report (Step 8)
+
+Update the same file — change the Verdict and fill in results:
+
+```markdown
+# Infrastructure Verification Report
+
+**Date**: YYYY-MM-DD
+**Trigger**: [infrastructure slice | auth slice]
+**Verdict**: [PASS | FAIL]
+
+## Results
+
+| # | Check | Status | Notes |
+|---|-------|--------|-------|
+| 0 | Placeholder audit | ✅/❌ | |
+| 1 | CI/CD config | ✅/❌ | |
+| 2 | CI/CD green | ✅/❌ | |
+| 3 | Environment audit | ✅/❌ | |
+| 4 | Migration check | ✅/❌ | |
+| 5 | Staging deployment | ✅/❌ | |
+| 6 | Auth smoke test | ✅/❌/⏭️ | |
+| 6.5 | Logging gate | ✅/❌ | |
+| 6.6 | Error tracking gate | ✅/❌ | |
+
+## Failures (if any)
+
+[Details of any failing checks]
+
+## Next Steps
+
+[What to do next based on the verdict]
+```

package/template/.codex/skills/prd-templates/references/input-classification.md

@@ -0,0 +1,23 @@
+# Input Classification Table
+
+Classify user-provided input to determine which mode the `idea-extraction` skill operates in.
+
+| Input Type | Detection Criteria | Extraction Mode |
+|---|---|---|
+| **Rich document** | >5KB, detailed docs, design conversations, prior specs | Extraction |
+| **Thin document** | <5KB, structured but shallow (bullet list, rough PRD) | Expansion |
+| **Conversational dump** | Chat logs, unstructured conversation transcripts | Extraction (with noise filtering) |
+| **Verbal / one-liner** | User describes idea in chat, no files | Interview |
+| **Nothing** | "I want to build an app" or similar zero-context input | Interview (deep) |
+
+## Mode References
+
+Each mode's full process is defined in `.codex/skills/idea-extraction/SKILL.md`:
+
+- **Extraction Mode** → `## Input-Adaptive Modes → Extraction Mode — Rich Input`
+- **Expansion Mode** → `## Input-Adaptive Modes → Expansion Mode — Thin Input`
+- **Interview Mode** → `## Input-Adaptive Modes → Interview Mode — No Input / One-Liner`
+
+## Proportionality Rule (Extraction Mode only)
+
+If source input > 50KB, total ideation output must be ≥ 30% of source line count.

package/template/.codex/skills/prd-templates/references/map-guard-protocol.md

@@ -0,0 +1,65 @@
+# Map Guard Protocol
+
+**Purpose**: Enforce strict surface stack map verification before any workflow step that depends on tech stack decisions. Auto-recover when possible, hard stop when not.
+
+---
+
+## Procedure
+
+### 1. Read the Map
+
+Read the surface stack map from `.codex/instructions/tech-stack.md`.
+
+### 2. Check Required Cells
+
+For the current workflow, verify that every cell the workflow depends on is filled (non-empty, no `{{PLACEHOLDER}}` literal).
+
+Required cells vary by workflow — check the `requires_placeholders` frontmatter of the current workflow file, or the specific cells referenced in the workflow steps.
+
+### 3. Classify Empty Cells
+
+**If ALL required cells are filled** → proceed. No action needed.
+
+**If ANY required cell is empty** → classify each empty cell:
+
+| Empty Cell | Recovery Action | Auto-Recoverable? |
+|---|---|---|
+| Languages / Frameworks / Databases / ORMs | Run `/bootstrap-agents` with confirmed values from `architecture-draft.md` | **YES** — auto-invoke |
+| Auth / Security | Run `/bootstrap-agents` with confirmed values from `architecture-draft.md` | **YES** — auto-invoke |
+| CI/CD / Hosting | Run `/bootstrap-agents` with confirmed values from `architecture-draft.md` | **YES** — auto-invoke |
+| Commands section | Run `/bootstrap-agents` | **YES** — auto-invoke |
+| `patterns.md` | Run `/bootstrap-agents-provision` | **YES** — auto-invoke |
+| `structure.md` | Run `/create-prd-compile` Step 9.5 | **NO** — hard stop |
+| Cells requiring decisions not yet made | Run `/create-prd-stack` | **NO** — hard stop |
+
+### 4. Auto-Recovery (for YES cells)
+
+If the empty cells are auto-recoverable:
+
+1. **Read `.memory/wiki/specs/architecture-draft.md`** — extract confirmed tech stack decisions (languages, frameworks, databases, ORMs, hosting, auth, CI/CD)
+2. **Build the bootstrap key set** from confirmed decisions
+3. **Execute `/bootstrap-agents`** with those keys — read `.codex/skills/bootstrap-agents/SKILL.md` and run BOTH shards (fill + provision)
+4. **Re-read the surface stack map** after bootstrap completes
+5. **Re-check the required cells** — if now filled → proceed. If still empty → escalate to hard stop (Step 5)
+
+> This auto-recovery fires silently. Do NOT ask the user "should I run bootstrap?" — just run it. Bootstrap is idempotent and safe.
+
+### 5. Hard Stop (for NO cells or failed auto-recovery)
+
+> **HARD STOP** — The surface stack map has empty cells that cannot be auto-recovered.
+>
+> | Empty Cell | Required Action |
+> |---|---|
+> | [cell name] | [what needs to happen] |
+>
+> Do NOT proceed. Do NOT use conversation-confirmed values. Do NOT apply timing fallbacks.
+
+---
+
+## What This Replaces
+
+This protocol replaces all instances of the timing fallback pattern:
+
+> ~~"If a cell is empty but the value was just confirmed in the current conversation... proceed using the conversation-confirmed value"~~
+
+That pattern is **permanently banned**. It creates an escape hatch that allows agents to bypass map guards entirely. If a cell is empty and auto-recovery fails, the upstream workflow that should have filled it has a bug. Surface the bug, don't work around it.

package/template/.codex/skills/prd-templates/references/operational-templates.md

@@ -0,0 +1,116 @@
+# Operational Templates
+
+Templates for operational artifacts produced during planning, assessment, and provisioning workflows.
+
+---
+
+## Slice Acceptance Criteria
+
+Use when writing slice entries during `/plan-phase` Step 4:
+
+```markdown
+### Slice N: [Name]
+**Size**: S/M/L
+**Surfaces**: Contract, API, DB, UI
+
+#### Tasks
+- [ ] Contract: {{CONTRACT_LIBRARY}} schema for [entity] ← no tag (orchestrator handles sequentially)
+- [ ] `BE` API endpoints for [entity] ← backend agent
+- [ ] `FE` [entity] page and components ← frontend agent
+- [ ] `QA` Integration tests for [entity] ← QA agent (runs FIRST to write failing tests, AND after BE+FE to verify)
+
+#### Acceptance Criteria
+- [ ] Given [context], when [action], then [result]
+- [ ] Given [context], when [error condition], then [error response]
+- [ ] [Performance/security criteria if applicable]
+
+#### Dependencies
+- Requires: Slice M
+- Enables: Slice P
+```
+
+---
+
+## Remediation State
+
+Use when writing `.memory/wiki/specs/audits/remediation-state.md` during `/remediate-pipeline-assess`:
+
+```markdown
+# Remediation State
+
+> Generated: [ISO 8601 date]
+
+## Layer Status
+
+- vision: [confirmed-clean | unverified-clean | needs-audit | no-content]
+- architecture: [confirmed-clean | unverified-clean | needs-audit | no-content]
+- ia: [confirmed-clean | unverified-clean | needs-audit | no-content]
+- be: [confirmed-clean | unverified-clean | needs-audit | no-content]
+- fe: [confirmed-clean | unverified-clean | needs-audit | no-content]
+
+## Current Layer
+
+[layer — the layer to process next]
+
+## Layers Confirmed Clean This Session
+
+(none yet)
+
+## Notes
+
+[Any relevant context]
+```
+
+---
+
+## Installed Skills List
+
+Use when updating `{{INSTALLED_SKILLS}}` during `/bootstrap-agents-provision` Step 8:
+
+```markdown
+### Default Skills
+- fix-bug — TDD bug fix workflow
+- refactor — Safe refactoring with test verification
+- add-feature — Add feature to existing architecture
+- deploy — Full deployment pipeline
+- pr-review — Structured PR review
+- security-audit — Security review across all layers
+- main-workflow — General development workflow
+- iterate-plan — Tech stack gap analysis
+- setup-session — Session initialization
+- using-git-worktrees — Isolated workspace management
+- github-workflow-automation — GitHub CI/CD patterns
+- audit-context-building — Deep code analysis
+- context7-auto-research — Auto documentation lookup
+- self-improving-agent — Learning from experiences
+
+### Stack Skills
+- [skill-name] — [description] (installed for [STACK_KEY]=[value])
+- ...
+
+### Surface Skills
+- [skill-name] — [description] (installed for [surface] surface)
+- ...
+```
+
+---
+
+## Sync Integration Inventory
+
+Use when building the integration inventory during `/sync-kit` Step 5a:
+
+```markdown
+## New Kit Content Since Last Sync
+
+### New Rules
+- [list new rules, e.g. boundary-not-placeholder]
+
+### New Skills
+- [list new skills, e.g. parallel-agents, parallel-debugging]
+
+### Changed Rules/Instructions
+- [list what changed, e.g. tdd-always now references BOUNDARY stubs]
+
+### New Concepts
+- [list new concepts, e.g. boundary stubs, file ownership, synthesis protocol]
+```

package/template/.codex/skills/prd-templates/references/persona-completeness-gate.md

@@ -0,0 +1,20 @@
+# Persona Completeness Gate
+
+Applies to every persona in `meta/personas.md` during ideation.
+
+## Required Fields (6)
+
+Every persona must have all 6 fields populated before proceeding past persona exploration:
+
+1. **Name + specific role** — not generic ("Shop Owner" not "User")
+2. **Specific pain point** — the problem this product solves for them
+3. **Current workaround** — how they solve it today without this product
+4. **Success criteria** — what "solved" looks like for them (measurable)
+5. **Switching trigger** — what event would make them adopt this product
+6. **Edge case or constraint** — at least one thing unique to this persona (regulatory, workflow, scale)
+
+## Enforcement
+
+If any field is absent for any persona → probe the user before proceeding.
+
+Reference: `.codex/skills/pipeline-rubrics/references/ideation-rubric.md` Dimension 2.

package/template/.codex/skills/prd-templates/references/placeholder-guard-template.md

@@ -0,0 +1,21 @@
+# Placeholder Guard — Hard Stop Template
+
+Use this template in any workflow `## 0. Placeholder guard` step to emit a hard stop when required placeholders are unfilled.
+
+## Hard Stop Message Format
+
+Emit one block per unfilled placeholder:
+
+> ❌ **Bootstrap incomplete — cannot proceed.**
+>
+> **Unfilled placeholder:** `{{PLACEHOLDER_NAME}}`
+>
+> **Recovery:** If `.memory/wiki/specs/*-architecture-design.md` exists, read it and extract the confirmed [tech decision] value, then run `/bootstrap-agents` with `KEY=<confirmed-value>`. If no architecture design document exists, run `/create-prd-stack` first to confirm tech stack decisions.
+>
+> **Why this matters:** [specific step] cannot produce correct output without this skill — [concrete consequence of proceeding without it].
+
+## Guard Procedure
+
+1. For each placeholder listed in the workflow's `requires_placeholders` frontmatter, check whether the literal characters `{{` still appear in the value.
+2. If **any** are unfilled, emit the hard stop message above (one block per unfilled placeholder) and **do not proceed** to the next step.
+3. Only proceed when **all** required placeholders report no literal `{{` characters.

package/template/.codex/skills/prd-templates/references/placeholder-workflow-mapping.md

@@ -0,0 +1,50 @@
+# Map Column Reference
+
+Maps surface stack map columns and cross-cutting categories to the workflows that consume them.
+
+> **How workflows use the map**: See `.codex/instructions/tech-stack.md` for the surface stack map format and resolution rules. Workflows determine their surface context (from shard directory or slice surface tag), then look up the corresponding row and column.
+
+## Per-Surface Columns
+
+| Column | Workflows That Consume It |
+|--------|--------------------------|
+| **Languages** | write-be-spec-classify, write-fe-spec-classify, implement-slice-setup, implement-slice-tdd, evolve-contract |
+| **BE Frameworks** | write-be-spec-classify |
+| **FE Frameworks** | write-fe-spec-classify |
+| **FE Design** | write-fe-spec-classify |
+| **ORMs** | create-prd-architecture, write-be-spec-classify, implement-slice-setup, verify-infrastructure, validate-phase |
+| **State Mgmt** | write-fe-spec-classify, implement-slice-setup |
+| **Databases** | create-prd-architecture, write-architecture-spec-design, write-be-spec-classify |
+| **Unit Tests** | create-prd-compile, write-be-spec-classify, implement-slice-setup, implement-slice-tdd, evolve-contract |
+| **E2E Tests** | create-prd-compile, implement-slice-tdd, validate-phase |
+| **Test Cmd** | implement-slice-tdd, validate-phase, evolve-contract |
+| **Validation Cmd** | implement-slice-tdd, validate-phase, evolve-contract |
+| **Lint Cmd** | validate-phase |
+| **Build Cmd** | validate-phase |
+| **Dev Cmd** | verify-infrastructure |
+| **Package Mgr** | bootstrap-agents-fill |
+
+## Cross-Cutting Categories
+
+| Category | Workflows That Consume It |
+|----------|--------------------------|
+| **Auth** | create-prd-security, write-be-spec-classify |
+| **CI/CD** | create-prd-compile, decompose-architecture-structure, plan-phase-write, verify-infrastructure, validate-phase |
+| **Hosting** | create-prd-architecture, decompose-architecture-structure, plan-phase-write, verify-infrastructure, validate-phase |
+| **Security** | create-prd-security, write-architecture-spec-design, validate-phase |
+| **API Design** | create-prd-architecture, write-architecture-spec-design, write-be-spec-classify |
+| **Accessibility** | write-fe-spec-classify, write-fe-spec-write, write-architecture-spec-design, validate-phase |
+| **Contract Library** | tdd-contract-first rule, implement-slice-setup |
+
+## Surface Context Resolution
+
+How each workflow determines which surface's row to read:
+
+| Workflow Type | Resolution Method |
+|--------------|-------------------|
+| Spec-writing (`write-be-spec`, `write-fe-spec`) | Shard directory path: `.memory/wiki/specs/be/desktop/` → surface `desktop`; flat `.memory/wiki/specs/be/` → surface `shared` |
+| Implementation (`implement-slice`) | Slice's `surface:` tag from the phase plan |
+| Planning (`plan-phase`) | Iterates ALL surfaces in the map |
+| Validation (`validate-phase`) | Runs per-surface commands for all surfaces |
+| Cross-cutting (`verify-infrastructure`) | Uses cross-cutting table + primary surface for commands |
+| Architecture (`create-prd-*`) | Map may be incomplete during these workflows — falls back to inline conversation context |