@lifeaitools/rdc-skills 0.24.6 → 0.24.8

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "rdc",
-  "version": "0.24.1",
+  "version": "0.24.8",
   "description": "RDC typed-agent dispatch skill suite for Claude Code — plan, build, review, overnight unattended builds with work-item tracking and TDD enforcement.",
   "author": {
     "name": "LIFEAI",
@@ -34,19 +34,19 @@
       "name": "channel-formatter",
       "slash": "rdc:channel-formatter",
       "category": "tooling",
-      "usage": "rdc:channel-formatter <channel> [content]",
+      "usage": "rdc:channel-formatter <channel|pack> [content]",
       "args": {
         "positional": [
           {
             "name": "channel",
             "required": false,
-            "description": "Target channel: linkedin | twitter | slack | email-ext | email-int | pitch-deck | word | pdf-report | web. Inferred from the request if omitted.",
+            "description": "Target channel or pack: linkedin | twitter | twitter-thread | slack | email-ext | email-int | pitch-deck | word | pdf-report | web | strict-format | social-pack | campaign-pack | exec-pack | launch-pack. Inferred from the request if omitted.",
             "accepts": "string"
           },
           {
             "name": "content",
             "required": false,
-            "description": "Text/content to format. If omitted, formats content from the surrounding conversation.",
+            "description": "Text/content to format or repurpose. If omitted, formats or repurposes content from the surrounding conversation.",
             "accepts": "string"
           }
         ],
@@ -57,6 +57,16 @@
       "default_model": "inherit",
       "triggers": [
         "format this for linkedin",
+        "turn this article into a linkedin post",
+        "repurpose this article",
+        "make a content pack",
+        "make a social pack",
+        "make a campaign pack",
+        "turn this into a twitter thread",
+        "make posts from this",
+        "write launch posts",
+        "format this for social",
+        "extract posts from this report",
         "write a tweet",
         "social media post",
         "draft an email",
@@ -65,7 +75,12 @@
         "reformat this for"
       ],
       "follows": [],
-      "leads_to": [],
+      "leads_to": [
+        "convert",
+        "brochure",
+        "rdc-brochurify",
+        "lifeai-brochure-author"
+      ],
       "sandbox_aware": true,
       "output_contract": "guides/output-contract.md",
       "enabled_default": true,

package/.github/workflows/self-test.yml

@@ -1,29 +1,29 @@
-name: self-test
-
-on:
-  push:
-    branches: ['**']
-    tags: ['v*']
-  pull_request:
-
-jobs:
-  tier1:
-    name: Tier 1 static lint
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node 20
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-
-      - name: Run rdc:self-test --strict (Tier 1)
-        # Tier 2 requires headless claude + clauth daemon — not available in standard CI.
-        # Tier 1 catches the backtick-drift + frontmatter class of bugs.
-        run: node scripts/self-test.mjs --strict
-
+name: self-test
+
+on:
+  push:
+    branches: ['**']
+    tags: ['v*']
+  pull_request:
+
+jobs:
+  tier1:
+    name: Tier 1 static lint
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node 20
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
+      - name: Run rdc:self-test --strict (Tier 1)
+        # Tier 2 requires headless claude + clauth daemon — not available in standard CI.
+        # Tier 1 catches the backtick-drift + frontmatter class of bugs.
+        run: node scripts/self-test.mjs --strict
+
   tier2-gate:
     name: Tier 2 behavioral (tag releases only)
     runs-on: ubuntu-latest
@@ -32,14 +32,14 @@ jobs:
     env:
       ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
     steps:
-      - name: Checkout
-        uses: actions/checkout@v4
-
-      - name: Setup Node 20
-        uses: actions/setup-node@v4
-        with:
-          node-version: '20'
-
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node 20
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+
       - name: Install claude CLI
         if: env.ANTHROPIC_API_KEY != ''
         run: npm install -g @anthropic-ai/claude-code

package/MANIFEST.md

@@ -110,6 +110,9 @@ All skills have been converted from project-specific to generic/portable:
 
 ### Utility (1)
 - rdc:collab — bidirectional claude.ai ↔ Claude Code relay via file transport
+- rdc:channel-formatter — channel-native formatting and content repurposing,
+  including article-to-post, social-pack, campaign-pack, exec-pack, and
+  launch-pack outputs
 
 ### Bridge (3)
 - rdc:handoff — planning → work items
@@ -132,6 +135,26 @@ All skills have been converted from project-specific to generic/portable:
    - Interactive: `/rdc:build <epic-id>`
    - Unattended: `/rdc:overnight`
    - Quality: `/rdc:review --unattended`
+   - Content repurposing: `/rdc:channel-formatter social-pack article.md`
+
+## Channel Formatter Content Packs
+
+`rdc:channel-formatter` can strictly format copy for one channel or repurpose a
+long source into a channel-native output set.
+
+Examples:
+
+```bash
+rdc:channel-formatter linkedin article.md
+rdc:channel-formatter twitter-thread article.md
+rdc:channel-formatter social-pack article.md
+rdc:channel-formatter campaign-pack report.md
+```
+
+Use `rdc:convert` for actual Office/Markdown file conversion, `rdc:brochure`
+for HTML/folder/URL PDF rendering, and `rdc:brochurify` for Brochurify
+orchestration. Channel formatter writes and repurposes text; it does not produce
+binary Word or PDF artifacts.
 
 ## Key Differences from Source
 

package/README.md

@@ -98,6 +98,7 @@ Located in `guides/agents/` — plain markdown playbooks spawned as sub-agents:
 
 ### Utility Skills
 - rdc:collab
+- rdc:channel-formatter — channel-native formatting and content repurposing for LinkedIn, Twitter/X, Slack/Teams, email, decks, Word/PDF structure, web copy, and content packs
 
 ### Design Skills
 - rdc:design — RDC/Studio design, tokens, palettes, themes, and Rampa CLI-assisted color systems
@@ -105,6 +106,42 @@ Located in `guides/agents/` — plain markdown playbooks spawned as sub-agents:
 ### Reference
 - rdc:help
 
+## Channel Formatting and Content Packs
+
+`rdc:channel-formatter` handles both strict channel formatting and content
+repurposing. It can take a long article, memo, report, transcript, or rough
+draft and turn it into a single channel-native output or a coordinated pack.
+
+Examples:
+
+```bash
+rdc:channel-formatter linkedin article.md
+rdc:channel-formatter twitter-thread article.md
+rdc:channel-formatter social-pack article.md
+rdc:channel-formatter campaign-pack report.md
+rdc:channel-formatter strict-format "preserve this wording for LinkedIn"
+```
+
+Pack modes:
+
+- `social-pack` — LinkedIn thought-leadership post, short LinkedIn variant,
+  Twitter/X single post, Twitter/X thread, and Slack/Teams internal share.
+- `campaign-pack` — social pack plus external email intro, web excerpt, meta
+  title/description, and CTA variants.
+- `exec-pack` — internal email summary, Slack/Teams update, executive summary,
+  talking points, and a decision/ask line when supported by the source.
+- `launch-pack` — launch posts and blurbs for LinkedIn, Twitter/X, Slack/Teams,
+  external email, and web hero copy.
+
+Boundaries:
+
+- Actual `.docx`, `.pptx`, `.ppt`, or Markdown file conversion uses
+  `rdc:convert`.
+- HTML/folder/zip/URL to PDF rendering uses `rdc:brochure`.
+- Brochurify jobs use `rdc:brochurify`.
+- Brochure JSX authored with `@lifeai/brochure-kit` uses
+  `lifeai-brochure-author`.
+
 ## Key Features
 
 ### TDD Enforcement (Built In)

package/commands/build.md

@@ -1,183 +1,183 @@
----
-name: rdc:build
-description: >-
-  Usage `rdc:build <epic-id|topic> [--unattended]` — dispatch typed agents from an epic, commit, push, update work items. The build engine. Use after rdc:plan or when the project lead says "build it".
----
-
-> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
-> Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
-> One checklist upfront, updated in place, shown again at end with a 1-line verdict.
-
-> **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Destructive external calls short-circuit under the flag.
-
-
-# rdc:build — Typed Agent Dispatch Engine
-
-## When to Use
-- Plan is approved and ready to execute
-- Project lead says "build it", "go", "execute", "do not stop"
-- An epic exists with child tasks ready for implementation
-- Called by `rdc:overnight` as part of the automated build loop
-
-## Arguments
-- `rdc:build <epic-id>` — build from a specific Supabase epic
-- `rdc:build <topic>` — find the epic by label/title match
-- `rdc:build` (no args) — show open epics and ask which to build (interactive only)
-- `rdc:build <epic-id> --unattended` — silent mode for overnight builds
-
-## Agent Types & Guide Files
-
-Every dispatched agent MUST read two files before starting — in this order:
-1. `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` — credentials, git rules, completion report format
-   (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` if `.rdc/` does not exist)
-2. `{PROJECT_ROOT}/.rdc/guides/<type>.md` — role-specific guide
-   (fallback: `{PROJECT_ROOT}/.rdc/guides/<type>.md`)
-
-Include both lines in every agent prompt:
-```
-"Read {PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md first (fallback: .rdc/guides/agent-bootstrap.md), then {PROJECT_ROOT}/.rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md) before starting."
-```
-
-| Agent Type | Guide File | When to dispatch |
-|-----------|-----------|-----------------|
-| `frontend` | `.rdc/guides/frontend.md` | React components, pages, UI, Tailwind, animation |
-| `backend` | `.rdc/guides/backend.md` | API routes, server components, database queries, auth |
-| `data` | `.rdc/guides/data.md` | Migrations, schema changes, RPC functions |
-| `design` | `.rdc/guides/design.md` | Visual design, brand palettes, OG images, token work |
-| `infra` | `.rdc/guides/infrastructure.md` | CI/CD, deployment, DNS, SSL |
-| `content` | `.rdc/guides/content.md` | Marketing copy, messaging, tone |
-| `cs2` | `.rdc/guides/cs2.md` | CS 2.0 paradigm work (generic) |
-| `hail` | `.rdc/guides/cs2.md` + `packages/hail/CLAUDE.md` | Grammar, DSL compiler, evolution |
-| `pal` | `.rdc/guides/cs2.md` + `packages/pal/CLAUDE.md` | Sessions, moment windows, graph memory |
-| `bpmn` | `.rdc/guides/cs2.md` + `docs/systems/<domain>/flowable-bpmn-architecture.md` | BPMN flows, governance |
-| `virtue` | `.rdc/guides/cs2.md` + `packages/virtue-engine/CLAUDE.md` | Virtue weights, coherence, certification |
-| `viz` | `.rdc/guides/frontend.md` + `.rdc/guides/design.md` | Custom viz components, charts, diagrams |
-
-### How to classify a task → agent type
-
-Read the task title and description, then:
-- Mentions React, component, page, UI, Tailwind → `frontend`
-- Mentions API route, server, database query, auth → `backend`
-- Mentions migration, schema, table, RPC → `data`
-- Mentions brand, palette, typography, OG image → `design`
-- Mentions deploy, infrastructure, CI, DNS → `infra`
-- Mentions copy, messaging, email template → `content`
-- Mentions grammar, DSL, compiler → `hail`
-- Mentions session, moment, memory graph → `pal`
-- Mentions BPMN, flow, governance → `bpmn`
-- Mentions virtue, coherence, certification → `virtue`
-- Mentions visualization, chart, diagram, SVG → `viz`
-- Multiple types? Dispatch multiple agents, each with its guide.
-
-## Procedure
-
-1. **Load the epic:**
-   ```sql
-   SELECT get_work_items_by_epic('<epic-id>', 'todo');
-   ```
-   - Interactive (no args): show open epics, ask which to build
-   - Unattended (no tasks found): escalate via advisor tool
-
-2. **CHECK FOR EXISTING WORK (mandatory — never skip):**
-   ```sql
-   -- Check if prototypes exist from earlier sessions
-   SELECT name, component, source_path, status, notes
-   FROM prototype_registry
-   WHERE status IN ('prototype', 'converting')
-   ORDER BY created_at DESC;
-
-   -- Check for design decisions on this topic
-   SELECT topic, context_type, summary, source
-   FROM design_context
-   WHERE topic ILIKE '%<epic-topic>%'
-   ORDER BY created_at DESC;
-   ```
-   **If a prototype exists: ADAPT IT. Do not build from scratch.**
-   Tell the agent: "Read <source_path> first and convert it to the production contract."
-   
-   **If design decisions exist: follow them.** Include the summary in the agent prompt.
-
-3. **Load the plan** (if exists): check `.rdc/plans/` for matching topic (fallback: `.rdc/plans/`).
-
-4. **Read CLAUDE.md files** for all affected packages.
-
-5. **Classify each task** → assign agent type from the table above.
-
-6. **Group tasks into waves** — parallelize tasks with no file overlap:
-   - Wave 1: independent tasks (different packages/files)
-   - Wave 2: tasks that depend on Wave 1 outputs
-   - Wave 3: integration tasks
-
-7. **For each wave — dispatch typed agents in parallel:**
-   - Set work item to `in_progress` before dispatching
-   - Each agent prompt MUST include:
-     - `"Read {PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md first (fallback: .rdc/guides/agent-bootstrap.md), then {PROJECT_ROOT}/.rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md) before starting."`
-     - Specific files to create/modify
-     - Exact deliverables and commit message
-     - `"NEVER run pnpm build/test. NEVER modify files outside your scope."`
-   - Use `run_in_background: true` for parallel execution
-   - NEVER let agents overlap on the same files
-
-8. **Post-wave test gate (mandatory):**
-   After all agents in a wave complete, before marking tasks done:
-   ```bash
-   # For each package modified in this wave:
-   cd packages/<name> && npx vitest run 2>&1 | tail -20
-   ```
-   - All tests must pass before proceeding to next wave
-   - If tests fail: fix before marking the wave done
-   - NEVER use `pnpm build` or `pnpm turbo test` — vitest only per package
-   - New code must have tests: if a modified package shows 0 new test files, flag it
-
-9. **As agents complete:**
-   - Verify commit landed on the development branch
-   - Push to origin *(skip if `$RDC_TEST=1` — echo `[RDC_TEST] skipping git push` instead)*
+---
+name: rdc:build
+description: >-
+  Usage `rdc:build <epic-id|topic> [--unattended]` — dispatch typed agents from an epic, commit, push, update work items. The build engine. Use after rdc:plan or when the project lead says "build it".
+---
+
+> **⚠️ OUTPUT CONTRACT (READ FIRST):** `guides/output-contract.md`
+> Checklist-only output. No tool-call narration. No raw MCP/JSON/log dumps.
+> One checklist upfront, updated in place, shown again at end with a 1-line verdict.
+
+> **Sandbox contract:** This skill honors `RDC_TEST=1` per `guides/agent-bootstrap.md` § RDC_TEST Sandbox Contract. Destructive external calls short-circuit under the flag.
+
+
+# rdc:build — Typed Agent Dispatch Engine
+
+## When to Use
+- Plan is approved and ready to execute
+- Project lead says "build it", "go", "execute", "do not stop"
+- An epic exists with child tasks ready for implementation
+- Called by `rdc:overnight` as part of the automated build loop
+
+## Arguments
+- `rdc:build <epic-id>` — build from a specific Supabase epic
+- `rdc:build <topic>` — find the epic by label/title match
+- `rdc:build` (no args) — show open epics and ask which to build (interactive only)
+- `rdc:build <epic-id> --unattended` — silent mode for overnight builds
+
+## Agent Types & Guide Files
+
+Every dispatched agent MUST read two files before starting — in this order:
+1. `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` — credentials, git rules, completion report format
+   (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` if `.rdc/` does not exist)
+2. `{PROJECT_ROOT}/.rdc/guides/<type>.md` — role-specific guide
+   (fallback: `{PROJECT_ROOT}/.rdc/guides/<type>.md`)
+
+Include both lines in every agent prompt:
+```
+"Read {PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md first (fallback: .rdc/guides/agent-bootstrap.md), then {PROJECT_ROOT}/.rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md) before starting."
+```
+
+| Agent Type | Guide File | When to dispatch |
+|-----------|-----------|-----------------|
+| `frontend` | `.rdc/guides/frontend.md` | React components, pages, UI, Tailwind, animation |
+| `backend` | `.rdc/guides/backend.md` | API routes, server components, database queries, auth |
+| `data` | `.rdc/guides/data.md` | Migrations, schema changes, RPC functions |
+| `design` | `.rdc/guides/design.md` | Visual design, brand palettes, OG images, token work |
+| `infra` | `.rdc/guides/infrastructure.md` | CI/CD, deployment, DNS, SSL |
+| `content` | `.rdc/guides/content.md` | Marketing copy, messaging, tone |
+| `cs2` | `.rdc/guides/cs2.md` | CS 2.0 paradigm work (generic) |
+| `hail` | `.rdc/guides/cs2.md` + `packages/hail/CLAUDE.md` | Grammar, DSL compiler, evolution |
+| `pal` | `.rdc/guides/cs2.md` + `packages/pal/CLAUDE.md` | Sessions, moment windows, graph memory |
+| `bpmn` | `.rdc/guides/cs2.md` + `docs/systems/<domain>/flowable-bpmn-architecture.md` | BPMN flows, governance |
+| `virtue` | `.rdc/guides/cs2.md` + `packages/virtue-engine/CLAUDE.md` | Virtue weights, coherence, certification |
+| `viz` | `.rdc/guides/frontend.md` + `.rdc/guides/design.md` | Custom viz components, charts, diagrams |
+
+### How to classify a task → agent type
+
+Read the task title and description, then:
+- Mentions React, component, page, UI, Tailwind → `frontend`
+- Mentions API route, server, database query, auth → `backend`
+- Mentions migration, schema, table, RPC → `data`
+- Mentions brand, palette, typography, OG image → `design`
+- Mentions deploy, infrastructure, CI, DNS → `infra`
+- Mentions copy, messaging, email template → `content`
+- Mentions grammar, DSL, compiler → `hail`
+- Mentions session, moment, memory graph → `pal`
+- Mentions BPMN, flow, governance → `bpmn`
+- Mentions virtue, coherence, certification → `virtue`
+- Mentions visualization, chart, diagram, SVG → `viz`
+- Multiple types? Dispatch multiple agents, each with its guide.
+
+## Procedure
+
+1. **Load the epic:**
+   ```sql
+   SELECT get_work_items_by_epic('<epic-id>', 'todo');
+   ```
+   - Interactive (no args): show open epics, ask which to build
+   - Unattended (no tasks found): escalate via advisor tool
+
+2. **CHECK FOR EXISTING WORK (mandatory — never skip):**
+   ```sql
+   -- Check if prototypes exist from earlier sessions
+   SELECT name, component, source_path, status, notes
+   FROM prototype_registry
+   WHERE status IN ('prototype', 'converting')
+   ORDER BY created_at DESC;
+
+   -- Check for design decisions on this topic
+   SELECT topic, context_type, summary, source
+   FROM design_context
+   WHERE topic ILIKE '%<epic-topic>%'
+   ORDER BY created_at DESC;
+   ```
+   **If a prototype exists: ADAPT IT. Do not build from scratch.**
+   Tell the agent: "Read <source_path> first and convert it to the production contract."
+   
+   **If design decisions exist: follow them.** Include the summary in the agent prompt.
+
+3. **Load the plan** (if exists): check `.rdc/plans/` for matching topic (fallback: `.rdc/plans/`).
+
+4. **Read CLAUDE.md files** for all affected packages.
+
+5. **Classify each task** → assign agent type from the table above.
+
+6. **Group tasks into waves** — parallelize tasks with no file overlap:
+   - Wave 1: independent tasks (different packages/files)
+   - Wave 2: tasks that depend on Wave 1 outputs
+   - Wave 3: integration tasks
+
+7. **For each wave — dispatch typed agents in parallel:**
+   - Set work item to `in_progress` before dispatching
+   - Each agent prompt MUST include:
+     - `"Read {PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md first (fallback: .rdc/guides/agent-bootstrap.md), then {PROJECT_ROOT}/.rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md) before starting."`
+     - Specific files to create/modify
+     - Exact deliverables and commit message
+     - `"NEVER run pnpm build/test. NEVER modify files outside your scope."`
+   - Use `run_in_background: true` for parallel execution
+   - NEVER let agents overlap on the same files
+
+8. **Post-wave test gate (mandatory):**
+   After all agents in a wave complete, before marking tasks done:
+   ```bash
+   # For each package modified in this wave:
+   cd packages/<name> && npx vitest run 2>&1 | tail -20
+   ```
+   - All tests must pass before proceeding to next wave
+   - If tests fail: fix before marking the wave done
+   - NEVER use `pnpm build` or `pnpm turbo test` — vitest only per package
+   - New code must have tests: if a modified package shows 0 new test files, flag it
+
+9. **As agents complete:**
+   - Verify commit landed on the development branch
+   - Push to origin *(skip if `$RDC_TEST=1` — echo `[RDC_TEST] skipping git push` instead)*
    - Ensure the agent submitted `implementation_report.codeflow_post`, then set the work item to `review`; the validator closes `done`
-   - Continue to next wave
-
-   **If an agent fails:**
-   - Interactive: diagnose before retrying
-   - Unattended: retry once; on second failure escalate via advisor
-     ```
-     BUILD_STATUS: { wave, tasks_done, tasks_failed, commits, escalated: true }
-     ```
-
+   - Continue to next wave
+
+   **If an agent fails:**
+   - Interactive: diagnose before retrying
+   - Unattended: retry once; on second failure escalate via advisor
+     ```
+     BUILD_STATUS: { wave, tasks_done, tasks_failed, commits, escalated: true }
+     ```
+
 10. **Final verification gate (mandatory — before marking work or epic done):**
-    Dispatch the verify agent (see `guides/agents/verify.md`) across every package/app touched in this build.
-    The Iron Law: **NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.**
-    - Run `npx vitest run --dir <pkg>` fresh for each touched package
-    - Run `npx tsc --noEmit --project <pkg>/tsconfig.json` for each
-    - Read the full output — zero failures, zero type errors
-    - If any step fails: fix and re-run the entire gate. Do not skip.
-    - NEVER `pnpm build` / `pnpm test` / `pnpm -r` (crashes machine)
-
-11. **After verification passes:**
-    - Push all commits:
-      ```bash
-      if [ "$RDC_TEST" != "1" ]; then
-        git push origin {development-branch}
-      else
-        echo "[RDC_TEST] skipping git push origin {development-branch}"
-      fi
-      ```
-    - Update epic version: `bump_epic_version()`
-    - Report summary with verification evidence quoted
-
-## Agent TDD Requirements
-
-When dispatching agents, include in every prompt:
-```
-TDD REQUIREMENT: Write tests FIRST for new functions/modules.
-Run: npx vitest run packages/<name> to verify red → implement → verify green.
-NEVER run pnpm build or pnpm turbo. Use npx vitest run only.
-```
-
-## Rules
-- Branch: development branch only (auto-commit, no confirmation needed)
-- NEVER let two agents edit the same file
-- NEVER run `pnpm build` (crashes system) — code only
-- Every agent reads its guide file — no exceptions
-- Update Supabase work items IN REAL TIME — not batch at end
-- Push after each wave, not just at the end
-- Unattended: NEVER pause — continue automatically
-- Unattended: max 2 retries per task before escalating to advisor
+    Dispatch the verify agent (see `guides/agents/verify.md`) across every package/app touched in this build.
+    The Iron Law: **NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION EVIDENCE.**
+    - Run `npx vitest run --dir <pkg>` fresh for each touched package
+    - Run `npx tsc --noEmit --project <pkg>/tsconfig.json` for each
+    - Read the full output — zero failures, zero type errors
+    - If any step fails: fix and re-run the entire gate. Do not skip.
+    - NEVER `pnpm build` / `pnpm test` / `pnpm -r` (crashes machine)
+
+11. **After verification passes:**
+    - Push all commits:
+      ```bash
+      if [ "$RDC_TEST" != "1" ]; then
+        git push origin {development-branch}
+      else
+        echo "[RDC_TEST] skipping git push origin {development-branch}"
+      fi
+      ```
+    - Update epic version: `bump_epic_version()`
+    - Report summary with verification evidence quoted
+
+## Agent TDD Requirements
+
+When dispatching agents, include in every prompt:
+```
+TDD REQUIREMENT: Write tests FIRST for new functions/modules.
+Run: npx vitest run packages/<name> to verify red → implement → verify green.
+NEVER run pnpm build or pnpm turbo. Use npx vitest run only.
+```
+
+## Rules
+- Branch: development branch only (auto-commit, no confirmation needed)
+- NEVER let two agents edit the same file
+- NEVER run `pnpm build` (crashes system) — code only
+- Every agent reads its guide file — no exceptions
+- Update Supabase work items IN REAL TIME — not batch at end
+- Push after each wave, not just at the end
+- Unattended: NEVER pause — continue automatically
+- Unattended: max 2 retries per task before escalating to advisor