cc-sdd-new-agent
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 gotalab/cc-sdd --skill cc-sdd-new-agent --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 deliverabl
What does the cc-sdd-new-agent skill do?
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.
How do I install it?
Run `npx skills add gotalab/cc-sdd --skill cc-sdd-new-agent --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gotalab/cc-sdd, a repository with 3,599 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.