mcpbeat Sign in

Cc Sdd New Agent Agent Skill

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.

2k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
3599
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/gotalab/cc-sdd --skill cc-sdd-new-agent

The instruction itself

12 sections, as written by the author

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:

  • Update tools/cc-sdd/src/agents/registry.ts
  • Add tools/cc-sdd/templates/manifests/{agent-id}.json
  • Add tools/cc-sdd/templates/agents/{agent-id}/...
  • Convert YAML frontmatter to target-agent format (keep body unless incompatibility is confirmed)
  • 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

Other skills for the same job

different authors, same section of the catalogue
Skill Creator
by anthropics
vendor ×10

Create 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.

56k tokens scripts
Skill Creator
by vercel-labs
vendor ×10

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.

12k tokens scripts
Skill Creator
by JayZeeDesign
×9

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.

10k tokens scripts
Template Skill
by JayZeeDesign
×7

Replace with description of the skill and when Claude should use it.

35 tokens
Dispatching Parallel Agents
by ZhanlinCui
×5

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

2k tokens
Skill Development
by anthropics
vendor ×4

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.

9k tokens
Find Skills
by sanity-io
vendor ×4

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.

1k tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts

How to use it

Copy the folder

Take gotalab/cc-sdd-new-agent from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

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.