@a5c-ai/babysitter-github 0.1.1-staging.0a3fc67d → 0.1.1-staging.400de59e

package/.github/plugin.json

@@ -0,0 +1,25 @@
+{
+  "name": "babysitter",
+  "version": "0.1.0",
+  "description": "Orchestrate complex, multi-step workflows with event-sourced state management, hook-based extensibility, and human-in-the-loop approval -- powered by the Babysitter SDK",
+  "author": { "name": "a5c.ai", "email": "support@a5c.ai" },
+  "license": "MIT",
+  "skills": "skills/",
+  "hooks": "hooks.json",
+  "commands": "commands/",
+  "agents": "AGENTS.md",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/a5c-ai/babysitter"
+  },
+  "keywords": [
+    "orchestration",
+    "workflow",
+    "automation",
+    "event-sourced",
+    "hooks",
+    "github-copilot",
+    "agent",
+    "LLM"
+  ]
+}

package/README.md

@@ -19,6 +19,32 @@ directly.
 
 ## Installation
 
+### From marketplace (recommended)
+
+Register the a5c.ai marketplace and install the plugin:
+
+```bash
+# Register the marketplace
+copilot plugin marketplace add a5c-ai/babysitter
+
+# Install the plugin
+copilot plugin install babysitter
+```
+
+### Direct GitHub install
+
+Install directly from the Git repository using Copilot CLI. Copilot CLI
+discovers the plugin via `.github/plugin/marketplace.json` at the repo root:
+
+```bash
+copilot plugin install a5c-ai/babysitter
+```
+
+### Alternative Installation (npm / development)
+
+For development or environments where the Copilot CLI plugin system is not
+available, install via npm:
+
 Install the SDK CLI first:
 
 ```bash
@@ -54,6 +80,14 @@ babysitter process-library:active --json
 
 ## Uninstallation
 
+Via Copilot CLI:
+
+```bash
+copilot plugin uninstall babysitter
+```
+
+Via npm:
+
 ```bash
 babysitter-github uninstall
 ```
@@ -64,8 +98,8 @@ The plugin provides:
 
 - `skills/babysit/SKILL.md` as the core orchestration entrypoint
 - Mode wrapper skills such as `$call`, `$plan`, and `$resume`
-- Plugin-level lifecycle hooks for `SessionStart`, `UserPromptSubmit`, and
-  `Stop`
+- Plugin-level lifecycle hooks for `sessionStart`, `sessionEnd`, and
+  `userPromptSubmitted`
 
 The process library is fetched and bound through the SDK CLI in
 `~/.a5c/active/process-library.json`.
@@ -113,10 +147,10 @@ Fires when a new Copilot CLI session begins. The hook:
    `versions.json`)
 3. Creates baseline session state in the `.a5c` state directory
 
-### Stop
+### SessionEnd
 
-The orchestration loop driver. When Copilot CLI attempts to end its turn,
-this hook intercepts the exit and:
+The orchestration loop driver. Registered as `sessionEnd` in `hooks.json`,
+this hook fires when the Copilot CLI session ends and:
 
 1. Checks whether the active run has completed or emitted a completion proof
 2. If the run is still in progress, re-injects the next orchestration step
@@ -128,7 +162,7 @@ This is what keeps Babysitter iterating autonomously within the Copilot CLI
 session -- each turn performs one orchestration phase, and the Stop hook
 decides whether to loop or yield.
 
-### UserPromptSubmit
+### UserPromptSubmitted
 
 Fires before a user prompt reaches the model. The hook applies
 density-filter compression to long user prompts to reduce token usage while
@@ -139,9 +173,8 @@ preserving semantic content.
 ### AGENTS.md
 
 The plugin uses `AGENTS.md` (the Copilot CLI equivalent of `CLAUDE.md`) for
-custom agent instructions. This file is set via the `contextFileName` field
-in `plugin.json` and is read by Copilot CLI to configure agent behavior
-within sessions.
+custom agent instructions. This file is read by Copilot CLI to configure
+agent behavior within sessions.
 
 ### Environment Variables
 
@@ -174,6 +207,10 @@ Copilot CLI looks for the plugin manifest in these paths, checked in order:
 
 The first match wins. This plugin uses `plugin.json` at the package root.
 
+For marketplace discovery, Copilot CLI looks for `.github/plugin/marketplace.json`
+at the repository root. This file lists all available plugins in the repo and is
+used when installing via `copilot plugin install OWNER/REPO`.
+
 ### plugin.json Schema
 
 The manifest declares metadata, skills, hooks, and optional integrations:
@@ -187,7 +224,7 @@ The manifest declares metadata, skills, hooks, and optional integrations:
 | `license` | No | `string` | SPDX license identifier |
 | `keywords` | No | `string[]` | Searchable tags for marketplace discovery |
 | `agents` | No | `string` | Path to agents directory |
-| `skills` | No | `array` | Array of skill directory paths (see below) |
+| `skills` | No | `string` | Path to skills directory (auto-discovers SKILL.md files in subdirectories) |
 | `hooks` | No | `string` | Path to `hooks.json` |
 | `mcpServers` | No | `string` | Path to `.mcp.json` for MCP server configuration |
 
@@ -200,15 +237,9 @@ Example from this plugin:
   "description": "Orchestrate complex, multi-step workflows ...",
   "author": "a5c.ai",
   "license": "MIT",
-  "hooks": {
-    "sessionStart": "hooks/session-start.sh",
-    "sessionEnd": "hooks/session-end.sh",
-    "userPromptSubmitted": "hooks/user-prompt-submitted.sh"
-  },
-  "skills": [
-    { "name": "babysit", "file": "skills/babysit/SKILL.md" },
-    { "name": "call", "file": "skills/call/SKILL.md" }
-  ],
+  "skills": "skills/",
+  "hooks": "hooks.json",
+  "commands": [],
   "keywords": ["orchestration", "workflow", "automation"]
 }
 ```
@@ -309,8 +340,8 @@ repositories that contain a manifest listing available plugins.
 
 ### Creating a Marketplace
 
-A marketplace is a Git repository with a `marketplace.json` file in
-`.github/plugin/` or `.claude-plugin/`:
+A marketplace is a Git repository with a `marketplace.json` file at the
+repository root in `.github/plugin/marketplace.json`:
 
 ```json
 {
@@ -387,6 +418,7 @@ These registries are available without running `marketplace add`.
 ```
 plugins/babysitter-github/
   plugin.json              # Plugin manifest (skills, hooks, metadata)
+  .github/plugin.json      # Plugin manifest (alternate discovery path)
   hooks.json               # Hook configuration (sessionStart, sessionEnd, userPromptSubmitted)
   hooks/
     session-start.sh       # SessionStart lifecycle hook
@@ -416,6 +448,12 @@ plugins/babysitter-github/
 
 ## Verification
 
+Verify marketplace registration:
+
+```bash
+copilot plugin marketplace list
+```
+
 Verify the installed plugin:
 
 ```bash

package/bin/install-shared.js

@@ -5,7 +5,7 @@ const os = require('os');
 const path = require('path');
 const { spawnSync } = require('child_process');
 
-const PLUGIN_NAME = 'babysitter-github';
+const PLUGIN_NAME = 'babysitter';
 const PLUGIN_CATEGORY = 'Coding';
 const LEGACY_HOOK_SCRIPT_NAMES = [
   'session-start.sh',

package/bin/install.js

@@ -28,16 +28,16 @@ function registerViaCopilotCli(pluginRoot) {
   });
 
   if (result.status === 0) {
-    console.log(`[babysitter-github] Registered plugin via 'copilot plugin install'`);
+    console.log(`[babysitter] Registered plugin via 'copilot plugin install'`);
     return true;
   }
 
   // CLI not available or failed -- fall back to manual registration
   const stderr = (result.stderr || '').trim();
   if (result.error || stderr.includes('not found') || stderr.includes('not recognized')) {
-    console.log(`[babysitter-github] Copilot CLI not found, using manual registration`);
+    console.log(`[babysitter] Copilot CLI not found, using manual registration`);
   } else {
-    console.warn(`[babysitter-github] 'copilot plugin install' failed: ${stderr || 'unknown error'}, using manual registration`);
+    console.warn(`[babysitter] 'copilot plugin install' failed: ${stderr || 'unknown error'}, using manual registration`);
   }
   return false;
 }
@@ -47,7 +47,7 @@ function main() {
   const pluginRoot = getHomePluginRoot();
   const marketplacePath = getHomeMarketplacePath();
 
-  console.log(`[babysitter-github] Installing plugin to ${pluginRoot}`);
+  console.log(`[babysitter] Installing plugin to ${pluginRoot}`);
 
   try {
     copyPluginBundle(PACKAGE_ROOT, pluginRoot);
@@ -62,18 +62,18 @@ function main() {
     installCopilotSurface(PACKAGE_ROOT, copilotHome);
 
     const active = ensureGlobalProcessLibrary(PACKAGE_ROOT);
-    console.log(`[babysitter-github]   marketplace: ${marketplacePath}`);
-    console.log(`[babysitter-github]   copilot config: ${path.join(copilotHome, 'config.json')}`);
-    console.log(`[babysitter-github]   process library: ${active.binding?.dir}`);
+    console.log(`[babysitter]   marketplace: ${marketplacePath}`);
+    console.log(`[babysitter]   copilot config: ${path.join(copilotHome, 'config.json')}`);
+    console.log(`[babysitter]   process library: ${active.binding?.dir}`);
     if (active.defaultSpec?.cloneDir) {
-      console.log(`[babysitter-github]   process library clone: ${active.defaultSpec.cloneDir}`);
+      console.log(`[babysitter]   process library clone: ${active.defaultSpec.cloneDir}`);
     }
-    console.log(`[babysitter-github]   process library state: ${active.stateFile}`);
+    console.log(`[babysitter]   process library state: ${active.stateFile}`);
     warnWindowsHooks();
-    console.log('[babysitter-github] Installation complete!');
-    console.log('[babysitter-github] Restart GitHub Copilot CLI to pick up the installed plugin and config changes.');
+    console.log('[babysitter] Installation complete!');
+    console.log('[babysitter] Restart GitHub Copilot CLI to pick up the installed plugin and config changes.');
   } catch (err) {
-    console.error(`[babysitter-github] Failed to install plugin: ${err.message}`);
+    console.error(`[babysitter] Failed to install plugin: ${err.message}`);
     process.exitCode = 1;
   }
 }

package/bin/uninstall.js

@@ -12,7 +12,7 @@ const {
   removeMarketplaceEntry,
 } = require('./install-shared');
 
-const PLUGIN_NAME = 'babysitter-github';
+const PLUGIN_NAME = 'babysitter';
 
 /**
  * Attempt to unregister the plugin via `copilot plugin uninstall`.

package/commands/assimilate.md

@@ -0,0 +1,37 @@
+---
+description: Assimilate an external methodology, harness, or specification into babysitter process definitions with skills and agents.
+argument-hint: Target to assimilate (e.g. repo URL, harness name, or spec path)
+allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
+---
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+Use the assimilation domain processes from the active process library to convert external sources into well-defined babysitter process definitions with accompanying skills/ and agents/ directories.
+
+If the workspace does not already have an active process-library binding, initialize it first through the shared global SDK binding:
+
+```bash
+babysitter process-library:active --json
+```
+
+Run the process after formalizing it.
+
+Available assimilation workflows:
+- **methodology-assimilation** (`specializations/domains/assimilation/workflows/methodology-assimilation`) - Learns an external methodology from its repo and converts procedural instructions, commands, and manual flows into babysitter processes with refactored skills and agents. Supports output as methodology or specialization.
+- **harness integration** (`specializations/domains/assimilation/harness/*`) - Integrates babysitter SDK with a specific AI coding harness (generic, codex, opencode, gemini-cli, openclaw, antigravity).
+
+During the interview phase, determine which assimilation workflow to use based on the user's target:
+- If the target is a **repo URL or methodology name** then use the methodology-assimilation workflow.
+- If the target is a **harness name** (e.g. codex, opencode, antigravity) then use the matching harness process.
+- If the target is a **specification or other source** then adapt the methodology-assimilation workflow for the spec format.
+- If unclear, ask the user to clarify the assimilation target and type.
+
+## After Assimilation: Contribute Back
+
+After successfully assimilating a methodology or harness integration, prompt the user to share it with the community. The assimilated process definitions, skills, and agents could benefit other babysitter users:
+
+- **Completed a methodology assimilation**: `/babysitter:contrib library contribution: assimilated [methodology-name] into babysitter process definitions`
+- **Completed a harness integration**: `/babysitter:contrib library contribution: [harness-name] harness integration`
+- **Hit issues during assimilation** (e.g. unsupported patterns, missing SDK features): `/babysitter:contrib bug report: assimilation of [target] failed because [description]` or `/babysitter:contrib feature request: [what the SDK needs to support]`
+
+Even just reporting that an assimilation didn't work well helps improve babysitter for everyone.

package/commands/call.md

@@ -0,0 +1,7 @@
+---
+description: Orchestrate a babysitter run. use this command to start babysitting a complex workflow.
+argument-hint: Specific instructions for the run.
+allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
+---
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).

package/commands/cleanup.md

@@ -0,0 +1,20 @@
+---
+description: Clean up .a5c/runs and .a5c/processes directories. Aggregates insights from completed/failed runs into docs/run-history-insights.md, then removes old run data and orphaned process files.
+argument-hint: "[--dry-run] [--keep-days N] Optional flags. --dry-run shows what would be removed without deleting. --keep-days N keeps runs newer than N days (default 7)."
+allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
+---
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+Create and run a cleanup process using the process at `skills\babysit\process\cradle\cleanup-runs.js/processes/cleanup-runs.js`.
+
+Implementation notes (for the process):
+- Parse arguments for `--dry-run` flag (if present, set dryRun: true in inputs) and `--keep-days N` (default: 7)
+- The process scans .a5c/runs/ for completed/failed runs, aggregates insights, writes summaries, then removes old data
+- Always show the user what will be removed before removing (in interactive mode via breakpoints)
+- In non-interactive mode (yolo), proceed with cleanup using defaults
+- The insights file goes to docs/run-history-insights.md
+- Only remove terminal runs (completed/failed) older than the keep-days threshold
+- Never remove active/in-progress runs
+- Remove orphaned process files not referenced by remaining runs
+- After cleanup, show remaining run count and disk usage

package/commands/contrib.md

@@ -0,0 +1,33 @@
+---
+description: Submit feedback or contribute to babysitter project
+argument-hint: Specific instructions for the run.
+allowed-tools: Read, Grep, Write, Task, Bash, Edit, Grep, Glob, WebFetch, WebSearch, Search, AskUserQuestion, TodoWrite, TodoRead, Skill, BashOutput, KillShell, MultiEdit, LS
+---
+
+Invoke the babysitter:babysit skill (using the Skill tool) and follow its instructions (SKILL.md).
+
+## Process Routing
+
+Contribution processes live under the active process library's `cradle/` directory. Resolve the active library root with `babysitter process-library:active --json` and route based on arguments:
+
+### Issue-based (opens a GitHub issue in a5c-ai/babysitter)
+ * **Bug report** → `cradle/bug-report.js#process` — Report a bug in the SDK, CLI, process library, etc.
+ * **Feature request** → `cradle/feature-request.js#process` — Request a new feature or enhancement
+ * **Documentation question** → `cradle/documentation-question.js#process` — Ask about undocumented behavior or missing docs
+
+### PR-based (forks repo, creates branch, submits PR to a5c-ai/babysitter)
+ * **Bugfix** → `cradle/bugfix.js#process` — User already has the fix for a bug
+ * **Feature implementation** → `cradle/feature-implementation-contribute.js#process` — User already has a feature implementation
+ * **Harness integration** → `cradle/feature-harness-integration-contribute.js#process` — User has a harness (CI/CD, IDE, editor) integration
+ * **Library contribution** → `cradle/library-contribution.js#process` — New or improved process/skill/subagent for the library
+ * **Documentation answer** → `cradle/documentation-contribute-answer.js#process` — User has an answer for an unanswered docs question
+
+### Router (when arguments are empty or general)
+ * **Contribute** → `cradle/contribute.js#process` — Explains contribution types and routes to the specific process
+
+## Contribution Rules
+
+ * PR-based contributions: fork the babysitter repo (a5c-ai/babysitter) for the user, ask to star if not already starred, perform changes, submit PR
+ * Issue-based contributions: gather details, search for duplicates, review, then open an issue in a5c-ai/babysitter
+ * Add breakpoints (permissions) before ALL gh actions (fork, star, submit PR/issue) to allow user review and cancellation
+ * If arguments are empty: use the `contribute.js` router process to show options and route accordingly