cc-sdd-new-agent

Adds or extends cc-sdd agent support via a standardized, plan-first SOP.

3.6k|274|Updated Jul 17, 2025
One-click install
npx skills add https://github.com/gotalab/cc-sdd --skill cc-sdd-new-agent
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cc-sdd-new-agent
Source: https://github.com/gotalab/cc-sdd/tree/main/.agents/skills/cc-sdd-new-agent
Command: npx skills add https://github.com/gotalab/cc-sdd --skill cc-sdd-new-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamline the process of adding or extending coding-agent support in cc-sdd by enforcing a standardized, end-to-end SOP that covers research, planning, implementation, and verification.

Core Features & Use Cases

  • Plans-first workflow: creates a comprehensive agent plan before code changes.
  • End-to-end artifacts: ensures deliverables like plan documents, manifests, and real manifest tests exist.
  • Migration readiness: supports additive migration paths and rollback considerations for existing integrations.

Quick Start

Begin by researching the target agent per docs/cc-sdd/sop-new-agent.md and drafting the agent plan before implementation.

Frequently Asked Questions about cc-sdd-new-agent

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I integrate a new coding agent into cc-sdd?

To integrate a new coding agent into cc-sdd, follow a standardized SOP that enforces a plan-first workflow, creating comprehensive agent plans and manifests before writing any implementation code.

What is the standard workflow for cc-sdd agent migration?

The cc-sdd agent migration workflow requires researching the target agent, drafting a comprehensive implementation plan, and generating end-to-end artifacts like manifests and real-manifest tests to ensure compatibility and rollback readiness.

Do I need to create an agent plan before extending coding-agent support?

Yes, extending coding-agent support requires a plans-first approach where you draft a comprehensive agent plan document before making any code changes to ensure standardized integration.

What artifacts are required when adding agent support to cc-sdd?

Required artifacts for adding cc-sdd agent support include comprehensive plan documents, integration manifests, and real-manifest tests to verify compatibility and enable additive migration paths.

How do I ensure rollback readiness during an agent integration?

To ensure rollback readiness during an agent integration, the SOP enforces generating real-manifest tests and supporting additive migration paths, allowing you to safely revert or extend existing integrations.

When should I use an SOP-driven approach for agent integration?

You should use an SOP-driven approach for agent integration when you need to standardize research, planning, implementation, and verification across new or existing migrations within the cc-sdd ecosystem.