Add or extend coding-agent support in cc-sdd by executing the SOP in docs/cc-sdd/sop-new-agent.md end-to-end. Use when introducing a new agent, adding a subagent-capable variant, or evaluating migration of an existing supported agent to skills-based templates.
npx skills add https://github.com/gotalab/cc-sdd --skill cc-sdd-new-agent
Add a production-ready agent integration to tools/cc-sdd with complete research, implementation, and verification artifacts.
Use the existing SOP and templates in this repository instead of inventing a new process.
Use plan-first as the default:
docs/cc-sdd/plans/agent-plan-{agent-id}.mdtools/cc-sdd/...Do not skip the plan document unless the user explicitly requests direct implementation.
Collect the minimum inputs before editing files:
commands-only, commands+agents, or skillsnew-agent or migrationIf any item is unclear, resolve it during Phase 1 research before creating implementation files.
Read docs/cc-sdd/sop-new-agent.md and extract all required spec details from official docs:
Record exact values (not assumptions) in the plan document.
Copy and fill:
docs/cc-sdd/templates/agent-plan-template.mdInclude:
Write the completed plan to:
docs/cc-sdd/plans/agent-plan-{agent-id}.mdBefore implementation, ensure the plan explicitly states:
commands-only, commands+agents, skills)new-agent or migrationPick the nearest existing implementation and copy from it:
commands-only: start from tools/cc-sdd/templates/agents/codex or another commands-only agentcommands+agents: start from tools/cc-sdd/templates/agents/claude-code-agent or tools/cc-sdd/templates/agents/opencode-agentskills: start from tools/cc-sdd/templates/agents/claude-code-skillsStart implementation only after the plan file exists and the user has confirmed to proceed.
Apply the standard 5 implementation steps from SOP:
tools/cc-sdd/src/agents/registry.tstools/cc-sdd/templates/manifests/{agent-id}.jsontools/cc-sdd/templates/agents/{agent-id}/...tools/cc-sdd/test/realManifest{AgentName}.test.tsFor skills integration, generate SKILL.md-based command packages under templates/agents/{agent-id}/skills/.
If the request is migration (or migration may be needed), read references/skills-migration.md and decide strategy before editing:
{agent-id}-skills as a new option)Always document compatibility impact and CLI flag impact in the plan.
Run verification in tools/cc-sdd:
npm testnpm run build && node dist/index.js --agent {agent-id} --dry-run--overwrite=force--lang ja, --lang en)If tests cannot run, explicitly report which step is blocked and why.
docs/cc-sdd/plans/agent-plan-{agent-id}.mddocs/cc-sdd/sop-new-agent.mddocs/cc-sdd/templates/agent-plan-template.mdreferences/skills-migration.mdreferences/plan-output-checklist.mdCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Replace with description of the skill and when Claude should use it.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Take gotalab/cc-sdd-new-agent from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.