cfsa-antigravity 2.0.0 → 2.2.0

package/template/.agent/skills/prd-templates/references/fractal-feature-template.md

@@ -0,0 +1,93 @@
+# Feature: {Feature Name}
+
+> **Number**: {NN.NN.NN}
+> **Parent**: [{sub-domain-name}](./{sub-domain}-index.md)
+> **Status**: [SURFACE] / [PARTIAL] / [DEEP] / [EXHAUSTED]
+> **Last updated**: {timestamp}
+
+## Overview
+
+_What this feature is, why it exists, what user problem it solves. 2-3 sentences._
+
+## Role Lens
+
+| Role | Access | What They See/Do |
+|------|--------|-------------------|
+| {Persona 1} | Full | _specific behavior for this role — actions, views, capabilities_ |
+| {Persona 2} | Config | _specific behavior — what they configure, what they see_ |
+| {Persona 3} | Read-only | _specific behavior — what they can view, what's hidden_ |
+| {Persona 4} | None | _not visible — brief note on why or what they see instead_ |
+
+> **Access levels**: Full · Config · Read-only · Reports · None
+>
+> **Rules:**
+> - Every feature file MUST have a Role Lens table — no exceptions
+> - Use persona names from `meta/personas.md`
+> - "What They See/Do" must be SPECIFIC to this feature, not generic role descriptions
+> - If a persona has "None" access, still list them — the explicit absence is valuable for downstream spec writers
+> - This is the implementation-ready detail that IA/BE/FE spec writers consume directly
+
+## Behavior
+
+_Detailed description of the feature's behavior._
+
+### Happy Path
+
+_Step-by-step user interaction for the normal/expected case. Number each step._
+
+1. _User does X_
+2. _System responds with Y_
+3. _User confirms Z_
+4. _System completes action, shows confirmation_
+
+### Edge Cases / Failure Modes
+
+| Scenario | What Happens | User Sees |
+|----------|-------------|-----------|
+| _edge case 1_ | _system behavior_ | _error message or fallback UI_ |
+| _edge case 2_ | _system behavior_ | _error message or fallback UI_ |
+
+### States
+
+| State | Trigger | What User Sees |
+|-------|---------|---------------|
+| Loading | _action initiated_ | _spinner, skeleton, progress bar_ |
+| Empty | _no data exists yet_ | _empty state with CTA_ |
+| Populated | _data loaded_ | _populated view_ |
+| Error | _request failed_ | _error message with retry option_ |
+| Partial | _incomplete data_ | _partial view with missing-data indicator_ |
+
+## Deep Think Annotations
+
+| # | Hypothesis | Source | Outcome |
+|---|-----------|--------|---------|
+| DT-01 | _hypothesis about what this feature needs_ | _reasoning or industry precedent_ | ✅ CONFIRMED / ❌ REJECTED: _reason_ |
+
+> Log every Deep Think hypothesis — both confirmed and rejected. This is the audit trail showing the agent explored beyond the obvious.
+
+## Cross-Cut Notes
+
+_Quick references to how this feature interacts with features in other domains/sub-domains. These are pointers — detailed cross-cut analysis lives in the parent's CX file._
+
+- Touches **{Domain/Sub-domain/Feature}** ([path](../../../path)) — _why: shared entity, trigger dependency, permission, etc._
+- Consumed by **{Surface/Domain}** via API — _why: spoke surface reads this data through platform API_
+
+> For detailed cross-cut analysis (synthesis questions, role scoping), see the CX file at the appropriate level.
+
+## Decisions
+
+| # | Decision | Context |
+|---|----------|---------|
+| D-01 | _what was decided_ | _why this was the right call_ |
+
+## Open Questions
+
+| # | Question | Owner | Deferred To |
+|---|----------|-------|-------------|
+| Q-01 | _question_ | User / Agent / /create-prd | _pipeline stage_ |
+
+> **Notes for agents:**
+> - Feature files are LEAF NODES — they are `.md` files, never folders
+> - If a feature reveals 2+ interacting capabilities during drilling, it should be PROMOTED to a sub-domain (see Reactive Depth Protocol in `idea-extraction/SKILL.md`)
+> - Status markers: `[SURFACE]` = identified only, `[PARTIAL]` = some depth, `[DEEP]` = all sections filled with edge cases, `[EXHAUSTED]` = Deep Think yields zero hypotheses + user confirms nothing missing
+> - The Role Lens is the PRIMARY output consumed by `/write-fe-spec` and `/write-be-spec` — make it thorough

package/template/.agent/skills/prd-templates/references/fractal-node-index-template.md

@@ -0,0 +1,55 @@
+# {Node Name} — Index
+
+> **Level**: {surface | domain | sub-domain}
+> **Parent**: [{parent-name}](../{parent}-index.md)
+> **Status**: [SURFACE] / [BREADTH] / [DEEP] / [EXHAUSTED]
+> **Last updated**: {timestamp}
+
+## Overview
+
+_What this node contains and why it exists. 2-3 sentences describing the domain or sub-domain's purpose and scope._
+
+## Children
+
+| # | Name | Type | Path | Status | Deep Think |
+|---|------|------|------|--------|------------|
+| 01 | _{child-name}_ | domain / sub-domain / feature | [01-slug](./01-slug/) or [01.01-slug.md](./01.01-slug.md) | [SURFACE] | _N hypotheses_ |
+| 02 | ... | ... | ... | ... | ... |
+
+> **Type column values:**
+> - `domain` — a top-level grouping within a surface (folder with index + CX)
+> - `sub-domain` — a grouping within a domain that has 2+ interacting capabilities (folder with index + CX)
+> - `feature` — a leaf node describing a single capability (.md file)
+
+## Role Matrix
+
+| Child | {Persona 1} | {Persona 2} | {Persona 3} | {Persona 4} |
+|-------|-------------|-------------|-------------|-------------|
+| 01-child | ✅ Full | ⚙️ Config | 👁️ View | ❌ None |
+| 02-child | ✅ Full | ✅ Full | ❌ None | ❌ None |
+
+> **Legend**: ✅ Full access · ⚙️ Configuration only · 👁️ Read-only · 📊 Reports only · ❌ No access
+>
+> **Rules:**
+> - Persona names come from `meta/personas.md` — use short names (e.g., "Tech", "Owner", "CSR", "Consumer")
+> - NEVER redefine a persona here — reference only
+> - Only list children that exist — the matrix grows as children are added
+> - Access icons are shorthand; detailed per-role behavior lives in each feature file's **Role Lens**
+
+## Decision Log
+
+| # | Decision | Context | Source |
+|---|----------|---------|--------|
+| D-01 | _what was decided_ | _why this was the right call_ | _conversation / document / user directive_ |
+
+## Open Questions
+
+| # | Question | Owner | Deferred To |
+|---|----------|-------|-------------|
+| Q-01 | _question_ | User / Agent / /create-prd | _pipeline stage_ |
+
+> **Notes for agents:**
+> - This template is used at EVERY folder level in the fractal structure (surface, domain, sub-domain)
+> - The content differs by level — a surface index lists domains, a domain index lists sub-domains/features
+> - Status propagates upward: all children `[EXHAUSTED]` → node is `[EXHAUSTED]`; all `[DEEP]`+ → node is `[DEEP]`
+> - When adding a new child, update BOTH the Children table AND the Role Matrix

package/template/.agent/skills/prd-templates/references/ideation-crosscut-template.md

@@ -1,57 +1,36 @@
-# Cross-Cut Ledger
+# Global Cross-Cuts — {{PROJECT_NAME}}
 
-> This ledger is accumulated incrementally at every level of ideation.
-> It is NOT built in a single pass. Each level adds resolution.
-> Never clear entries — this is the audit trail.
+> **Scope**: Cross-surface interactions for multi-product projects, or cross-domain interactions for single-surface projects.
+> **Format**: Index + one-line summary. Detailed synthesis lives in lower-level CX files.
 
-## Ledger
+## Cross-Surface Interaction Map
 
-### Level 0 — Surface Guesses (from domain map)
+> Each row records that an interaction EXISTS between two surfaces or top-level domains. The Detail column links to the lower-level CX file where the full synthesis questions are answered.
 
-_Noted during global domain mapping. Low confidence, not yet validated._
+| # | Source Surface/Domain | Target Surface/Domain | Summary | Roles | Detail |
+|---|----------------------|----------------------|---------|-------|--------|
+| CX-01 | _Web / Consumer Platform_ | _Desktop / Shop Ops_ | _Desktop diagnostic workflow consumes web supplier data via API_ | Tech, Owner | [detail](surfaces/desktop/desktop-cx.md#CX-03) |
+| CX-02 | _Web / Device History_ | _Mobile / Device Guardian_ | _Mobile app syncs with web device history for owner verification_ | Consumer | [detail](surfaces/mobile/mobile-cx.md#CX-01) |
 
-| Domain A | Domain B | Suspected Connection | Status |
-|----------|----------|---------------------|--------|
-| _Domain 01_ | _Domain 05_ | _Likely share customer entity_ | `pending` |
+> **Rules:**
+> - This file is an INDEX with one-line summaries — not the source of truth for cross-cut details
+> - Detailed synthesis (5 questions, role scoping) lives in the lower-level CX file linked in the Detail column
+> - For single-surface projects, this file covers cross-DOMAIN interactions (same content as would appear in a surface-level CX)
+> - For multi-product projects, this file covers cross-SURFACE interactions
+> - Use `CX-NN` numbering. This file's entries are distinct from CX entries in lower-level files.
+> - When referencing from other files, use `ideation-cx.md#CX-NN`
 
-### Level 1 — Sub-Domain Connections (from breadth sweep)
+## Shared Domain Consumption _(multi-product only)_
 
-_Noted during domain breadth mapping. Medium confidence, connection identified at sub-area level._
+> Which shared domains are consumed by which spoke surfaces, and through what mechanism.
 
-| Domain A.Sub-Area | Domain B.Sub-Area | Connection | Status |
-|-------------------|-------------------|------------|--------|
-| _01.Inventory_ | _05.Supplier Catalog_ | _Parts lookup cross-references supplier data_ | `pending` |
+| Shared Domain | Owner | Consumed By | Mechanism | Detail |
+|--------------|-------|-------------|-----------|--------|
+| _Device History_ | Web (hub) | Desktop, Mobile | REST API | [web/02-device-history-cx.md](surfaces/web/02-device-history/device-history-cx.md) |
+| _Payments_ | Web (hub) | Desktop | REST API | [web/03-payments-cx.md](surfaces/web/03-payments/payments-cx.md) |
 
-### Level 2+ — Evidence-Backed (from vertical drilling)
+## Rejected Cross-Surface Pairs
 
-_Confirmed during vertical drilling with specific evidence. High confidence._
-
-| Domain A.Sub-Area.Feature | Domain B.Sub-Area.Feature | Evidence | Status |
-|--------------------------|--------------------------|----------|--------|
-| _02.Inventory.Purgatory_ | _01.Payments.PreAuth_ | _Pre-auth clears purgatory on completion_ | `✅ confirmed` |
-
-## Synthesis Outcomes
-
-For each confirmed pair, the five synthesis questions have been asked and answered.
-
-### [Interaction Name]: Domain A × Domain B
-
-**Connection**: _One-sentence description of the interaction._
-
-1. **Shared state conflict**: _Who owns the entity? What's the merge strategy?_
-2. **Trigger chain**: _Does A trigger B? Rollback if B fails? Sync or async?_
-3. **Permission intersection**: _Does permission in A affect B?_
-4. **Notification fan-out**: _Does event in A notify actors in B?_
-5. **State transition conflict**: _Can A and B race? Data consistency impact?_
-
-**Outcome**: `✅ confirmed → [Interaction Name]` | `❌ rejected: [reason]`
-
----
-
-_Repeat Synthesis Outcomes for each confirmed cross-cut pair._
-
-## Rejected Pairs
-
-| Domain A | Domain B | Reason for Rejection |
-|----------|----------|---------------------|
-| _Domain 03_ | _Domain 07_ | _No shared state, no trigger dependency, independent lifecycles_ |
+| # | Surface A | Surface B | Reason for Rejection |
+|---|-----------|-----------|---------------------|
+| R-01 | _Desktop_ | _Mobile_ | _No direct interaction — both consume web API independently_ |

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

@@ -16,16 +16,31 @@
 - 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_ |
-| SURFACE | _N_ |
-| BREADTH | _N_ |
-| DEEP | _N_ |
-| EXHAUSTED | _N_ |
-| Cross-cut pairs confirmed | _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_ |
 
@@ -42,54 +57,55 @@
 | Competitive Landscape | [competitive-landscape.md](meta/competitive-landscape.md) | _status_ |
 | Constraints | [constraints.md](meta/constraints.md) | _status_ |
 
-### Domain Documents
-
-| # | Domain | Path | Status | Sub-areas | Deep Think |
-|---|--------|------|--------|-----------|------------|
-| 01 | _Domain Name_ | [01-domain-slug.md](domains/01-domain-slug.md) | `[SURFACE]` | _N_ sub-areas | _N_ hypotheses |
-
-### Cross-Cut Ledger
+### Global Cross-Cuts
 
 | Document | Path |
 |----------|------|
-| Cross-Cut Ledger | [cross-cut-ledger.md](cross-cuts/cross-cut-ledger.md) |
+| Global Cross-Cuts | [ideation-cx.md](ideation-cx.md) |
 
-## Domain Map
+### Structure Map
 
-Visual status of all domains with sub-area breakdowns:
+> **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.
 
-```
-Domain 01: [Domain Name] [STATUS]
-  ├── Sub-area A [STATUS] — N sub-topics
-  ├── Sub-area B [STATUS] — N sub-topics
-  └── Sub-area C [STATUS] — N sub-topics
+#### _{Surface Name or "Top-Level Domains" for single-surface}_
 
-Domain 02: [Domain Name] [STATUS]
-  ├── ...
-  └── ...
-```
+| # | Domain | Path | Status | Children | Depth | Deep Think |
+|---|--------|------|--------|----------|-------|------------|
+| 01 | _Domain Name_ | [01-slug/](./01-slug/) | `[SURFACE]` | _N children_ | _N levels_ | _N hypotheses_ |
 
-Status markers: `[SURFACE]` → `[BREADTH]` → `[DEEP]` → `[EXHAUSTED]`
+_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. Each decision links to the domain file where it was made.
+Numbered decisions with source references.
 
 | # | Decision | Source | Domain |
 |---|----------|--------|--------|
-| 1 | _Decision description_ | _Discussion context_ | [domain-file.md](domains/NN-domain.md) |
+| 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_ → Domain NN
-- _Feature 2_ → Domain NN
+- _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_ → Domain NN
+- _Feature 3_ → `web/02.01` ([link](./path))
 
 ### Could Have
-- _Feature 4_ → Domain NN
+- _Feature 4_ → `desktop/01.03.02.04` ([link](./path))
 
 ### Won't Have (Now)
 - _Feature 5_ — Reason for exclusion

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

@@ -14,7 +14,7 @@ Use when writing slice entries during `/plan-phase` Step 4:
 **Surfaces**: Contract, API, DB, UI
 
 #### Tasks
-- [ ] Contract: Zod schema for [entity] ← no tag (orchestrator handles sequentially)
+- [ ] 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)

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

@@ -1,21 +1,50 @@
-# Placeholder → Workflow Mapping
-
-Maps tech stack placeholders to the source keys and consuming workflows.
-
-| Placeholder | Source Key | Workflows |
-|---|---|---|
-| `{{DATABASE_SKILLS}}` | `DATABASE_*` (accumulated) | create-prd, write-architecture-spec, write-be-spec-classify |
-| `{{AUTH_SKILL}}` | `AUTH_PROVIDER` | create-prd, write-be-spec-classify |
-| `{{BACKEND_FRAMEWORK_SKILL}}` | `BACKEND_FRAMEWORK` / `API_LAYER` | write-be-spec-classify |
-| `{{API_DESIGN_SKILL}}` | `API_LAYER` (default: `api-design-principles`) | create-prd, create-prd-architecture, write-architecture-spec-design, write-be-spec-classify |
-| `{{FRONTEND_FRAMEWORK_SKILL}}` | `FRONTEND_FRAMEWORK` | write-fe-spec-classify |
-| `{{FRONTEND_DESIGN_SKILL}}` | `CSS_FRAMEWORK` / `UI_LIBRARY` | write-fe-spec-classify |
-| `{{ACCESSIBILITY_SKILL}}` | surface: `accessibility-compliance` | write-fe-spec-classify, write-fe-spec-write, write-architecture-spec-design, validate-phase |
-| `{{LANGUAGE_SKILL}}` | `LANGUAGE` | implement-slice-setup, implement-slice-tdd, write-be-spec-classify, write-fe-spec-classify, evolve-contract |
-| `{{CI_CD_SKILL}}` | `CI_CD` | create-prd-compile, decompose-architecture-structure, plan-phase, verify-infrastructure, validate-phase |
-| `{{HOSTING_SKILL}}` | `HOSTING` | create-prd-architecture, decompose-architecture-structure, plan-phase, verify-infrastructure, validate-phase |
-| `{{ORM_SKILL}}` | `ORM` | create-prd-architecture, write-be-spec-classify, implement-slice-setup, verify-infrastructure, validate-phase |
-| `{{UNIT_TESTING_SKILL}}` | `UNIT_TESTING` | create-prd-compile, implement-slice-setup, implement-slice-tdd, write-be-spec-classify, evolve-contract |
-| `{{E2E_TESTING_SKILL}}` | `E2E_TESTING` | create-prd-compile, implement-slice-tdd, validate-phase |
-| `{{STATE_MANAGEMENT_SKILL}}` | `STATE_MANAGEMENT` | write-fe-spec-classify, implement-slice-setup |
-| `{{SECURITY_SKILLS}}` | `SECURITY` + surface triggers (accumulated) | create-prd-security, write-architecture-spec-design, validate-phase |
+# Map Column Reference
+
+Maps surface stack map columns and cross-cutting categories to the workflows that consume them.
+
+> **How workflows use the map**: See `.agent/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: `docs/plans/desktop/be/` → surface `desktop`; flat `docs/plans/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 |

package/template/.agent/skills/prd-templates/references/skill-loading-protocol.md

@@ -0,0 +1,32 @@
+# Skill Loading Protocol
+
+Standard procedure for loading skills from the surface stack map before beginning spec or implementation work.
+
+## How to Load Skills from the Surface Stack Map
+
+1. **Determine the surface**: Identify which surface this work belongs to from the directory path or phase plan (e.g., `docs/plans/web/be/` → surface `web`; flat `docs/plans/be/` → surface `shared`).
+
+2. **Read the surface stack map**: Open `.agent/instructions/tech-stack.md` and locate this surface's row.
+
+3. **For each skill category** relevant to your workflow (Languages, Databases, BE Frameworks, FE Frameworks, FE Design, ORMs, Auth, Unit Tests, E2E Tests, State Mgmt, Accessibility, CI/CD, Hosting, Security):
+   - Read the skill name(s) listed in that cell
+   - For each skill directory name, read `.agent/skills/[skill]/SKILL.md`
+   - Follow its conventions (language, testing, framework, design, etc.)
+
+4. **Cross-cutting skills**: Some categories (Auth, Security, CI/CD, Hosting, Accessibility) are in the cross-cutting section — not per-surface. Read those from the cross-cutting rows.
+
+5. **Missing skill fallback**: If any skill in the bundle is not installed in `.agent/skills/` and is not in `.agent/skill-library/MANIFEST.md`, read `.agent/skills/find-skills/SKILL.md` and follow its discovery methodology to search for a community equivalent before proceeding without it.
+
+## Which Categories to Load Per Workflow
+
+| Workflow | Required Categories |
+|----------|-------------------|
+| `write-be-spec-classify` | Languages, Databases, Auth, BE Frameworks, ORMs, Unit Tests |
+| `write-fe-spec-classify` | Languages, FE Frameworks, FE Design, Accessibility, State Mgmt |
+| `write-architecture-spec-design` | Databases, Security, API Design |
+| `implement-slice-tdd` | Languages, Unit Tests, E2E Tests |
+| `validate-phase` | Unit Tests, E2E Tests, CI/CD, Hosting, Accessibility, Security |
+
+## Surface Stack Map Verification
+
+Before loading, verify the required cells have filled values. If any required cell is empty → **HARD STOP**: tell the user to run `/create-prd` first to make tech stack decisions.

package/template/.agent/skills/prd-templates/references/slice-completion-gates.md

@@ -0,0 +1,29 @@
+# Slice Completion Gates
+
+Checklists that must pass before a slice can be marked complete. Every unchecked item is a hard stop.
+
+## UI Completeness Check (FE slices only)
+
+- [ ] Every acceptance criterion mentioning "user sees", "user can", "displays", or "shows" has a rendered implementation — not just a passing test
+- [ ] Every new route in this slice is wired into the app's navigation (not just exported as a component)
+- [ ] Loading, error, and empty states are rendered in the UI — not just covered by tests
+- [ ] The feature is reachable from the app's entry point via normal user navigation
+
+Non-FE slices skip this block.
+
+## Spec Traceability Gate (all slices)
+
+- [ ] Re-read the BE spec section(s) for every endpoint in this slice — every response field, error code, and validation rule has a corresponding test tagged with the spec reference
+- [ ] Re-read the IA shard's `## Edge Cases` section for this slice's domain — every edge case relevant to this slice has a `// IA-EDGE:` tagged test
+- [ ] No `// DECISION:` annotations exist for behaviors that are actually specified in the BE spec or IA shard (i.e., no spec-defined behavior was treated as an undocumented implementation decision)
+- [ ] The {{CONTRACT_LIBRARY}} contract written in Step 2 matches the delivered implementation field-for-field — no fields added, removed, or renamed during implementation without a corresponding contract update
+
+## Resource Cleanup Gate (all slices)
+
+- [ ] Every database client or connection created in this slice has a corresponding cleanup call (`disconnect`, `close`, `end`, `dispose`) in a `finally` block or lifecycle hook
+- [ ] Every event listener or subscription registered in UI components has a corresponding cleanup in the component's unmount/destroy lifecycle
+- [ ] Every `setInterval` or `setTimeout` with a stored reference has a corresponding `clearInterval`/`clearTimeout` on cleanup
+- [ ] No file handles or streams are opened without corresponding `close`/`destroy` calls
+- [ ] If using connection pools — pool size is configured (not left at framework default) and documented via code comment: `// POOL: max=N, reason=...`
+
+> ❌ STOP — Do not call `notify_user` if any of the above are unchecked. Fix the gap and re-run the Test Cmd from the surface stack map.

package/template/.agent/skills/prd-templates/references/spec-coverage-sweep.md

@@ -18,8 +18,8 @@ For each slice in the phase plan (`docs/plans/phases/phase-N.md`):
 
 4. Identify the BE spec section(s) for each endpoint in this slice
 5. For each endpoint:
-   - Verify every Zod-validated field in the BE spec has a corresponding test
-   - Verify every error code defined in the BE spec has a corresponding test
+   - Verify every {{CONTRACT_LIBRARY}}-validated field in the BE spec has a corresponding test
+   - Verify every error code defined in the BE spec has a corresponding test that asserts the **full error response shape** (status + error code + message), not just the HTTP status
    - Verify every auth rule (role, ownership check) defined in the BE spec has a corresponding permission test
 
 ### IA Shard Coverage
@@ -33,7 +33,7 @@ For each slice in the phase plan (`docs/plans/phases/phase-N.md`):
 
 If any flow, field, error code, auth rule, IA acceptance criterion, or accessibility requirement has no corresponding test:
 
-> ❌ STOP — Do not mark this phase as complete. List the uncovered items. Either write the missing tests and re-run `{{TEST_COMMAND}}`, or if the item was genuinely deferred (valid boundary stub + tracking issue), document the deferral explicitly in the phase validation report.
+> ❌ STOP — Do not mark this phase as complete. List the uncovered items. Either write the missing tests and re-run the Test Cmd from `.agent/instructions/commands.md`, or if the item was genuinely deferred (valid boundary stub + tracking issue), document the deferral explicitly in the phase validation report.
 
 ## Pass Criteria
 

package/template/.agent/skills/prd-templates/references/tdd-testing-policy.md

@@ -0,0 +1,39 @@
+# TDD Testing Policy
+
+## Assertion Depth Rule
+
+Every test must assert **at minimum**:
+- Response status code AND response body structure (not just status)
+- At least one specific field value from the response body
+- For error paths: the full error shape (code + message), not just the status code
+- Contract tests must assert both valid input accepted AND invalid input rejected with the correct error shape
+
+Tests that only assert `status == 200` without checking the response body are **insufficient** and will be flagged during QA anti-cheat audit.
+
+## Anti-Mock-Abuse Rules
+
+| Test Type | Mocking Policy |
+|-----------|---------------|
+| **Unit tests** | Mocking external dependencies allowed and expected |
+| **Integration tests** | At least one test per endpoint must hit a real test database — no mocked DB responses |
+| **E2E tests** | No mocks allowed — full stack or it doesn't count |
+
+**Banned patterns**:
+- Mocking the module under test (testing a mock of what you're building)
+- Mock chains (mocking a mock that mocks another dependency)
+- Tests where the mock returns exactly the expected value (circular, proves nothing)
+
+**Test order**: Unit → Integration → E2E (if applicable)
+
+## QA Anti-Cheat Audit
+
+Before marking tests as passing, verify:
+
+- [ ] No tests with zero assertions
+- [ ] No tautological tests (e.g., `expect(true).toBe(true)`, `expect(mock).toEqual(mock)`)
+- [ ] No `test.skip` without a `BOUNDARY:` reference and tracking issue
+- [ ] Every test that asserts a response also asserts the response body, not just the status code
+- [ ] No tests that mock the thing they're supposed to test (e.g., mocking the handler to test the handler)
+- [ ] Error path tests actually trigger the error condition — they don't just mock the error response
+
+In sequential mode, the agent self-audits against this checklist. In parallel mode, the QA-GREEN agent runs this explicitly.

package/template/.agent/skills/prd-templates/references/vision-template.md

@@ -4,7 +4,7 @@ Use this template when compiling `docs/plans/vision.md` as the human-readable ex
 
 > **Important**: `vision.md` is a summary document for human consumption. The pipeline reads
 > `docs/plans/ideation/ideation-index.md` directly — not this file. All the depth, domain
-> files, cross-cut ledger, and structured data live in the `ideation/` folder.
+> files, CX files, and structured data live in the `ideation/` folder's fractal tree.
 
 ```markdown
 # [Project Name] — Vision
@@ -12,7 +12,7 @@ Use this template when compiling `docs/plans/vision.md` as the human-readable ex
 > One-sentence pitch: [from Step 4]
 
 > **This is a human-readable project summary.** For pipeline-grade detail, see
-> [ideation-index.md](ideation/ideation-index.md) and the domain files it references.
+> [ideation-index.md](ideation/ideation-index.md) and the fractal domain tree it references.
 
 ## Problem Statement
 [Condensed from `meta/problem-statement.md`]
@@ -25,26 +25,26 @@ Not the full 6-field exploration — that detail stays in the personas file.]
 [2-3 paragraphs describing what the product does and why it matters.]
 
 ## Domain Map
-[One paragraph per domain, condensed from the domain files in `ideation/domains/`.
-Each domain links to its full file.]
+[One paragraph per domain, condensed from the ideation domain folders (paths in `ideation-index.md` Structure Map).
+Each domain links to its folder's index file.]
 
 ## Feature Inventory (MoSCoW)
 ### Must Have (Phase 1)
-[Feature names + one-line description. Links to domain files for drill-down detail.]
+[Feature names + one-line description. Links to domain folder index files for drill-down detail.]
 ### Should Have (Phase 2)
 [Feature names + one-line description.]
 ### Could Have (Phase 3+)
 ### Won't Have (explicitly excluded)
 
 ## Key Cross-Cutting Interactions
-[Top confirmed interactions from `cross-cuts/cross-cut-ledger.md`.
-Full synthesis detail stays in the ledger.]
+[Top confirmed interactions from `ideation-cx.md` (global) and domain-level `*-cx.md` files.
+Full synthesis detail stays in the CX files.]
 
 ## Constraints Summary
 [Condensed from `meta/constraints.md` — budget, timeline, team, compliance, performance, surfaces.]
 
 ## Success Metrics
-[Key metrics with concrete targets. Full details in relevant domain files.]
+[Key metrics with concrete targets. Full details in relevant domain folder feature files.]
 
 ## Competitive Landscape
 [Condensed from `meta/competitive-landscape.md` — competitors, differentiation, moat.]