cfsa-antigravity 2.6.0 → 2.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "cfsa-antigravity",
-  "version": "2.6.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: 3b681461bb17210e795e7a4d05a3393ba1e57438
-last_synced_at: 2026-03-17T01:38:22Z
-kit_version: 2.6.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