cfsa-antigravity 3.1.1 → 6.0.0

package/README.md

@@ -29,13 +29,12 @@ npx cfsa-antigravity init --agent claude,factory
 | `cfsa-antigravity init --dry-run` | Preview what would be installed |
 | `cfsa-antigravity init --path ./dir` | Install into specific directory |
 | `cfsa-antigravity init --memory` | Scaffold unified `.memory/` + MCP integration |
-| `cfsa-antigravity init --migrate-memory` | Scaffold unified memory and import legacy runtime memory |
 
 ### Available runtimes
 
 Runtimes are auto-detected from the template. Currently shipped:
 
-- **Antigravity** (`.agent/`) -- Antigravity, Cursor, Gemini CLI
+- **Antigravity** (`.agents/`) -- Antigravity, Cursor, Gemini CLI
 - **Codex** (`.codex/`) -- Standalone Codex runtime
 - **Claude Code** (`.claude/`) -- Standalone Claude Code runtime
 - **Factory Droid** (`.factory/`) -- Standalone Factory Droid runtime
@@ -54,8 +53,7 @@ Every install now scaffolds a shared `.memory/` root at the project level. It is
 ├── schema/      # machine-readable index/chunk artifacts
 ├── mcp-server/  # shared project-local MCP daemon + per-runtime client entrypoints
 ├── runtime/     # daemon pid/state files
-├── hooks/       # Claude hook entrypoints
-└── migrate/     # legacy memory import helpers
+└── hooks/       # Claude hook entrypoints
 ```
 
 The installer ships the shared memory runtime into `.memory/`, including the project-local MCP server under `.memory/mcp-server/`. Tool-specific MCP client config is intentionally **not** managed by the kit — users wire their own `.mcp.json` / editor settings for the tools they actually use. The daemon writes workspace-local runtime state into `.memory/runtime/`, and clients resolve that state before proxying requests so one workspace does not silently talk to another workspace's daemon. The semantic index writes retrieval artifacts into `.memory/schema/semantic-index.json` plus `.memory/schema/semantic-manifest.json`.
@@ -110,7 +108,7 @@ If you are using an editor that indexes agent files for slash commands, do not h
 Keep the installed runtime directory out of shared `.gitignore` rules when your tool needs to index it. Prefer `.git/info/exclude` for local-only exclusions.
 
 Examples:
-1. Antigravity install → keep `.agent/` out of `.gitignore`
+1. Antigravity install → keep `.agents/` out of `.gitignore`
 2. Codex install → keep `.codex/` out of `.gitignore`
 3. Claude install → keep `.claude/` out of `.gitignore`
 4. Factory install → keep `.factory/` out of `.gitignore`
@@ -141,7 +139,7 @@ This performs a **semantic merge** — it applies new workflows, skills, and rul
 ## What Init Adds
 
 A fresh `init` now installs:
-- your selected runtime directories (`.agent/`, `.codex/`, `.claude/`, `.factory/`)
+- your selected runtime directories (`.agents/`, `.codex/`, `.claude/`, `.factory/`)
 - `docs/`
 - shared `.memory/`
 - the shared memory MCP server/runtime under `.memory/mcp-server/`
@@ -150,10 +148,6 @@ A fresh `init` now installs:
 
 Tool-specific MCP client config (such as `.mcp.json`) is user-managed and documented above.
 
-Use `--migrate-memory` when upgrading an older installation that still has runtime-local memory you want imported into `.memory/`.
-
-If migration finds a knowledge-file destination with different existing contents, it preserves both versions by writing a `.conflict-YYYY-MM-DD.md` sibling file for manual reconciliation.
-
 ## Documentation
 
 | Document | Contents |

package/bin/cli.mjs

@@ -200,7 +200,6 @@ ${c.bold}Init Options:${c.reset}
   --dry-run           Preview what would be copied without making changes
   --quiet             Suppress output (for CI/CD — installs all runtimes)
   --memory            Scaffold unified .memory/ and MCP integration
-  --migrate-memory    Scaffold .memory/ and migrate legacy runtime memory
 
 ${c.bold}Examples:${c.reset}
   ${c.dim}# Interactive — pick which runtimes to install${c.reset}
@@ -225,7 +224,7 @@ ${c.bold}Examples:${c.reset}
 
 // --- Parse Arguments ---
 function parseArgs(args) {
-    const parsed = { command: null, agents: null, force: false, dryRun: false, path: null, quiet: false, memory: false, migrateMemory: false, json: false };
+    const parsed = { command: null, agents: null, force: false, dryRun: false, path: null, quiet: false, memory: false, json: false };
 
     let i = 0;
     while (i < args.length) {
@@ -272,10 +271,6 @@ function parseArgs(args) {
             case "--memory":
                 parsed.memory = true;
                 break;
-            case "--migrate-memory":
-                parsed.memory = true;
-                parsed.migrateMemory = true;
-                break;
             case "--json":
                 parsed.json = true;
                 break;
@@ -424,18 +419,6 @@ function installMemoryScaffold(targetDir, opts) {
     info(`MCP client configuration is user-managed; see the README for tool-specific setup and the initial graph compile step.`);
 }
 
-async function migrateMemory(targetDir) {
-    const migratePath = join(targetDir, ".memory", "migrate", "migrate-legacy.mjs");
-    if (!existsSync(migratePath)) {
-        error("Unified memory migration script not found after scaffold.");
-        exit(1);
-    }
-
-    const migrationModule = await import(pathToFileURL(migratePath).href);
-    const result = migrationModule.migrateLegacyMemory({ projectRoot: targetDir });
-    info(`Migrated legacy memory (${result.migratedCount} item(s))`);
-}
-
 // --- Install runtimes ---
 function installRuntimes(runtimes, targetDir, opts) {
     let totalCopied = 0;
@@ -569,9 +552,6 @@ async function cmdInit(opts) {
     const { totalCopied, totalSkipped } = installRuntimes(selected, targetDir, opts);
 
     installMemoryScaffold(targetDir, opts);
-    if (opts.migrateMemory && !opts.dryRun) {
-        await migrateMemory(targetDir);
-    }
 
     if (!opts.dryRun) {
         const compilePath = join(targetDir, ".memory", "pipeline", "compile.mjs");

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "cfsa-antigravity",
-  "version": "3.1.1",
+  "version": "6.0.0",
   "description": "CFSA Pipeline — Constraint-First Specification Architecture for AI agents. Production-grade from line one.",
   "scripts": {
     "changeset": "changeset",
     "version": "changeset version",
     "prebuild": "./scripts/build-template.sh",
     "build": "./scripts/build-template.sh",
-    "check": "./scripts/check-template-integrity.sh && node ./scripts/check-memory-mcp.mjs && node ./scripts/check-memory-migration.mjs && node ./scripts/check-vault-contract.mjs && node ./scripts/check-e2e-harness.mjs",
+    "check": "./scripts/check-template-integrity.sh && node ./scripts/check-memory-mcp.mjs && node ./scripts/check-vault-contract.mjs && node ./scripts/check-e2e-harness.mjs",
     "prepare": "husky || true"
   },
   "bin": {

package/template/{.agent → .agents}/instructions/structure.md

@@ -20,10 +20,10 @@
 ## Protected Files (Do Not Modify Without Approval)
 - `AGENTS.md` — Project agent config
 - `.memory/wiki/specs/ENGINEERING-STANDARDS.md` — Quality bar
-- `.agent/instructions/*` — Agent rules
+- `.agents/instructions/*` — Agent rules
 - `package.json` — Dependencies (add carefully)
 - `tsconfig.json` — TypeScript config
 
 ## Notes
-- All agent config lives in `.agent/` (canonical for all agents)
+- All agent config lives in `.agents/` (canonical for all agents)
 - Frontend and API may be separately deployed depending on architecture

package/template/{.agent → .agents}/instructions/tech-stack.md

@@ -26,7 +26,7 @@ The surface stack map is the **single source of truth** for all per-surface stac
 
 ### Per-Surface Skills
 
-Each cell is a comma-separated list of skill directory names from `.agent/skills/`. Use `—` for "not applicable."
+Each cell is a comma-separated list of skill directory names from `.agents/skills/`. Use `—` for "not applicable."
 
 <!-- Bootstrap fills this table. One row per confirmed surface + a `shared` row for cross-surface backend. -->
 
@@ -62,7 +62,7 @@ A valid surface stack map must satisfy:
 3. **Test Cmd column is never empty** — every surface must be testable
 4. **No `⚠️` cells** — all skill resolution must be complete before implementation begins
 
-Verification gates in `plan-phase` and `implement-slice` check these conditions. See `.agent/skills/session-continuity/protocols/10-placeholder-verification-gate.md` for the full verification procedure.
+Verification gates in `plan-phase` and `implement-slice` check these conditions. See `.agents/skills/session-continuity/protocols/10-placeholder-verification-gate.md` for the full verification procedure.
 
 ---
 

package/template/{.agent → .agents}/instructions/workflow.md

@@ -4,12 +4,12 @@ Before taking any action on a task:
 
 ## 1. Understand Context
 - Read the agent config file at project root (`AGENTS.md` for Antigravity, `GEMINI.md` for Gemini CLI, or equivalent for your agent)
-- Read relevant `.agent/instructions/` files for the task type
+- Read relevant `.agents/instructions/` files for the task type
 - Check [Engineering Standards](../../.memory/wiki/specs/ENGINEERING-STANDARDS.md) for quality bar — if this file doesn't exist yet, the pipeline hasn't reached /create-prd; run /ideate then /create-prd first
-- **Session Resumption**: If `.memory/pipeline/progress/index.md` exists, read `.agent/skills/session-continuity/protocols/01-session-resumption.md` and follow the **Session Resumption Protocol** to load cross-session context and identify the resumption point
+- **Session Resumption**: If `.memory/pipeline/progress/index.md` exists, read `.agents/skills/session-continuity/protocols/01-session-resumption.md` and follow the **Session Resumption Protocol** to load cross-session context and identify the resumption point
 
 ## 2. Check Skills
-- Scan `.agent/skills/` for applicable skills
+- Scan `.agents/skills/` for applicable skills
 - Load relevant skill SKILL.md before proceeding
 - Key skills: `brainstorming` (before creative work), `tdd-workflow` (before features), `clean-code` (during review)
 
@@ -28,7 +28,7 @@ Before taking any action on a task:
 ## 4. Validate (MANDATORY)
 After **every** code change, run:
 ```bash
-See `.agent/instructions/commands.md` for the validation command.
+See `.agents/instructions/commands.md` for the validation command.
 ```
 
 Do NOT mark a task complete until all validations pass.
@@ -37,8 +37,8 @@ Do NOT mark a task complete until all validations pass.
 
 After completing a workflow or substantial task:
 
-- **Pattern Extraction**: Read `.agent/skills/session-continuity/protocols/04-pattern-extraction.md` and follow the **Pattern Extraction Protocol**. Reflect on what worked, what didn't, and log reusable patterns to `.memory/wiki/patterns.md`. Skip only if the task was trivial (routine, nothing new learned).
-- **Session Close**: Read `.agent/skills/session-continuity/protocols/05-session-close.md` and follow the **Session Close Protocol**. Write a session log to `.memory/pipeline/progress/sessions/` so the next session can resume cleanly.
+- **Pattern Extraction**: Read `.agents/skills/session-continuity/protocols/04-pattern-extraction.md` and follow the **Pattern Extraction Protocol**. Reflect on what worked, what didn't, and log reusable patterns to `.memory/wiki/patterns.md`. Skip only if the task was trivial (routine, nothing new learned).
+- **Session Close**: Read `.agents/skills/session-continuity/protocols/05-session-close.md` and follow the **Session Close Protocol**. Write a session log to `.memory/pipeline/progress/sessions/` so the next session can resume cleanly.
 - **Unified Memory First**: Treat `.memory/` as the canonical project memory root. When shared memory is needed, prefer the `cfsa-memory` MCP bridge over runtime-local silos so all runtimes see the same memory.
 
 > These steps are **not optional**. They are what differentiate a pipeline that gets

package/template/{.agent → .agents}/rules/completion-checklist.md

@@ -43,7 +43,7 @@ A unit of work is only DONE when:
    - `blockers.md` — Any blockers hit logged with status and impact
    - See rule: `memory-capture` for triggers and format
 6. **The Session Log**: A session close log exists in `.memory/pipeline/progress/sessions/`.
-   - Follow `.agent/skills/session-continuity/protocols/05-session-close.md` — write what was accomplished, deferred, and where the next session should start
+   - Follow `.agents/skills/session-continuity/protocols/05-session-close.md` — write what was accomplished, deferred, and where the next session should start
 7. **The Next Step**: The user is told what comes next in the pipeline.
    - Read the pipeline progress file (`.memory/pipeline/progress/spec-pipeline.md` or equivalent)
    - Propose the next valid pipeline command based on current state

package/template/{.agent → .agents}/rules/extensibility.md

@@ -30,7 +30,7 @@ trigger: always_on
 
 ## Naming Conventions
 
-Follow the project's established conventions in `.agent/instructions/patterns.md`. When no convention exists yet, use the stack's community standard.
+Follow the project's established conventions in `.agents/instructions/patterns.md`. When no convention exists yet, use the stack's community standard.
 
 ## Anti-Spaghetti Rules
 

package/template/{.agent → .agents}/rules/vertical-slices.md

@@ -41,7 +41,7 @@ When a multi-surface feature launches on one surface first:
 
 ## The Four Implementation Layers
 
-> **Note on terminology**: The layers below describe implementation completeness criteria — what every feature slice requires regardless of surface type. These are not the same as surface types (web/mobile/cli/etc.). For the mapping between surface types and how each implementation layer manifests on that surface, see `.agent/skills/prd-templates/references/surface-model.md`.
+> **Note on terminology**: The layers below describe implementation completeness criteria — what every feature slice requires regardless of surface type. These are not the same as surface types (web/mobile/cli/etc.). For the mapping between surface types and how each implementation layer manifests on that surface, see `.agents/skills/prd-templates/references/surface-model.md`.
 
 | Surface | What It Is | Example |
 |---------|-----------|---------|

package/template/{.agent → .agents}/skill-library/MANIFEST.md

@@ -8,7 +8,7 @@
 1. A pipeline skill (e.g., `/create-prd`, `/iterate-plan`, `/add-feature`) makes a tech decision
 2. It calls `/bootstrap-agents` with the new stack key=value
 3. Bootstrap reads this manifest and finds matching skills
-4. Matching skills are copied from `.agent/skill-library/` → `.agent/skills/`
+4. Matching skills are copied from `.agents/skill-library/` → `.agents/skills/`
 5. Any `{{PLACEHOLDER}}`s inside the copied skills are filled with current values
 
 ## Stack Triggers
@@ -98,10 +98,10 @@ When a stack key matches a value pattern (case-insensitive), install the listed
 | `UI_LIBRARY` | `*svelte-flow*` OR `*svelteflow*` OR `*xyflow*` | `stack/ui/svelte-flow` | `svelte-flow` |
 | `FRONTEND_FRAMEWORK` | `*react*` | `stack/ui/react-best-practices` | `react-best-practices` |
 | `FRONTEND_FRAMEWORK` | `*react*` | `stack/ui/react-composition-patterns` | `react-composition-patterns` |
-| `DESIGN_DIRECTION` | `*` (any confirmed value) | Fills `{{PLACEHOLDER}}`s in `.agent/skills/brand-guidelines/SKILL.md` in-place | `brand-guidelines` (in-place fill, not copy) |
+| `DESIGN_DIRECTION` | `*` (any confirmed value) | Fills `{{PLACEHOLDER}}`s in `.agents/skills/brand-guidelines/SKILL.md` in-place | `brand-guidelines` (in-place fill, not copy) |
 | `DESIGN_DIRECTION` | `*cinematic*` OR `*immersive*` | `stack/3d/threejs-pro` | `threejs-pro` |
 
-Note: `DESIGN_DIRECTION` does not copy a skill from the library — it fills placeholders in the pre-placed `.agent/skills/brand-guidelines/SKILL.md` template. Exception: when the direction is `Cinematic/Immersive`, `threejs-pro` is also installed as a standard skill copy, since WebGL and Three.js capabilities will be required.
+Note: `DESIGN_DIRECTION` does not copy a skill from the library — it fills placeholders in the pre-placed `.agents/skills/brand-guidelines/SKILL.md` template. Exception: when the direction is `Cinematic/Immersive`, `threejs-pro` is also installed as a standard skill copy, since WebGL and Three.js capabilities will be required.
 
 ### Authentication
 
@@ -168,7 +168,7 @@ Note: `DESIGN_DIRECTION` does not copy a skill from the library — it fills pla
 |-----------|--------------|-------------|-------------|
 | `OBSERVABILITY` | `*opentelemetry*` OR `*otel*` | `stack/observability/opentelemetry` | `opentelemetry` |
 | `OBSERVABILITY` | `*distributed-tracing*` OR `*jaeger*` OR `*zipkin*` | `stack/observability/distributed-tracing` | `distributed-tracing` |
-| `OBSERVABILITY` | `*structured-logging*` OR `*pino*` OR `*winston*` | Pre-installed: `.agent/skills/logging-best-practices` | `logging-best-practices` (pre-installed) |
+| `OBSERVABILITY` | `*structured-logging*` OR `*pino*` OR `*winston*` | Pre-installed: `.agents/skills/logging-best-practices` | `logging-best-practices` (pre-installed) |
 | `OBSERVABILITY` | `*python*` | `stack/observability/python-observability` | `python-observability` |
 | `OBSERVABILITY` | `*datadog*` | `stack/observability/datadog` | `datadog` |
 | `OBSERVABILITY` | `*prometheus*` OR `*grafana*` | `stack/observability/prometheus-grafana` | `prometheus-grafana` |
@@ -362,7 +362,7 @@ When the project includes a surface type, install the listed skills.
 | `api` | `surface/api/api-caching` | `api-caching` |
 | `api` | `surface/api/api-documentation-openapi` | `api-documentation-openapi` |
 | `api` | `surface/api/webhook-design` | `webhook-design` |
-| `api` | Pre-installed: `.agent/skills/api-design-principles` | `api-design-principles` (pre-installed) |
+| `api` | Pre-installed: `.agents/skills/api-design-principles` | `api-design-principles` (pre-installed) |
 | `api` | `surface/api/api-security-checklist` | `api-security-checklist` |
 | `api` | `stack/security/input-sanitization` | `input-sanitization` |
 
@@ -420,7 +420,7 @@ These skills are NOT auto-installed. Install via `/find-skills` or manually copy
 | `meta/mcp-builder` | Building MCP servers |
 | `meta/tmux-processes` | Long-lived process management via tmux |
 | `meta/using-tmux-for-interactive-commands` | Interactive CLI tools via tmux |
-| Pre-installed: `.agent/skills/brand-guidelines` | Brand color and typography application (pre-installed) |
+| Pre-installed: `.agents/skills/brand-guidelines` | Brand color and typography application (pre-installed) |
 | `meta/product-marketing-context` | Marketing context document generator — run first before any SEO or CRO skill |
 
 ---
@@ -441,7 +441,7 @@ These skills are specific to Claude Code's plugin and agent system. Not applicab
 
 To add a new skill to the library:
 
-1. Create a directory under the appropriate category: `.agent/skill-library/[category]/[subcategory]/[skill-name]/SKILL.md`
+1. Create a directory under the appropriate category: `.agents/skill-library/[category]/[subcategory]/[skill-name]/SKILL.md`
 2. Add a row to the appropriate trigger table above
 3. Use `{{PLACEHOLDER}}`s for any values that should be filled by bootstrap
 4. Test by running `/bootstrap-agents` with a matching stack value

package/template/{.agent → .agents}/skill-library/README.md

@@ -9,8 +9,8 @@
 
 1. A pipeline workflow (e.g., `/create-prd`) makes a tech stack decision
 2. It calls `/bootstrap-agents` with the new stack key=value
-3. Bootstrap reads `.agent/skill-library/MANIFEST.md` and finds matching skills
-4. Matching skills are copied from `.agent/skill-library/` → `.agent/skills/`
+3. Bootstrap reads `.agents/skill-library/MANIFEST.md` and finds matching skills
+4. Matching skills are copied from `.agents/skill-library/` → `.agents/skills/`
 5. Any `{{PLACEHOLDER}}`s inside the copied skills are filled with current values
 
 ## Installing Skills
@@ -26,7 +26,7 @@ Use `/find-skills` to search the library and install matching skills interactive
 
 ### Direct
 
-Copy a skill directory from `.agent/skill-library/[path]/` to `.agent/skills/[name]/`
+Copy a skill directory from `.agents/skill-library/[path]/` to `.agents/skills/[name]/`
 and manually replace any `{{PLACEHOLDER}}` values.
 
 ## Library Structure

package/template/{.agent → .agents}/skill-library/meta/claude-code/README.md

@@ -6,4 +6,4 @@ These skills are specific to Claude Code's plugin and agent system. They are not
 - **plugin-structure** — Claude Code plugin architecture (.claude-plugin/plugin.json)
 - **agent-development** — Claude Code agent frontmatter (model, color, triggering examples)
 
-These are manual-install only. Copy the relevant skill to `.agent/skills/` when working in Claude Code.
+These are manual-install only. Copy the relevant skill to `.agents/skills/` when working in Claude Code.

package/template/{.agent → .agents}/skill-library/surface/web/design-reference-data/SKILL.md

@@ -48,7 +48,7 @@ After the user confirms their design direction, run these searches to get concre
 #### 1. Find matching design styles
 
 ```bash
-python .agent/skills/design-reference-data/scripts/search.py \
+python .agents/skills/design-reference-data/scripts/search.py \
   "<direction + project context>" \
   --domain style --max-results 5
 ```
@@ -58,7 +58,7 @@ Example: `"modern dark mode SaaS dashboard"` or `"warm friendly wellness app"`
 #### 2. Find specific color palettes
 
 ```bash
-python .agent/skills/design-reference-data/scripts/search.py \
+python .agents/skills/design-reference-data/scripts/search.py \
   "<mood + industry>" \
   --domain color --max-results 3
 ```
@@ -68,7 +68,7 @@ Example: `"professional trust-building fintech"` or `"vibrant playful consumer"`
 #### 3. Find typography pairings
 
 ```bash
-python .agent/skills/design-reference-data/scripts/search.py \
+python .agents/skills/design-reference-data/scripts/search.py \
   "<style + readability needs>" \
   --domain typography --max-results 3
 ```
@@ -78,7 +78,7 @@ Example: `"clean serif editorial"` or `"modern sans-serif technical"`
 #### 4. Generate full design system recommendation
 
 ```bash
-python .agent/skills/design-reference-data/scripts/search.py \
+python .agents/skills/design-reference-data/scripts/search.py \
   "<project description>" \
   --design-system -p "ProjectName"
 ```

package/template/{.agent → .agents}/skill-library/surface/web/frontend-design/SKILL.md

@@ -14,7 +14,7 @@ This skill guides creation of **production-grade frontend interfaces that feel A
 
 ## Prerequisite: Read Brand Guidelines First
 
-Before making any aesthetic decisions, read `.agent/skills/brand-guidelines/SKILL.md`.
+Before making any aesthetic decisions, read `.agents/skills/brand-guidelines/SKILL.md`.
 
 - If the design direction is confirmed (no `{{PLACEHOLDER}}` values), **execute that direction**. Do not invent a new direction — the user confirmed this one during `/create-prd`.
 - If `{{DESIGN_DIRECTION}}` is still a literal placeholder, stop and tell the user: "Design direction hasn't been confirmed yet — run `/create-prd` first before building UI."

package/template/{.agent → .agents}/skill-library/surface/web/frontend-verification/SKILL.md

@@ -36,7 +36,7 @@ A 750-line Python scanner with 75+ automated checks across 11 categories:
 After implementing a frontend slice, run the audit on **changed files only**:
 
 ```bash
-python .agent/skills/frontend-verification/scripts/ux_audit.py src/components/NewFeature/ --json
+python .agents/skills/frontend-verification/scripts/ux_audit.py src/components/NewFeature/ --json
 ```
 
 **Exit codes:**
@@ -47,7 +47,7 @@ python .agent/skills/frontend-verification/scripts/ux_audit.py src/components/Ne
 For slice-level scans, you may skip categories unrelated to the current work:
 
 ```bash
-python .agent/skills/frontend-verification/scripts/ux_audit.py src/components/Chart/ \
+python .agents/skills/frontend-verification/scripts/ux_audit.py src/components/Chart/ \
   --skip-psychology --skip-typography
 ```
 
@@ -56,7 +56,7 @@ python .agent/skills/frontend-verification/scripts/ux_audit.py src/components/Ch
 At phase validation, run the audit on the **entire frontend source**:
 
 ```bash
-python .agent/skills/frontend-verification/scripts/ux_audit.py src/ --json
+python .agents/skills/frontend-verification/scripts/ux_audit.py src/ --json
 ```
 
 **Validation threshold:**

package/template/{.agent/workflows/audit-ambiguity.md → .agents/skills/audit-ambiguity/SKILL.md}

@@ -21,8 +21,8 @@ Audit pipeline output completeness and identify gaps that would force guesswork
 ## 0. Load audit skills
 
 Read these skills for review guidance:
-1. `.agent/skills/code-review-pro/SKILL.md` — Review methodology
-2. `.agent/skills/technical-writer/SKILL.md` — Spec clarity standards
+1. `.agents/skills/code-review-pro/SKILL.md` — Review methodology
+2. `.agents/skills/technical-writer/SKILL.md` — Spec clarity standards
 
 ---
 
@@ -30,18 +30,18 @@ Read these skills for review guidance:
 
 | # | Shard | What It Does |
 |---|-------|-------------|
-| 1 | [`audit-ambiguity-rubrics`](.agent/workflows/audit-ambiguity-rubrics.md) | Determines scope, loads documents, provides all 5 rubrics (Vision, Architecture, IA, BE, FE) with scoring criteria |
-| 2 | [`audit-ambiguity-execute`](.agent/workflows/audit-ambiguity-execute.md) | Executes the audit one document at a time, compiles report, remediates gaps, proposes next steps |
+| 1 | [`audit-ambiguity-rubrics`](.agents/skills/audit-ambiguity-rubrics/SKILL.md) | Determines scope, loads documents, provides all 5 rubrics (Vision, Architecture, IA, BE, FE) with scoring criteria |
+| 2 | [`audit-ambiguity-execute`](.agents/skills/audit-ambiguity-execute/SKILL.md) | Executes the audit one document at a time, compiles report, remediates gaps, proposes next steps |
 
 ---
 
 ## Orchestration
 
-### Step A — Run `.agent/workflows/audit-ambiguity-rubrics.md`
+### Step A — Run `.agents/skills/audit-ambiguity-rubrics/SKILL.md`
 
 Asks the user which layer(s) to audit, loads the source documents, and provides the scoring rubrics for each applicable layer.
 
-### Step B — Run `.agent/workflows/audit-ambiguity-execute.md`
+### Step B — Run `.agents/skills/audit-ambiguity-execute/SKILL.md`
 
 Audits each document one at a time (read → score with evidence → classify gaps → verify → finalize), compiles the report to `.memory/wiki/specs/audits/`, remediates gaps using `resolve-ambiguity`, and proposes next steps.
 

package/template/{.agent/workflows/audit-ambiguity-execute.md → .agents/skills/audit-ambiguity-execute/SKILL.md}

@@ -48,7 +48,7 @@ Read `.memory/wiki/specs/audits/audit-scope.md`. Extract the `## Document Count`
 
 ## 3a. Implementer Simulation
 
-Read .agent/skills/verification-before-completion/SKILL.md and follow its methodology.
+Read .agents/skills/verification-before-completion/SKILL.md and follow its methodology.
 
 **CRITICAL**: You MUST NOT read all documents at once. Process one document at a time through 3a→3b→3c. Do NOT skip documents because they seem redundant, because rubric dimensions "map" to other files, or because you can "derive" their content from synthesized documents. EVERY document in the scope list gets the full 3a→3b→3c treatment. After each document, state: **"Documents processed: X/N."**
 
@@ -65,7 +65,7 @@ These gaps are **unconditional** — the rubric in 3b cannot override them.
 
 ## 3b. Rubric Scoring with Two-Implementer Test
 
-Score each dimension using the rubric files loaded in Step 0 (persisted paths from `.memory/wiki/specs/audits/audit-scope.md`). Read `.agent/skills/pipeline-rubrics/SKILL.md` for the scoring methodology. For every score:
+Score each dimension using the rubric files loaded in Step 0 (persisted paths from `.memory/wiki/specs/audits/audit-scope.md`). Read `.agents/skills/pipeline-rubrics/SKILL.md` for the scoring methodology. For every score:
 
 - **✅** → State explicitly: *"Two implementers would make the same decision because: [specific reason citing exact text from the document]."* If you cannot complete this sentence confidently, score ⚠️ instead. The bar is "unambiguous to any implementer reading cold", not "text exists somewhere."
 - **⚠️** → Quote what exists AND state precisely what is missing AND what decision an implementer would have to make without it.
@@ -122,7 +122,7 @@ Do not re-read documents to reconstruct scores — read the report file that was
 
 Do NOT stop and ask the user what to do. After compiling the report in Step 4, immediately execute this step for every ⚠️ and ❌ in the punch list.
 
-1. Read `.agent/skills/resolve-ambiguity/SKILL.md` and execute the resolution process inline — do not invoke it as a separate command.
+1. Read `.agents/skills/resolve-ambiguity/SKILL.md` and execute the resolution process inline — do not invoke it as a separate command.
 2. For each gap, classify using the skill's two-path model:
    - **Judgment calls** (Intent/Choice gaps — no source has the answer): present to user with smart options ordered by recommendation; wait for user decision before applying any fix.
    - **Mechanical fixes** (Technical/Factual gaps — answer exists in project docs, architecture files, upstream specs, or official sources): propose the fix with source citation; apply after user approval.

package/template/{.agent/workflows/audit-ambiguity-rubrics.md → .agents/skills/audit-ambiguity-rubrics/SKILL.md}

@@ -33,7 +33,7 @@ Ask the user:
 
 ## 2. Enumerate source documents
 
-Read `.agent/skills/pipeline-rubrics/references/scoring.md` for the document-to-layer mapping table.
+Read `.agents/skills/pipeline-rubrics/references/scoring.md` for the document-to-layer mapping table.
 
 **MANDATORY filesystem discovery**: Use file system tools (`find_by_name`, `list_dir`) to recursively discover ALL files matching the layer's patterns from `scoring.md`. Do NOT build the document list from memory or from reading an index file — the filesystem is the source of truth.
 
@@ -69,11 +69,11 @@ Write `.memory/wiki/specs/audits/audit-scope.md` with the determined scope and t
 
 ## Rubric Files
 [for each layer being audited, list the exact path of the rubric file]
-- vision: .agent/skills/pipeline-rubrics/references/vision-rubric.md
-- architecture: .agent/skills/pipeline-rubrics/references/architecture-rubric.md
-- ia: .agent/skills/pipeline-rubrics/references/ia-rubric.md
-- be: .agent/skills/pipeline-rubrics/references/be-rubric.md
-- fe: .agent/skills/pipeline-rubrics/references/fe-rubric.md
+- vision: .agents/skills/pipeline-rubrics/references/vision-rubric.md
+- architecture: .agents/skills/pipeline-rubrics/references/architecture-rubric.md
+- ia: .agents/skills/pipeline-rubrics/references/ia-rubric.md
+- be: .agents/skills/pipeline-rubrics/references/be-rubric.md
+- fe: .agents/skills/pipeline-rubrics/references/fe-rubric.md
 
 ## Status
 in-progress
@@ -85,16 +85,16 @@ This file is read by `/audit-ambiguity-execute` as its prerequisite.
 
 ## 3. Load and apply rubrics
 
-Read `.agent/skills/pipeline-rubrics/SKILL.md` for the scoring methodology. For each layer being audited, load the matching rubric from the skill's `references/` directory:
+Read `.agents/skills/pipeline-rubrics/SKILL.md` for the scoring methodology. For each layer being audited, load the matching rubric from the skill's `references/` directory:
 
 | Layer | Rubric File |
 |-------|-------------|
-| Vision | `.agent/skills/pipeline-rubrics/references/vision-rubric.md` |
-| Architecture | `.agent/skills/pipeline-rubrics/references/architecture-rubric.md` |
-| IA | `.agent/skills/pipeline-rubrics/references/ia-rubric.md` |
-| BE | `.agent/skills/pipeline-rubrics/references/be-rubric.md` |
-| FE | `.agent/skills/pipeline-rubrics/references/fe-rubric.md` |
+| Vision | `.agents/skills/pipeline-rubrics/references/vision-rubric.md` |
+| Architecture | `.agents/skills/pipeline-rubrics/references/architecture-rubric.md` |
+| IA | `.agents/skills/pipeline-rubrics/references/ia-rubric.md` |
+| BE | `.agents/skills/pipeline-rubrics/references/be-rubric.md` |
+| FE | `.agents/skills/pipeline-rubrics/references/fe-rubric.md` |
 
-Apply the scoring formula from `.agent/skills/pipeline-rubrics/references/scoring.md`.
+Apply the scoring formula from `.agents/skills/pipeline-rubrics/references/scoring.md`.
 
 Proceed to `/audit-ambiguity-execute` with scope and rubrics loaded.

package/template/{.agent/workflows/bootstrap-agents.md → .agents/skills/bootstrap-agents/SKILL.md}

@@ -1,5 +1,5 @@
 ---
-description: Utility — fill {{PLACEHOLDER}} values and provision skills from `.agent/skill-library/`. Called by pipeline workflows when tech stack info changes.
+description: Utility — fill {{PLACEHOLDER}} values and provision skills from `.agents/skill-library/`. Called by pipeline workflows when tech stack info changes.
 pipeline:
   position: infrastructure
   stage: provisioning
@@ -20,7 +20,7 @@ shards: [bootstrap-agents-fill, bootstrap-agents-provision]
 
 Bootstrap does two things:
 1. **Fill `{{PLACEHOLDER}}` values** in kit instruction templates
-2. **Provision skills** from `.agent/skill-library/` based on stack and surface triggers
+2. **Provision skills** from `.agents/skill-library/` based on stack and surface triggers
 
 ## Invocation Points
 
@@ -33,7 +33,7 @@ Bootstrap does two things:
 | `/implement-slice` | If implementation adds significant new dependency | New key only |
 
 **Input**: Template values (package manager, framework, database, etc.) + optional stack/surface triggers
-**Output**: Filled templates + newly installed skills in `.agent/skills/`
+**Output**: Filled templates + newly installed skills in `.agents/skills/`
 
 ---
 
@@ -41,20 +41,20 @@ Bootstrap does two things:
 
 | # | Shard | What It Does |
 |---|-------|-------------|
-| 1 | [`bootstrap-agents-fill`](.agent/workflows/bootstrap-agents-fill.md) | Receives template values, fills instruction/rule/AGENTS.md templates |
-| 2 | [`bootstrap-agents-provision`](.agent/workflows/bootstrap-agents-provision.md) | Reads skill library manifest, provisions skills, fills workflow placeholders, reports results |
+| 1 | [`bootstrap-agents-fill`](.agents/skills/bootstrap-agents-fill/SKILL.md) | Receives template values, fills instruction/rule/AGENTS.md templates |
+| 2 | [`bootstrap-agents-provision`](.agents/skills/bootstrap-agents-provision/SKILL.md) | Reads skill library manifest, provisions skills, fills workflow placeholders, reports results |
 
 ---
 
 ## Orchestration
 
-### Step A — Run `.agent/workflows/bootstrap-agents-fill.md`
+### Step A — Run `.agents/skills/bootstrap-agents-fill/SKILL.md`
 
 Receives template values from the calling workflow and fills `{{PLACEHOLDER}}` values across instruction templates, rule templates, skill templates, and `AGENTS.md`.
 
 > **MANDATORY**: After fill completes, you MUST proceed to Step B. Do NOT return to the calling workflow after Step A alone. Fill without provision is an incomplete bootstrap — the skill library remains unresolved, map cells reference skills that don't exist, and downstream workflows will fail on missing skills.
 
-### Step B — Run `.agent/workflows/bootstrap-agents-provision.md`
+### Step B — Run `.agents/skills/bootstrap-agents-provision/SKILL.md`
 
 Reads the skill library manifest, provisions matching skills based on stack/surface triggers, updates the installed skills list, fills workflow command/skill placeholders, and reports results.
 
@@ -67,6 +67,6 @@ Reads the skill library manifest, provisions matching skills based on stack/surf
 Bootstrap is safe to call multiple times:
 
 - **Already-filled placeholders**: If a `{{PLACEHOLDER}}` has already been replaced with a value, it is NOT re-filled unless the calling workflow explicitly provides a new value for that key
-- **Already-installed skills**: Skills that already exist in `.agent/skills/` are not re-copied from the library
+- **Already-installed skills**: Skills that already exist in `.agents/skills/` are not re-copied from the library
 - **New values**: New stack/surface values trigger new skill installations without affecting existing ones
 - **Partial invocation**: Bootstrap can be called with just one or two new values — it only fills what's provided