@lifeaitools/rdc-skills 0.24.38 → 0.24.41

package/commands/handoff.md

@@ -1,173 +1,173 @@
----
-name: rdc:handoff
-description: >-
-  Usage `rdc:handoff <topic>` — structured handoff from planning session to CLI agents. Produces plan doc in .rdc/plans/, work items in DB, prototype registry entry if applicable. Use when plan/prototype is finalized and ready for implementation.
----
-
-> **⚠️ 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.
-
-> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md`).
-
-
-# rdc:handoff — Planning → CLI Bridge
-
-## When to Use
-
-- A prototype has been built and needs production implementation
-- A design decision has been made and needs to be executed
-- Project lead says "hand this off", "give this to the CLI", "write it up"
-- A plan exists in the conversation but hasn't been saved to disk or database yet
-
-## What This Skill Produces
-
-1. **Plan doc** → `.rdc/plans/<topic-slug>.md` (fallback: `.rdc/plans/<topic-slug>.md`)
-2. **Database epic + child tasks** (with agent types and guide file refs)
-3. **Prototype registry entry** (if a prototype was built)
-4. **Design context entries** (for decisions made in the session)
-
-## Procedure
-
-### Step 1 — Extract the Plan
-
-Identify from the conversation:
-- What is the goal?
-- What prototypes or designs were built? Where are they?
-- What decisions were made? What was rejected and why?
-- What is the sequencing (what depends on what)?
-- Which agent types are needed?
-
-### Step 2 — Write the Plan Doc
-
-```
-.rdc/plans/<topic-slug>.md
-```
-(fallback: `.rdc/plans/<topic-slug>.md` if `.rdc/` does not exist)
-
-Template:
-```markdown
-# Plan: <Topic>
-> Route: <app route or package>
-> Status: Ready for CLI build
-> Created: <date>
-> Source: planning session
-
----
-
-## What Already Exists (Do NOT Re-implement)
-
-[List any existing components, database tables, or files
- that agents must use rather than recreate]
-
-## What Was Built in Planning (Prototype)
-
-[Describe the prototype — file location, key design decisions,
- what to preserve vs what to adapt]
-
-## Work Packages
-
-### Package 1 — <Name>
-- Agent type: frontend | backend | data | design | infra | content | cs2 | viz
-- Guide: .rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md)
-- Files to create/modify: [list]
-- Deliverables: [specific outputs]
-- Depends on: [other packages if sequential]
-
-### Package 2 — <Name>
-[...]
-
-## Sequencing
-
-Wave 1 (parallel): Package 1, Package 2
-Wave 2 (after Wave 1): Package 3
-
-## Definition of Done
-
-- [ ] [specific acceptance criterion]
-- [ ] [build verification: zero new TS errors]
-- [ ] [functional test]
-```
-
-### Step 3 — Create Database Epic + Tasks
-
-```sql
--- Check for existing epics first
-SELECT get_open_epics();
-
--- Create epic
-SELECT insert_work_item(
-  p_title       := 'EPIC: <Topic>',
-  p_description := 'See .rdc/plans/<topic-slug>.md for full spec.',
-  p_item_type   := 'epic',
-  p_priority    := 'high',
-  p_labels      := ARRAY['<system-label>'],
-  p_source      := 'planning'
-);
-
--- Create tasks (one per work package)
-SELECT insert_work_item(
-  p_title       := '<Package Name>',
-  p_description := 'What: <deliverable>
-Where: <files>
-Agent type: <type>
-Guide: .rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md)
-Design doc: .rdc/plans/<topic-slug>.md (fallback: .rdc/plans/<topic-slug>.md)
-Depends on: <other task if applicable>
-Est: <hours>',
-  p_parent_id   := '<epic-uuid>'::uuid,
-  p_item_type   := 'task',
-  p_priority    := 'high',
-  p_labels      := ARRAY['<label>'],
-  p_estimated_hours := 2,
-  p_source      := 'planning'
-);
-```
-
-### Step 4 — Register Prototype (if one was built)
-
-```sql
-INSERT INTO prototype_registry (name, component, source_path, notes, created_by)
-VALUES (
-  '<Component Name> v1',
-  '<ComponentName>',
-  'docs/source/<filename>.jsx',
-  '<Key design decisions, data shapes, what to preserve>',
-  'planning'
-)
-ON CONFLICT DO NOTHING;
-```
-
-### Step 5 — Record Design Decisions
-
-```sql
-INSERT INTO design_context (topic, context_type, summary, source, created_by)
-VALUES
-  ('<Topic>', 'decision', '<What was decided and why>', 'planning session', 'planning'),
-  ('<Topic>', 'rejected', '<What was considered but not chosen, and why>', 'planning session', 'planning');
-```
-
-## System Labels Reference
-
-| Label | When |
-|-------|------|
-| `project-a` | Your-app-specific label |
-| `marketing` | Marketing / outreach work |
-| `ui` | Component library work |
-| `data` | Schema, migrations |
-| `infrastructure` | CI/CD, deployment |
-| `cs2` | Core paradigm packages |
-| `website` | Public-facing sites |
-| `media` | Media/asset work |
-
-## Output
-
-When complete, tell the project lead:
-```
-Handoff complete:
-- Plan: .rdc/plans/<topic-slug>.md
-- Epic: <epic-id> ("<title>")
-- Tasks: <N> tasks created, wave structure: [Wave 1: X, Y | Wave 2: Z]
-- Prototype: registered at docs/source/<file> (if applicable)
-- CLI agents will pick this up on next run.
-```
+---
+name: rdc:handoff
+description: >-
+  Usage `rdc:handoff <topic>` — structured handoff from planning session to CLI agents. Produces plan doc in .rdc/plans/, work items in DB, prototype registry entry if applicable. Use when plan/prototype is finalized and ready for implementation.
+---
+
+> **⚠️ 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.
+
+> If dispatching subagents or running as a subagent: read `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md` first (fallback: `{PROJECT_ROOT}/.rdc/guides/agent-bootstrap.md`).
+
+
+# rdc:handoff — Planning → CLI Bridge
+
+## When to Use
+
+- A prototype has been built and needs production implementation
+- A design decision has been made and needs to be executed
+- Project lead says "hand this off", "give this to the CLI", "write it up"
+- A plan exists in the conversation but hasn't been saved to disk or database yet
+
+## What This Skill Produces
+
+1. **Plan doc** → `.rdc/plans/<topic-slug>.md` (fallback: `.rdc/plans/<topic-slug>.md`)
+2. **Database epic + child tasks** (with agent types and guide file refs)
+3. **Prototype registry entry** (if a prototype was built)
+4. **Design context entries** (for decisions made in the session)
+
+## Procedure
+
+### Step 1 — Extract the Plan
+
+Identify from the conversation:
+- What is the goal?
+- What prototypes or designs were built? Where are they?
+- What decisions were made? What was rejected and why?
+- What is the sequencing (what depends on what)?
+- Which agent types are needed?
+
+### Step 2 — Write the Plan Doc
+
+```
+.rdc/plans/<topic-slug>.md
+```
+(fallback: `.rdc/plans/<topic-slug>.md` if `.rdc/` does not exist)
+
+Template:
+```markdown
+# Plan: <Topic>
+> Route: <app route or package>
+> Status: Ready for CLI build
+> Created: <date>
+> Source: planning session
+
+---
+
+## What Already Exists (Do NOT Re-implement)
+
+[List any existing components, database tables, or files
+ that agents must use rather than recreate]
+
+## What Was Built in Planning (Prototype)
+
+[Describe the prototype — file location, key design decisions,
+ what to preserve vs what to adapt]
+
+## Work Packages
+
+### Package 1 — <Name>
+- Agent type: frontend | backend | data | design | infra | content | cs2 | viz
+- Guide: .rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md)
+- Files to create/modify: [list]
+- Deliverables: [specific outputs]
+- Depends on: [other packages if sequential]
+
+### Package 2 — <Name>
+[...]
+
+## Sequencing
+
+Wave 1 (parallel): Package 1, Package 2
+Wave 2 (after Wave 1): Package 3
+
+## Definition of Done
+
+- [ ] [specific acceptance criterion]
+- [ ] [build verification: zero new TS errors]
+- [ ] [functional test]
+```
+
+### Step 3 — Create Database Epic + Tasks
+
+```sql
+-- Check for existing epics first
+SELECT get_open_epics();
+
+-- Create epic
+SELECT insert_work_item(
+  p_title       := 'EPIC: <Topic>',
+  p_description := 'See .rdc/plans/<topic-slug>.md for full spec.',
+  p_item_type   := 'epic',
+  p_priority    := 'high',
+  p_labels      := ARRAY['<system-label>'],
+  p_source      := 'planning'
+);
+
+-- Create tasks (one per work package)
+SELECT insert_work_item(
+  p_title       := '<Package Name>',
+  p_description := 'What: <deliverable>
+Where: <files>
+Agent type: <type>
+Guide: .rdc/guides/<type>.md (fallback: .rdc/guides/<type>.md)
+Design doc: .rdc/plans/<topic-slug>.md (fallback: .rdc/plans/<topic-slug>.md)
+Depends on: <other task if applicable>
+Est: <hours>',
+  p_parent_id   := '<epic-uuid>'::uuid,
+  p_item_type   := 'task',
+  p_priority    := 'high',
+  p_labels      := ARRAY['<label>'],
+  p_estimated_hours := 2,
+  p_source      := 'planning'
+);
+```
+
+### Step 4 — Register Prototype (if one was built)
+
+```sql
+INSERT INTO prototype_registry (name, component, source_path, notes, created_by)
+VALUES (
+  '<Component Name> v1',
+  '<ComponentName>',
+  'docs/source/<filename>.jsx',
+  '<Key design decisions, data shapes, what to preserve>',
+  'planning'
+)
+ON CONFLICT DO NOTHING;
+```
+
+### Step 5 — Record Design Decisions
+
+```sql
+INSERT INTO design_context (topic, context_type, summary, source, created_by)
+VALUES
+  ('<Topic>', 'decision', '<What was decided and why>', 'planning session', 'planning'),
+  ('<Topic>', 'rejected', '<What was considered but not chosen, and why>', 'planning session', 'planning');
+```
+
+## System Labels Reference
+
+| Label | When |
+|-------|------|
+| `project-a` | Your-app-specific label |
+| `marketing` | Marketing / outreach work |
+| `ui` | Component library work |
+| `data` | Schema, migrations |
+| `infrastructure` | CI/CD, deployment |
+| `cs2` | Core paradigm packages |
+| `website` | Public-facing sites |
+| `media` | Media/asset work |
+
+## Output
+
+When complete, tell the project lead:
+```
+Handoff complete:
+- Plan: .rdc/plans/<topic-slug>.md
+- Epic: <epic-id> ("<title>")
+- Tasks: <N> tasks created, wave structure: [Wave 1: X, Y | Wave 2: Z]
+- Prototype: registered at docs/source/<file> (if applicable)
+- CLI agents will pick this up on next run.
+```

package/commands/help.md

@@ -1,95 +1,95 @@
----
-name: rdc:help
-description: >-
-  Usage `rdc:help` or `rdc` — manifest-driven menu of all MCP skills with
-  argument syntax, requirements, decision hints, and direct MCP/curl access.
----
-
-> **Output contract:** Checklist/table output only. No raw MCP/JSON/log dumps.
-
-# rdc:help — Manifest-Driven Skill Reference
-
-Print a concise skill reference from the plugin manifest, then stop. Do not
-ask which command to run unless the user explicitly asks for a recommendation.
-
-## Source Of Truth
-
-Resolve the manifest in this order and use the first existing file:
-
-1. `{PLUGIN_ROOT}/.claude-plugin/plugin.json`
-2. `C:/Dev/rdc-skills/.claude-plugin/plugin.json`
-3. `~/.claude/plugins/cache/rdc-skills/rdc-skills/latest/.claude-plugin/plugin.json`
-
-Read `skills_meta` from the manifest. Accept either the current object map shape
-(`skills_meta.<name>`) or an older array shape (`skills_meta[]`); normalize to
-entries before rendering. Group entries by `category` in this order:
-`planning`, `build`, `deploy`, `release`, `dev-loop`, `reporting`, `tooling`,
-`infra`.
-
-For each row, show:
-
-```text
-{slash}  —  {usage}  —  needs: {requires or "(none)"}  —  cf: {yes|no}
-```
-
-At the end, render a short decision tree from `skills_meta[].triggers`.
-
-If the manifest is unreachable, say `manifest fallback used` and render the
-static fallback table from `skills/help/SKILL.md`.
-
-## Direct MCP / curl Access
-
-Show this block after the command table so non-Claude callers have the same
-entry point. Do not summarize, compress, relabel, or omit the curl examples;
-this block is the public direct-caller contract for MCP/API/curl users.
-
-```text
-MCP endpoint: https://rdc-skills.regendevcorp.com/mcp
-Health:       curl -s https://rdc-skills.regendevcorp.com/health
-Header:       Accept: application/json, text/event-stream
-Tools:        rdc_skill_list, rdc_skill_search, rdc_skill_get
-Variants:     cli for Claude Code/Codex/local terminal; cloud for claude.ai
-Response:     SSE `data:` line contains the JSON-RPC envelope; tool text is result.content[0].text
-Catalog:      rdc_skill_list returns aliases, args, requires, produces, follows, leads_to, output_contract, codeflow_required, and variants
-```
-
-Minimal curl examples:
-
-```bash
-curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
-  -H 'Content-Type: application/json' \
-  -H 'Accept: application/json, text/event-stream' \
-  -d '{"jsonrpc":"2.0","id":0,"method":"tools/list"}' \
-  | sed -n 's/^data: //p'
-
-curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
-  -H 'Content-Type: application/json' \
-  -H 'Accept: application/json, text/event-stream' \
-  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"rdc_skill_list","arguments":{}}}'
-
-curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
-  -H 'Content-Type: application/json' \
-  -H 'Accept: application/json, text/event-stream' \
-  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"rdc_skill_search","arguments":{"query":"turn this article into social posts"}}}'
-
-curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
-  -H 'Content-Type: application/json' \
-  -H 'Accept: application/json, text/event-stream' \
-  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"rdc_skill_get","arguments":{"name":"rdc:build","variant":"cli"}}}'
-
-curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
-  -H 'Content-Type: application/json' \
-  -H 'Accept: application/json, text/event-stream' \
-  -d '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"rdc_skill_get","arguments":{"name":"rdc:build","variant":"cli","format":"json"}}}'
-```
-
-Required exact token for tests and direct callers: `"format":"json"`
-
-## Hard Rules
-
-- `cf: yes` skills must consult CodeFlow before acting.
-- Never run `pnpm build` at monorepo root. Use scoped typecheck/tests.
-- Never commit to `main` without explicit approval.
-- Never overlap agents on the same files.
-- Update work items in real time for skills that require work-items RPCs.
-- Credentials come from clauth: `curl -s http://127.0.0.1:52437/v/<service>`.
+---
+name: rdc:help
+description: >-
+  Usage `rdc:help` or `rdc` — manifest-driven menu of all MCP skills with
+  argument syntax, requirements, decision hints, and direct MCP/curl access.
+---
+
+> **Output contract:** Checklist/table output only. No raw MCP/JSON/log dumps.
+
+# rdc:help — Manifest-Driven Skill Reference
+
+Print a concise skill reference from the plugin manifest, then stop. Do not
+ask which command to run unless the user explicitly asks for a recommendation.
+
+## Source Of Truth
+
+Resolve the manifest in this order and use the first existing file:
+
+1. `{PLUGIN_ROOT}/.claude-plugin/plugin.json`
+2. `C:/Dev/rdc-skills/.claude-plugin/plugin.json`
+3. `~/.claude/plugins/cache/rdc-skills/rdc-skills/latest/.claude-plugin/plugin.json`
+
+Read `skills_meta` from the manifest. Accept either the current object map shape
+(`skills_meta.<name>`) or an older array shape (`skills_meta[]`); normalize to
+entries before rendering. Group entries by `category` in this order:
+`planning`, `build`, `deploy`, `release`, `dev-loop`, `reporting`, `tooling`,
+`infra`.
+
+For each row, show:
+
+```text
+{slash}  —  {usage}  —  needs: {requires or "(none)"}  —  cf: {yes|no}
+```
+
+At the end, render a short decision tree from `skills_meta[].triggers`.
+
+If the manifest is unreachable, say `manifest fallback used` and render the
+static fallback table from `skills/help/SKILL.md`.
+
+## Direct MCP / curl Access
+
+Show this block after the command table so non-Claude callers have the same
+entry point. Do not summarize, compress, relabel, or omit the curl examples;
+this block is the public direct-caller contract for MCP/API/curl users.
+
+```text
+MCP endpoint: https://rdc-skills.regendevcorp.com/mcp
+Health:       curl -s https://rdc-skills.regendevcorp.com/health
+Header:       Accept: application/json, text/event-stream
+Tools:        rdc_skill_list, rdc_skill_search, rdc_skill_get
+Variants:     cli for Claude Code/Codex/local terminal; cloud for claude.ai
+Response:     SSE `data:` line contains the JSON-RPC envelope; tool text is result.content[0].text
+Catalog:      rdc_skill_list returns aliases, args, requires, produces, follows, leads_to, output_contract, codeflow_required, and variants
+```
+
+Minimal curl examples:
+
+```bash
+curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
+  -H 'Content-Type: application/json' \
+  -H 'Accept: application/json, text/event-stream' \
+  -d '{"jsonrpc":"2.0","id":0,"method":"tools/list"}' \
+  | sed -n 's/^data: //p'
+
+curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
+  -H 'Content-Type: application/json' \
+  -H 'Accept: application/json, text/event-stream' \
+  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"rdc_skill_list","arguments":{}}}'
+
+curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
+  -H 'Content-Type: application/json' \
+  -H 'Accept: application/json, text/event-stream' \
+  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"rdc_skill_search","arguments":{"query":"turn this article into social posts"}}}'
+
+curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
+  -H 'Content-Type: application/json' \
+  -H 'Accept: application/json, text/event-stream' \
+  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"rdc_skill_get","arguments":{"name":"rdc:build","variant":"cli"}}}'
+
+curl -s -X POST https://rdc-skills.regendevcorp.com/mcp \
+  -H 'Content-Type: application/json' \
+  -H 'Accept: application/json, text/event-stream' \
+  -d '{"jsonrpc":"2.0","id":4,"method":"tools/call","params":{"name":"rdc_skill_get","arguments":{"name":"rdc:build","variant":"cli","format":"json"}}}'
+```
+
+Required exact token for tests and direct callers: `"format":"json"`
+
+## Hard Rules
+
+- `cf: yes` skills must consult CodeFlow before acting.
+- Never run `pnpm build` at monorepo root. Use scoped typecheck/tests.
+- Never commit to `main` without explicit approval.
+- Never overlap agents on the same files.
+- Update work items in real time for skills that require work-items RPCs.
+- Credentials come from clauth: `curl -s http://127.0.0.1:52437/v/<service>`.