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