Опишете задачата
Към всички skills

cc-sdd-new-agent

gotalab · Бази данни

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.

Оригинален текст · няма потвърден превод на български
Платформи: ClaudeНиво: СредноВ индекса: 11.06.2026 г.Обновен в GitHub: 20.05.2026 г.

Теми: agent-skills · claude-code · codex · cursor · gemini-cli · github-copilot · kiro · opencode · sdd · spec-driven-development · steering · subagents

Първо прочетете инструкцията.

Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.

Оригинален SKILL.md
GitHub хранилище
Звезди на репото
3677
Лиценз
MIT
Последна проверка на записа
22.09.2026 г.

Добавете в своя инструмент.

Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.

npx skills add gotalab/cc-sdd

Страницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.

Откъс от SKILL.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.

Целият SKILL.md в GitHub