cc-sdd-new-agent
**cc-sdd-new-agent** executes a structured standard operating procedure for integrating new coding agents into the cc-sdd repository. Use this skill when adding a new agent, creating a subagent-capable variant, or migrating an existing agent to skills-based templates. The skill manages the full workflow from research and planning through implementation, requiring initial specification gathering, followed by Phase 1 research of official documentation, plan document creation, and then implementation using existing templates as patterns.
git clone --depth 1 https://github.com/gotalab/cc-sdd /tmp/cc-sdd-new-agent && cp -r /tmp/cc-sdd-new-agent/.agents/skills/cc-sdd-new-agent ~/.claude/skills/cc-sdd-new-agentSKILL.md
# CC-SDD New Agent Integration
## Goal
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.
## Default Operation Mode
Use `plan-first` as the default:
- First deliverable: `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
- Second deliverable (after plan approval): implementation changes in `tools/cc-sdd/...`
Do not skip the plan document unless the user explicitly requests direct implementation.
## Collect Inputs First
Collect the minimum inputs before editing files:
- Target agent display name and agent id (kebab-case)
- Official documentation URL for command/agent/skills format
- Integration scope: `commands-only`, `commands+agents`, or `skills`
- Whether work type is `new-agent` or `migration`
If any item is unclear, resolve it during Phase 1 research before creating implementation files.
## Execution Workflow
### 1) Run Phase 1 Research
Read `docs/cc-sdd/sop-new-agent.md` and extract all required spec details from official docs:
- commands directory
- agent directory (if supported)
- documentation filename
- command invocation format
- YAML frontmatter schema for commands and agents (or skills)
- placeholders/arguments format
Record exact values (not assumptions) in the plan document.
### 2) Create Plan Document
Copy and fill:
- `docs/cc-sdd/templates/agent-plan-template.md`
Include:
- Phase 1 research summary table
- Differences vs nearest existing agent pattern
- 5-step implementation plan
- changed-file list
- verification plan
Write the completed plan to:
- `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
Before implementation, ensure the plan explicitly states:
- integration scope (`commands-only`, `commands+agents`, `skills`)
- whether this is `new-agent` or `migration`
- compatibility impact and rollback approach
### 3) Choose Base Pattern and Implement
Pick the nearest existing implementation and copy from it:
- `commands-only`: start from `tools/cc-sdd/templates/agents/codex` or another commands-only agent
- `commands+agents`: start from `tools/cc-sdd/templates/agents/claude-code-agent` or `tools/cc-sdd/templates/agents/opencode-agent`
- `skills`: start from `tools/cc-sdd/templates/agents/claude-code-skills`
Start implementation only after the plan file exists and the user has confirmed to proceed.
Apply the standard 5 implementation steps from SOP:
1. Update `tools/cc-sdd/src/agents/registry.ts`
2. Add `tools/cc-sdd/templates/manifests/{agent-id}.json`
3. Add `tools/cc-sdd/templates/agents/{agent-id}/...`
4. Convert YAML frontmatter to target-agent format (keep body unless incompatibility is confirmed)
5. Add `tools/cc-sdd/test/realManifest{AgentName}.test.ts`
For `skills` integration, generate `SKILL.md`-based command packages under `templates/agents/{agent-id}/skills/`.
### 4) Handle Migration Cases
If the request is migration (or migration may be needed), read `references/skills-migration.md` and decide strategy before editing:
- Recommended default: additive migration (`{agent-id}-skills` as a new option)
- Use in-place replacement only when explicitly requested
Always document compatibility impact and CLI flag impact in the plan.
### 5) Verify Before Reporting
Run verification in `tools/cc-sdd`:
- `npm test`
- `npm run build && node dist/index.js --agent {agent-id} --dry-run`
- local temp-directory apply test with `--overwrite=force`
- language checks (`--lang ja`, `--lang en`)
- generated file count checks
If tests cannot run, explicitly report which step is blocked and why.
## Completion Criteria
- Plan file exists at `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
- Registry entry exists and routes to the new manifest id
- Manifest artifacts match target integration scope
- Templates render to expected target directories
- Real manifest test exists and passes
- Dry-run output matches expected artifact plan
- Plan document is updated with research evidence and verification notes
## References
- SOP: `docs/cc-sdd/sop-new-agent.md`
- Plan template: `docs/cc-sdd/templates/agent-plan-template.md`
- Migration guide: `references/skills-migration.md`
- Plan checklist: `references/plan-output-checklist.md`Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.
Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.
Implement approved tasks using TDD with subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel sub-agent dispatch by dependency wave.
Create comprehensive technical design for a specification
Initialize a new specification with detailed project description
Quick spec generation with interactive or automatic mode