II.
Page JSON
Structured · livepage:docs-reference-process-examples-with-agent-skill-invocation
Process Examples with Agent/Skill Invocation json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-reference-process-examples-with-agent-skill-invocation",
"_kind": "Page",
"_file": "wiki/docs/reference/process-examples-with-agent-skill-invocation.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/reference/PROCESS_EXAMPLES_WITH_AGENT_SKILL_INVOCATION.md",
"sourceKind": "repo-docs",
"title": "Process Examples with Agent/Skill Invocation",
"displayName": "Process Examples with Agent/Skill Invocation",
"slug": "docs/reference/process-examples-with-agent-skill-invocation",
"articlePath": "wiki/docs/reference/PROCESS_EXAMPLES_WITH_AGENT_SKILL_INVOCATION.md",
"article": "\n# Process Examples with Agent/Skill Invocation\n\n**Date:** 2026-01-20\n**Task:** Create advanced process example demonstrating agent and skill invocation, quality convergence, TDD, parallelization, and breakpoints\n**Status:** Historical note, updated for the current library layout\n\n---\n\n## Summary\n\nThe original January 2026 implementation report described a prototype where the advanced example lived inside a skill package. In the current repo, the public example process lives in the built-in library:\n\n- Process implementation: `library/tdd-quality-convergence.js`\n- Process documentation: `library/tdd-quality-convergence.md`\n- Example inputs: `library/examples/tdd-quality-convergence-example.json`\n- Babysitter skill instructions: `plugins/babysitter-unified/skills/babysit/SKILL.md`\n\nThe plugin skill does not ship a separate `process/` tree under `plugins/babysitter-unified/skills/babysit/`. The canonical process library is `library/`, and project-local `.a5c/processes/` copies are user-managed overrides or generated local assets.\n\n---\n\n## Current Example\n\nThe current advanced example is still the TDD quality convergence process. It demonstrates:\n\n1. Agent-based planning\n2. Test-Driven Development workflow\n3. Quality convergence with iterative feedback\n4. Parallel quality checks\n5. Human review gates\n6. Agent-based quality scoring\n7. Final verification and review\n\nSee:\n\n- `library/tdd-quality-convergence.js`\n- `library/tdd-quality-convergence.md`\n- `docs/user-guide/features/quality-convergence.md`\n- `docs/reference/PROCESS_SELECTION.md`\n\n---\n\n## Correct Task Patterns\n\n### Agent Tasks\n\nUse `kind: \"agent\"` with a structured `agent.prompt` payload and optional `outputSchema`.\n\n### Skill Tasks\n\nUse `kind: \"skill\"` with parameters in `skill.context`. Do not rely on a separate `args` field. Instructional guidance belongs inside `skill.context.instructions`.\n\n### Node Tasks\n\nUse `kind: \"node\"` with a real process or task entry point. In the current packaging model, those entry points come from `library/` or from explicit project-local `.a5c/` copies.\n\n---\n\n## Current Usage\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\nIf a project has copied or customized the process locally, the equivalent entry may instead be under `.a5c/processes/`. That is a project-local asset, not the built-in library source of truth.\n\n---\n\n## Packaging Clarification\n\nThe current model separates responsibilities:\n\n- `library/` contains the built-in process library, examples, assets, methodologies, and specializations.\n- `plugins/babysitter-unified/skills/babysit/SKILL.md` provides the Babysitter skill instructions used by harnesses.\n- `.a5c/processes/`, `.a5c/skills/`, and `.a5c/agents/` are project-local copies or overrides when users install, generate, or customize assets locally.\n\nFor a broader explanation of that lookup and packaging model, see `docs/user-guide/features/process-library.md`.\n\n---\n\n## Historical Note\n\nThis document originally referenced prototype paths inside a skill package. Those paths were valid for an earlier packaging experiment but are not part of the current public repository layout. Public docs should use `library/` for built-in processes and describe `.a5c/` paths only as project-local copies.\n",
"documents": []
},
"outgoingEdges": [],
"incomingEdges": []
}