{
  "id": "page:docs-reference-process-packaging-implementation-2026-01-20",
  "_kind": "Page",
  "_file": "wiki/docs/reference/process-packaging-implementation-2026-01-20.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "sourcePath": "docs/reference/PROCESS_PACKAGING_IMPLEMENTATION_2026-01-20.md",
    "sourceKind": "repo-docs",
    "title": "Process Packaging Implementation",
    "displayName": "Process Packaging Implementation",
    "slug": "docs/reference/process-packaging-implementation-2026-01-20",
    "articlePath": "wiki/docs/reference/PROCESS_PACKAGING_IMPLEMENTATION_2026-01-20.md",
    "article": "\n# Process Packaging Implementation\n\n**Date:** 2026-01-20\n**Task:** Todo #7 - Allow packaging processes with skills\n**Status:** Historical implementation note, updated for the current packaging model\n\n---\n\n## Summary\n\nThis report originally documented a prototype that colocated example processes inside a skill package. The current public layout uses a different packaging model:\n\n- The built-in process library lives under `library/`.\n- The Babysitter plugin source provides skill instructions and plugin behavior under `plugins/babysitter-unified/`.\n- Project-local `.a5c/` directories contain copied or customized assets for a specific workspace.\n\nThe canonical built-in source is no longer a plugin-internal `process/` directory.\n\n---\n\n## Current Packaging Model\n\n### 1. Built-in Library\n\nThe shipped process library is in `library/`. That is where public docs should point when they reference built-in processes, examples, methodologies, specializations, or shared assets.\n\nReal examples in this repo include:\n\n- `library/tdd-quality-convergence.js`\n- `library/tdd-quality-convergence.md`\n- `library/examples/tdd-quality-convergence-example.json`\n- `library/methodologies/plan-and-execute.js`\n- `library/methodologies/ralph.js`\n- `library/methodologies/devin.js`\n\n### 2. Plugin Package\n\nThe plugin source lives under `plugins/babysitter-unified/`. It provides:\n\n- `plugins/babysitter-unified/skills/babysit/SKILL.md`\n- plugin metadata and installation behavior\n- references and hook-related assets\n\nThe plugin does not currently ship the full process tree inside `plugins/babysitter-unified/skills/babysit/`.\n\n### 3. Project-Local Assets\n\nProject-local copies live under `.a5c/`, for example:\n\n- `.a5c/processes/`\n- `.a5c/skills/`\n- `.a5c/agents/`\n\nThose are local copies, generated assets, or overrides. They are useful for customization, but they are not the repository’s built-in library location.\n\n### 4. Active Library Binding\n\nBabysitter resolves the active library through the process-library binding managed by the SDK and CLI.\n\n```bash\nbabysitter process-library:active --json\n```\n\nThat command reports the currently bound library root and revision.\n\n---\n\n## Current Discovery and Execution\n\n### Discovery\n\n```bash\nfind library -name \"*.js\" -type f\n```\n\nUse `.a5c/processes/` only when you intentionally want project-local copies or overrides.\n\n### Execution\n\n```bash\nbabysitter run:create \\\n  --process-id tdd-quality-convergence \\\n  --entry library/tdd-quality-convergence.js#process \\\n  --inputs library/examples/tdd-quality-convergence-example.json\n```\n\n### Integration\n\n```javascript\nimport { process as tddQualityConvergence } from './library/tdd-quality-convergence.js';\n\nexport async function deploymentProcess(inputs, ctx) {\n  return await tddQualityConvergence(inputs, ctx);\n}\n```\n\nIf a team copies a built-in process into `.a5c/processes/`, they can update the entry path to the local copy explicitly.\n\n---\n\n## Migration from the Prototype\n\nThe January 2026 prototype assumed a skill could expose its own process tree as the public source of truth. The current guidance is:\n\n1. Point public documentation at `library/` for built-in processes.\n2. Treat `plugins/babysitter-unified/skills/babysit/SKILL.md` as the skill entry point, not the process library root.\n3. Describe `.a5c/` paths only as project-local copies or overrides.\n4. Use `babysitter process-library:active --json` when you need to confirm the active bound library.\n\n---\n\n## Public References\n\nFor the current user-facing explanation of this model, see:\n\n- `docs/user-guide/features/process-library.md`\n- `docs/user-guide/features/process-definitions.md`\n- `docs/plugins.md`\n- `docs/reference/PROCESS_SELECTION.md`\n\n---\n\n## Historical Note\n\nThis file preserves the intent of the original implementation report while replacing prototype-only paths with the current public model. References to skill-internal process directories from the January prototype should now be read as historical context rather than current repository structure.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": [
    {
      "from": "page:docs-reference",
      "to": "page:docs-reference-process-packaging-implementation-2026-01-20",
      "kind": "contains_page"
    }
  ]
}