cfsa-antigravity 2.5.0 → 2.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cfsa-antigravity",
-  "version": "2.5.0",
+  "version": "2.7.0",
   "description": "CFSA Pipeline — Constraint-First Specification Architecture for AI agents. Production-grade from line one.",
   "scripts": {
     "changeset": "changeset",

package/template/.agent/kit-sync.md

@@ -1,6 +1,6 @@
 # Kit Sync State
 
 upstream: https://github.com/RepairYourTech/cfsa-antigravity
-last_synced_commit: dcc4be60e1815572706beb831a87daed6d7b0f14
-last_synced_at: 2026-03-17T00:12:26Z
-kit_version: 2.5.0
+last_synced_commit: b0f13b49de8b5d929395c6974898ae091a6cf252
+last_synced_at: 2026-03-17T01:44:25Z
+kit_version: 2.7.0

package/template/.agent/workflows/create-prd-architecture.md

@@ -36,6 +36,12 @@ Read the surface stack map from `.agent/instructions/tech-stack.md`. Check the f
 
 If cells are empty AND the value hasn't been confirmed in conversation → **HARD STOP**: tell the user to run `/create-prd-stack` first.
 
+Read `## Engagement Tier` from `docs/plans/ideation/ideation-index.md`.
+
+**Tier behavior for architecture decisions:**
+- 🤖 **Auto**: Agent designs system architecture + data strategy via Deep Think. Writes reasoning. Marks decisions `[AUTO-CONFIRMED]`. User reviews at end of shard.
+- 🤝 **Hybrid** / 💬 **Interactive**: Present each major section, walk through, wait for user confirmation (current behavior).
+
 ---
 
 ## 4. System architecture

package/template/.agent/workflows/create-prd-compile.md

@@ -38,6 +38,12 @@ Read the surface stack map from `.agent/instructions/tech-stack.md`. Check the f
 
 If cells are empty AND the value hasn't been confirmed in conversation → **HARD STOP**: tell the user to run `/create-prd-stack` first.
 
+Read `## Engagement Tier` from `docs/plans/ideation/ideation-index.md`.
+
+**Tier behavior for compile decisions:**
+- 🤖 **Auto**: Agent selects methodology, phasing, and performance budgets via Deep Think. Writes reasoning. Marks `[AUTO-CONFIRMED]`. User reviews compiled documents.
+- 🤝 **Hybrid** / 💬 **Interactive**: Present each decision, wait for user confirmation (current behavior).
+
 ---
 
 ## 8. Development methodology

package/template/.agent/workflows/create-prd-design-system.md

@@ -29,9 +29,11 @@ Establish the structural UI architecture — navigation paradigm, layout grid, p
 2. Scan for any `{{PLACEHOLDER}}` values that are still unfilled. If any exist → **stop** and tell the user: _"Design direction hasn't been confirmed yet. Run `/create-prd-stack` first to establish the design direction before designing the system."_
 3. If all placeholders are filled → extract and store for this session: the confirmed `DESIGN_DIRECTION`, color palette, typography choices, motion philosophy, and anti-patterns.
 
----
+Read `## Engagement Tier` from `docs/plans/ideation/ideation-index.md`.
 
-## 1. Read source documents
+**Tier behavior for design system decisions** (all 7 decisions are product decisions):
+- 🤖 **Auto**: Agent selects based on design direction + constraints via Deep Think. Writes reasoning. Marks `[AUTO-CONFIRMED]`. User reviews compiled `design-system.md` at Step 9.
+- 🤝 **Hybrid** / 💬 **Interactive**: Present options, wait for explicit confirmation per decision (current behavior).
 
 1. Read `docs/plans/ideation/meta/constraints.md` — extract the **Project Surfaces** section. Read `docs/plans/ideation/ideation-index.md` — extract the feature inventory from the MoSCoW Summary.
 2. Read `.agent/skills/brand-guidelines/SKILL.md` — extract the confirmed `DESIGN_DIRECTION`.

package/template/.agent/workflows/create-prd-security.md

@@ -37,6 +37,12 @@ Read the surface stack map from `.agent/instructions/tech-stack.md`. Check the f
 
 If cells are empty AND the value hasn't been confirmed in conversation → **HARD STOP**: tell the user to run `/create-prd-stack` first.
 
+Read `## Engagement Tier` from `docs/plans/ideation/ideation-index.md`.
+
+**Tier behavior for security decisions:**
+- 🤖 **Auto**: Agent designs security model + attack surface + integrations via Deep Think. Writes reasoning. Marks `[AUTO-CONFIRMED]`. User reviews at end of shard.
+- 🤝 **Hybrid** / 💬 **Interactive**: Present each section, walk through, wait for user confirmation (current behavior).
+
 ---
 
 ## 6. Security model

package/template/.agent/workflows/create-prd-stack.md

@@ -27,7 +27,11 @@ Build the decision constraints map from the ideation output, then walk through e
 
 Before any tech stack decision, read `docs/plans/ideation/meta/constraints.md` to build the **decision constraints map**.
 
-Also read `docs/plans/ideation/ideation-index.md` — specifically the `## Structural Classification` section. This is the **authoritative source** for the project's surface list and project shape (`single-surface`, `multi-surface-shared`, `multi-product-hub`, or `multi-product-peer`). Use this to determine which decision axes apply and whether tech stack decisions need to be made per-surface.
+Also read `docs/plans/ideation/ideation-index.md` — specifically `## Structural Classification` (authoritative surface list and project shape) and `## Engagement Tier` (gate behavior for this session).
+
+**Tier behavior for tech stack decisions:**
+- 🤖 **Auto**: Agent uses constraints + Deep Think to select best-fit option per axis. Records reasoning. Writes decisions. User reviews all stack decisions at end of shard.
+- 🤝 **Hybrid** / 💬 **Interactive**: Present options, wait for user confirmation per axis (current behavior).
 
 Build the constraints map:
 
@@ -35,7 +39,7 @@ Build the constraints map:
 2. **Surface constraints** — the project surfaces (from structural classification) constrain framework choices. For multi-product projects, some axes may need separate decisions per surface (e.g., different frontend frameworks for web vs desktop vs mobile).
 3. **Soft constraints** — preferences that should bias decisions but aren't hard rules
 
-Present the constraints map to the user before starting tech decisions. Constraints narrow the option space — some decisions may be obvious. Skip those with a brief rationale.
+Present the constraints map to the user before starting tech decisions *(Interactive/Hybrid)* or auto-confirm with Deep Think reasoning *(Auto)*. Constraints narrow the option space — some decisions may be obvious. Skip those with a brief rationale.
 
 Read `.agent/skills/tech-stack-catalog/references/constraint-questions.md` for the per-axis constraint questions to ask before presenting options.
 
@@ -54,7 +58,7 @@ Score Fit from 1–5 based on how well the option matches the constraints map. I
 1. Ask the constraint questions for this axis
 2. Filter options based on answers
 3. Present the filtered option table with recommendation
-4. Wait for user confirmation
+4. **Interactive/Hybrid**: Wait for user confirmation. **Auto**: Select highest-fit option via Deep Think, write reasoning to `architecture-draft.md`, mark as `[AUTO-CONFIRMED]`.
 5. Fire bootstrap with only that key: read `.agent/workflows/bootstrap-agents.md` and call with `PIPELINE_STAGE=create-prd` + the confirmed key
 6. Move to next axis
 
@@ -64,7 +68,7 @@ Score Fit from 1–5 based on how well the option matches the constraints map. I
 >
 > These are independent MANIFEST entries. Firing bootstrap with `BACKEND_FRAMEWORK=Hono` does **not** provision the tRPC skill — `API_LAYER=tRPC` must be fired separately. Similarly, skipping the `Database` axis (handled by the Persistence Map Interview) does not affect backend framework or API layer keys — those must still fire individually.
 
-Get explicit user decisions — no "TBD" allowed. Use the brainstorming skill's approach — one decision at a time.
+Get explicit user decisions *(Interactive/Hybrid)* or auto-select with Deep Think reasoning *(Auto)* — no "TBD" allowed. Use the brainstorming skill's approach — one decision at a time.
 
 > **Decision recording**: For each confirmed tech stack decision, read `.agent/skills/session-continuity/protocols/06-decision-analysis.md` and follow the **Decision Effect Analysis Protocol**. Tech stack choices have high downstream impact (they constrain frameworks, skills, deployment, and testing). Record each decision to `memory/decisions.md` with upstream/downstream effects.
 

package/template/.agent/workflows/create-prd.md

@@ -44,6 +44,17 @@ Use the **Structure Map** in `ideation-index.md` to locate specific files:
 
 Pay special attention to the **Project Surfaces** section in `meta/constraints.md` — it determines which tech stack axes apply.
 
+Also read `## Engagement Tier` from `ideation-index.md`. If not set during ideation, ask now:
+
+> **How involved do you want to be?**
+> 1. 🤖 **Auto** — I design the full architecture via Deep Think. You review the compiled output.
+> 2. 🤝 **Hybrid** *(recommended)* — Structural steps auto. Architecture/product decisions pause for you.
+> 3. 💬 **Interactive** — I pause at every step.
+
+**Wait for user answer.** If an ideation tier exists, present it as default. Write to `ideation-index.md` immediately.
+
+Each shard reads the tier and adapts gates: **Auto** = all gates auto-confirm with Deep Think reasoning. **Hybrid** = structural auto, architecture/product pause. **Interactive** = all pause.
+
 ---
 
 ## 2. Load skills

package/template/.agent/workflows/ideate-discover.md

@@ -29,6 +29,19 @@ Read `.agent/skills/idea-extraction/SKILL.md` — follow the Recursive Domain Ex
 
 Read `## Expansion Mode` and `## Structural Classification` from `docs/plans/ideation/ideation-index.md`.
 
+## 2.5. Read Engagement Tier
+
+Read `## Engagement Tier` from `docs/plans/ideation/ideation-index.md`. Apply gate behavior rules for this session:
+
+| Tier | Structural gates (domain maps, classification, sub-domain structure) | Product gates (personas, MoSCoW, feature scope, competitive positioning) |
+|------|----------------------------------------------------------------------|-------------------------------------------------------------------------|
+| 🤖 **Auto** | Auto-confirm: apply Deep Think, write reasoning to feature files, proceed | Auto-confirm: apply Deep Think, write reasoning to feature files, proceed |
+| 🤝 **Hybrid** | Auto-confirm: apply Deep Think, write reasoning to feature files, proceed | **Pause for user**: present findings, wait for explicit confirmation |
+| 💬 **Interactive** | **Pause for user**: present findings, wait for explicit confirmation | **Pause for user**: present findings, wait for explicit confirmation |
+
+> [!IMPORTANT]
+> **Auto-confirmed gates must still write.** When a gate is auto-confirmed, the agent writes the Deep Think reasoning and decision to the relevant file immediately — just as if the user had confirmed it. The file trail must be identical regardless of tier. This ensures the Auto tier review checkpoint in `ideate-validate` has full traceability.
+
 ### Full Mode (recommended for 3+ domains)
 
 #### Level 0 — Global Domain Map
@@ -42,7 +55,7 @@ Read `## Expansion Mode` and `## Structural Classification` from `docs/plans/ide
    - In the relevant parent's CX file (surface CX or global CX)
    - In `ideation-cx.md` if cross-surface
 5. Update `ideation-index.md` structure map with paths
-6. **Gate**: Present domain map. User confirms before Level 1.
+6. **Gate** *(structural)*: Present domain map. **Interactive/Hybrid**: User confirms before Level 1. **Auto**: Auto-confirm with Deep Think reasoning written to `ideation-index.md`.
 
 #### Level 1 — Domain Breadth Sweep
 
@@ -57,7 +70,7 @@ For each domain (dependency order — foundational first):
 5. Note cross-cuts in the domain's CX file
 6. **NEW DOMAINS DISCOVERED?** → Classify, create, update index, loop to Level 0
 7. Mark domain status as `[BREADTH]`
-8. **Gate**: Pause after EACH domain. "Here's what I mapped for [Domain]. Missing anything?" After ALL: "All domains at BREADTH. Ready to drill?"
+8. **Gate** *(structural)*: Pause after EACH domain. **Interactive/Hybrid**: "Here's what I mapped for [Domain]. Missing anything?" After ALL: "All domains at BREADTH. Ready to drill?" **Auto**: Auto-confirm with Deep Think reasoning written to domain index.
 
 #### Level 2+ — Vertical Drilling
 
@@ -71,9 +84,9 @@ For each domain (dependency order), for each child:
 6. Cross-cuts with evidence → add to parent's CX file with synthesis questions
 7. **Feature reveals 2+ interacting capabilities?** → Run **Promotion Protocol** (convert .md to folder)
 8. **NEW DOMAINS DISCOVERED?** → Loop to Level 0
-9. When Deep Think yields zero hypotheses AND user confirms → mark `[EXHAUSTED]`
+9. When Deep Think yields zero hypotheses AND user confirms (or auto-confirms for Auto tier) → mark `[EXHAUSTED]`
 10. Status propagation: all children `[EXHAUSTED]` → node is `[EXHAUSTED]`
-11. **Gate**: Pause after each domain is drilled.
+11. **Gate** *(product)*: Pause after each domain is drilled. **Interactive**: Full review. **Hybrid**: Pause for review. **Auto**: Auto-confirm with Deep Think reasoning written to domain index.
 
 #### Cross-Cut Synthesis (Continuous)
 

package/template/.agent/workflows/ideate-extract.md

@@ -19,7 +19,7 @@ pipeline:
 
 Classify the user's input, create the fractal `ideation/` folder structure, and load skills.
 
-**Prerequisite**: If invoked standalone (not from `/ideate`), verify the user has provided input — either an `@file` reference or a verbal description. If no input is provided, prompt: "What would you like to build? Describe your idea, or provide a file with `/ideate-extract @path/to/file.md`."
+**Prerequisite**: If standalone, verify user provided input via `@file` or verbal. If none, prompt: \"What would you like to build? Provide a file or describe your idea.\"
 
 ---
 
@@ -170,27 +170,30 @@ For each concept classified as **domain** in the confirmed table:
 - **Thin document**: Create domain folders with depth markers on feature files.
 - **Verbal / one-liner**: Create domain folders with scaffolding. Feature files are `[SURFACE]`.
 
-## 1.6. User Intent Check (ALL input types)
+## 1.6. Engagement Tier Selection (ALL input types)
 
-Read `.agent/skills/brainstorming/SKILL.md` and follow its methodology.
+All three tiers are available for all input types. Present with the recommended default for this input type (Rich/Thin/Chat → Hybrid, Verbal → Interactive):
 
-After seeding, present a summary and ask how the user wants to proceed. Present all options:
+> **How involved do you want to be?**
+> 1. 🤖 **Auto** — I explore independently via Deep Think. You review at the end.
+> 2. 🤝 **Hybrid** *(recommended)* — Structural stuff auto, product decisions pause for you.
+> 3. 💬 **Interactive** — I pause at every gate. Full interview mode.
 
-1. **Full exploration** *(recommended for 3+ domains)* — Recursive breadth-before-depth with Deep Think
-2. **Process as-is** — Proceed with what's captured; fill gaps as they arise
-3. **Expand vertically** — Drill deeper into existing features
-4. **Expand horizontally** — Add new feature domains not yet covered
-5. **Explore cross-cutting concerns** — Map how existing features interact
-6. **Combination** — User specifies dimensions and order
-7. **Audit ambiguity first** — Run inline check before deciding
+**Wait for user answer.** Write the engagement tier to `ideation-index.md` under `## Engagement Tier` immediately.
 
-**Wait for user answer — do not assume.**
+## 1.6.5. Expansion Mode Selection (ALL input types)
 
-## 1.7. Expansion Mode Routing
+Present expansion mode options:
 
-Write the expansion mode to `ideation-index.md` per the super-index template.
+1. **Full exploration** *(recommended for 3+ domains)* — Breadth-before-depth with Deep Think
+2. **Process as-is** — Proceed with what's captured
+3. **Expand vertically** — Drill deeper into existing features
+4. **Expand horizontally** — Add new domains
+5. **Cross-cutting concerns** — Map feature interactions
+6. **Combination** — User specifies dimensions and order
+7. **Audit ambiguity first** — Inline check before deciding
 
-This flag is read by `ideate-discover.md` to shape exploration behavior.
+**Wait for user answer.** Write expansion mode to `ideation-index.md` under `## Expansion Mode` immediately.
 
 ## 2. Load skills
 

package/template/.agent/workflows/ideate-validate.md

@@ -23,6 +23,14 @@ Explore constraints, verify domain exhaustion, and compile the vision summary.
 
 ---
 
+## 7.5. Read Engagement Tier
+
+Read `## Engagement Tier` from `docs/plans/ideation/ideation-index.md`. Apply to gates in this shard:
+
+- **Auto**: Steps 8 (constraints, metrics, competitive positioning) → agent self-interviews using Deep Think, writes answers to files. Step 10.5 (below) provides a review checkpoint before compilation.
+- **Hybrid**: Steps 8 product decisions → pause for user. Structural checks → auto.
+- **Interactive**: All steps pause for user confirmation.
+
 ## 8. Constraints and metrics
 
 Read `.agent/skills/idea-extraction/SKILL.md` and follow its Deep Think Protocol.
@@ -40,7 +48,11 @@ Explore constraints with the user. Write to `docs/plans/ideation/meta/constraint
 
 **Deep Think**: "Based on the product type and user personas, what constraints would I expect that haven't been mentioned? For example, does this product handle payments (PCI)? Does it serve minors (COPPA)? Does it store health data (HIPAA)?"
 
-Write constraints to `meta/constraints.md`. If the surface classification changed, update `ideation-index.md` `## Structural Classification` section.
+**Interactive/Hybrid**: Present each constraint question to user, wait for answers. Write each confirmed constraint to `meta/constraints.md` immediately.
+
+**Auto**: Self-interview using Deep Think. Write all answers with reasoning to `meta/constraints.md` immediately. Mark each answer as `[AUTO-CONFIRMED]` for traceability.
+
+If the surface classification changed, update `ideation-index.md` `## Structural Classification` section.
 
 ### Success metrics
 
@@ -113,6 +125,19 @@ If proportionality fails, return to `/ideate-discover` for the under-explored ar
 
 ---
 
+## 10.5. Auto Tier Review Checkpoint (Auto tier only)
+
+If engagement tier is **Auto**, present a comprehensive review before compilation:
+
+1. **List all auto-confirmed decisions** with their Deep Think reasoning — from domain classification, feature drilling, constraints, personas, competitive positioning
+2. **Highlight any `[AUTO-CONFIRMED]` entries** in `meta/constraints.md`, `meta/personas.md`, and `meta/competitive-landscape.md`
+3. **Present for review**: "I explored your idea independently. Here's everything I decided and why. Override anything before I compile the vision."
+4. **Wait for user response.** Apply any overrides. Write corrections to files immediately.
+
+For **Hybrid** and **Interactive** tiers, skip this step — the user already confirmed during exploration.
+
+---
+
 ## 11. Compile vision document
 
 Read `.agent/skills/prd-templates/references/vision-template.md` for the output template.

package/template/.agent/workflows/ideate.md

@@ -29,7 +29,26 @@ shards: [ideate-extract, ideate-discover, ideate-validate]
 | One-liner / verbal | User describes idea in chat, no files | Interview (deep) — builds vision from scratch domain by domain |
 | Full exploration | Any input with 3+ domains | Full — Recursive breadth-before-depth with Deep Think protocol, cross-cut detection active throughout |
 
-**Quality guarantee**: All input types produce the **same output quality** using the same fractal structure. The ideation output from a one-liner is structurally identical to one from a rich document. Every node has an index, CX file, and children. Every feature has a Role Lens. Only the amount of interview work differs.
+### Engagement Tiers
+
+After input classification, the user chooses how much involvement they want. All tiers are available for all input types — the pipeline recommends a default but the user picks.
+
+| Tier | Gate behavior | Default for |
+|------|---------------|-------------|
+| 🤖 **Auto** | Pipeline uses Deep Think to self-interview at every gate. User reviews compiled output at the end. | — |
+| 🤝 **Hybrid** | Structural/mechanical gates auto-confirm. Product decisions (personas, MoSCoW, competitive positioning, constraints) pause for user. | Rich doc, thin doc, chat transcript |
+| 💬 **Interactive** | Every gate pauses for explicit user confirmation. | Verbal / one-liner |
+
+**Full matrix — Input × Tier:**
+
+| Input Type | 🤖 Auto | 🤝 Hybrid | 💬 Interactive |
+|---|---|---|---|
+| Rich document | AI extracts + self-interviews gaps | AI extracts, pauses for product calls | AI extracts, pauses at every gate |
+| Thin document | AI expands all domains independently | AI expands, pauses for product calls | AI expands with user at every step |
+| Chat transcript | AI filters noise + self-interviews | AI filters, pauses for product calls | AI filters with user validation |
+| Verbal / one-liner | AI generates vision from scratch via Deep Think | AI generates, pauses for product calls | Full traditional interview |
+
+**Quality guarantee**: All input types and engagement tiers produce the **same output quality** using the same fractal structure. The ideation output from an Auto one-liner is structurally identical to an Interactive rich document. Every node has an index, CX file, and children. Every feature has a Role Lens. Only the amount of human involvement differs.
 
 Transform a raw idea into comprehensive, structured ideation output through exhaustive recursive exploration with the Deep Think protocol.
 
@@ -63,9 +82,9 @@ Check whether `docs/plans/ideation/ideation-index.md` already exists.
 
 | # | Shard | What It Does |
 |---|-------|-------------|
-| 1 | [`ideate-extract`](.agent/workflows/ideate-extract.md) | Classifies input, determines structural classification (4 shapes), creates fractal `ideation/` folder structure using Node Classification Gate, seeds domain folders, runs user intent check, sets expansion mode, loads skills |
-| 2 | [`ideate-discover`](.agent/workflows/ideate-discover.md) | Recursive breadth-before-depth exploration with Deep Think. Creates fractal nodes (folders with index + CX) and leaf feature files (with Role Lens). Hierarchical CX detection active throughout. |
-| 3 | [`ideate-validate`](.agent/workflows/ideate-validate.md) | Constraints, metrics, competitive positioning, leaf-node exhaustion check, fractal structure compliance, vision summary compilation |
+| 1 | [`ideate-extract`](.agent/workflows/ideate-extract.md) | Classifies input, determines structural classification (4 shapes), creates fractal `ideation/` folder structure using Node Classification Gate, seeds domain folders, asks engagement tier + expansion mode, loads skills |
+| 2 | [`ideate-discover`](.agent/workflows/ideate-discover.md) | Recursive breadth-before-depth exploration with Deep Think. Gate behavior controlled by engagement tier. Creates fractal nodes (folders with index + CX) and leaf feature files (with Role Lens). Hierarchical CX detection active throughout. |
+| 3 | [`ideate-validate`](.agent/workflows/ideate-validate.md) | Constraints, metrics, competitive positioning, leaf-node exhaustion check, fractal structure compliance, vision summary compilation. Auto tier gets a review checkpoint before compilation. |
 
 ---
 
@@ -73,7 +92,7 @@ Check whether `docs/plans/ideation/ideation-index.md` already exists.
 
 ### Step 1 — Run `.agent/workflows/ideate-extract.md`
 
-Classifies the user's input (rich doc, thin PRD, chat transcript, verbal), determines structural classification (single-surface, multi-surface-shared, multi-product-hub, multi-product-peer), checks for existing ideation folder (re-run check), creates the fractal `docs/plans/ideation/` folder structure using the Node Classification Gate, runs user intent check to determine expansion mode, sets the expansion mode flag in `ideation-index.md`, and loads skills.
+Classifies the user's input (rich doc, thin PRD, chat transcript, verbal), determines structural classification (single-surface, multi-surface-shared, multi-product-hub, multi-product-peer), checks for existing ideation folder (re-run check), creates the fractal `docs/plans/ideation/` folder structure using the Node Classification Gate, asks user to choose engagement tier (Auto/Hybrid/Interactive) and expansion mode, writes both to `ideation-index.md` immediately, and loads skills.
 
 ### Step 2 — Run `.agent/workflows/ideate-discover.md`