cc-sdd-new-agent

Name: cc-sdd-new-agent
Author: gotalab

3.6kstars271forks

How to install cc-sdd-new-agent?

gotalab/cc-sdd/cc-sdd-new-agent

$npx -y skills add gotalab/cc-sdd --skill cc-sdd-new-agent

Installs into the current project.

Summary

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.

Files · 1

View on GitHub

SKILL.md

1	# CC-SDD New Agent Integration
2
3	## Goal
4
5	Add a production-ready agent integration to `tools/cc-sdd` with complete research, implementation, and verification artifacts.
6	Use the existing SOP and templates in this repository instead of inventing a new process.
7
8	## Default Operation Mode
9
10	Use `plan-first` as the default:
11	- First deliverable: `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
12	- Second deliverable (after plan approval): implementation changes in `tools/cc-sdd/...`
13
14	Do not skip the plan document unless the user explicitly requests direct implementation.
15
16	## Collect Inputs First
17
18	Collect the minimum inputs before editing files:
19	- Target agent display name and agent id (kebab-case)
20	- Official documentation URL for command/agent/skills format
21	- Integration scope: `commands-only`, `commands+agents`, or `skills`
22	- Whether work type is `new-agent` or `migration`
23
24	If any item is unclear, resolve it during Phase 1 research before creating implementation files.
25
26	## Execution Workflow
27
28	### 1) Run Phase 1 Research
29
30	Read `docs/cc-sdd/sop-new-agent.md` and extract all required spec details from official docs:
31	- commands directory
32	- agent directory (if supported)
33	- documentation filename
34	- command invocation format
35	- YAML frontmatter schema for commands and agents (or skills)
36	- placeholders/arguments format
37
38	Record exact values (not assumptions) in the plan document.
39
40	### 2) Create Plan Document
41
42	Copy and fill:
43	- `docs/cc-sdd/templates/agent-plan-template.md`
44
45	Include:
46	- Phase 1 research summary table
47	- Differences vs nearest existing agent pattern
48	- 5-step implementation plan
49	- changed-file list
50	- verification plan
51
52	Write the completed plan to:
53	- `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
54
55	Before implementation, ensure the plan explicitly states:
56	- integration scope (`commands-only`, `commands+agents`, `skills`)
57	- whether this is `new-agent` or `migration`
58	- compatibility impact and rollback approach
59
60	### 3) Choose Base Pattern and Implement
61
62	Pick the nearest existing implementation and copy from it:
63	- `commands-only`: start from `tools/cc-sdd/templates/agents/codex` or another commands-only agent
64	- `commands+agents`: start from `tools/cc-sdd/templates/agents/claude-code-agent` or `tools/cc-sdd/templates/agents/opencode-agent`
65	- `skills`: start from `tools/cc-sdd/templates/agents/claude-code-skills`
66
67	Start implementation only after the plan file exists and the user has confirmed to proceed.
68
69	Apply the standard 5 implementation steps from SOP:
70	1. Update `tools/cc-sdd/src/agents/registry.ts`
71	2. Add `tools/cc-sdd/templates/manifests/{agent-id}.json`
72	3. Add `tools/cc-sdd/templates/agents/{agent-id}/...`
73	4. Convert YAML frontmatter to target-agent format (keep body unless incompatibility is confirmed)
74	5. Add `tools/cc-sdd/test/realManifest{AgentName}.test.ts`
75
76	For `skills` integration, generate `SKILL.md`-based command packages under `templates/agents/{agent-id}/skills/`.
77
78	### 4) Handle Migration Cases
79
80	If the request is migration (or migration may be needed), read `references/skills-migration.md` and decide strategy before editing:
81	- Recommended default: additive migration (`{agent-id}-skills` as a new option)
82	- Use in-place replacement only when explicitly requested
83
84	Always document compatibility impact and CLI flag impact in the plan.
85
86	### 5) Verify Before Reporting
87
88	Run verification in `tools/cc-sdd`:
89	- `npm test`
90	- `npm run build && node dist/index.js --agent {agent-id} --dry-run`
91	- local temp-directory apply test with `--overwrite=force`
92	- language checks (`--lang ja`, `--lang en`)
93	- generated file count checks
94
95	If tests cannot run, explicitly report which step is blocked and why.
96
97	## Completion Criteria
98
99	- Plan file exists at `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
100	- Registry entry exists and routes to the new manifest id
101	- Manifest artifacts match target integration scope
102	- Templates render to expected target directories
103	- Real manifest test exists and passes
104	- Dry-run output matches expected artifact plan
105	- Plan document is updated with research evidence and verification notes
106
107	## References
108
109	- SOP: `docs/cc-sdd/sop-new-agent.md`
110	- Plan template: `docs/cc-sdd/templates/agent-plan-template.md`
111	- Migration guide: `references/skills-migration.md`
112	- Plan checklist: `references/plan-output-checklist.md`

People who liked this also viewed

6 picks

Type

cc-sdd-new-agent

3.6kstars271forks

View on GitHub

How to install cc-sdd-new-agent?

gotalab/cc-sdd/cc-sdd-new-agent

$npx -y skills add gotalab/cc-sdd --skill cc-sdd-new-agent

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# CC-SDD New Agent Integration
2
3	## Goal
4
5	Add a production-ready agent integration to `tools/cc-sdd` with complete research, implementation, and verification artifacts.
6	Use the existing SOP and templates in this repository instead of inventing a new process.
7
8	## Default Operation Mode
9
10	Use `plan-first` as the default:
11	- First deliverable: `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
12	- Second deliverable (after plan approval): implementation changes in `tools/cc-sdd/...`
13
14	Do not skip the plan document unless the user explicitly requests direct implementation.
15
16	## Collect Inputs First
17
18	Collect the minimum inputs before editing files:
19	- Target agent display name and agent id (kebab-case)
20	- Official documentation URL for command/agent/skills format
21	- Integration scope: `commands-only`, `commands+agents`, or `skills`
22	- Whether work type is `new-agent` or `migration`
23
24	If any item is unclear, resolve it during Phase 1 research before creating implementation files.
25
26	## Execution Workflow
27
28	### 1) Run Phase 1 Research
29
30	Read `docs/cc-sdd/sop-new-agent.md` and extract all required spec details from official docs:
31	- commands directory
32	- agent directory (if supported)
33	- documentation filename
34	- command invocation format
35	- YAML frontmatter schema for commands and agents (or skills)
36	- placeholders/arguments format
37
38	Record exact values (not assumptions) in the plan document.
39
40	### 2) Create Plan Document
41
42	Copy and fill:
43	- `docs/cc-sdd/templates/agent-plan-template.md`
44
45	Include:
46	- Phase 1 research summary table
47	- Differences vs nearest existing agent pattern
48	- 5-step implementation plan
49	- changed-file list
50	- verification plan
51
52	Write the completed plan to:
53	- `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
54
55	Before implementation, ensure the plan explicitly states:
56	- integration scope (`commands-only`, `commands+agents`, `skills`)
57	- whether this is `new-agent` or `migration`
58	- compatibility impact and rollback approach
59
60	### 3) Choose Base Pattern and Implement
61
62	Pick the nearest existing implementation and copy from it:
63	- `commands-only`: start from `tools/cc-sdd/templates/agents/codex` or another commands-only agent
64	- `commands+agents`: start from `tools/cc-sdd/templates/agents/claude-code-agent` or `tools/cc-sdd/templates/agents/opencode-agent`
65	- `skills`: start from `tools/cc-sdd/templates/agents/claude-code-skills`
66
67	Start implementation only after the plan file exists and the user has confirmed to proceed.
68
69	Apply the standard 5 implementation steps from SOP:
70	1. Update `tools/cc-sdd/src/agents/registry.ts`
71	2. Add `tools/cc-sdd/templates/manifests/{agent-id}.json`
72	3. Add `tools/cc-sdd/templates/agents/{agent-id}/...`
73	4. Convert YAML frontmatter to target-agent format (keep body unless incompatibility is confirmed)
74	5. Add `tools/cc-sdd/test/realManifest{AgentName}.test.ts`
75
76	For `skills` integration, generate `SKILL.md`-based command packages under `templates/agents/{agent-id}/skills/`.
77
78	### 4) Handle Migration Cases
79
80	If the request is migration (or migration may be needed), read `references/skills-migration.md` and decide strategy before editing:
81	- Recommended default: additive migration (`{agent-id}-skills` as a new option)
82	- Use in-place replacement only when explicitly requested
83
84	Always document compatibility impact and CLI flag impact in the plan.
85
86	### 5) Verify Before Reporting
87
88	Run verification in `tools/cc-sdd`:
89	- `npm test`
90	- `npm run build && node dist/index.js --agent {agent-id} --dry-run`
91	- local temp-directory apply test with `--overwrite=force`
92	- language checks (`--lang ja`, `--lang en`)
93	- generated file count checks
94
95	If tests cannot run, explicitly report which step is blocked and why.
96
97	## Completion Criteria
98
99	- Plan file exists at `docs/cc-sdd/plans/agent-plan-{agent-id}.md`
100	- Registry entry exists and routes to the new manifest id
101	- Manifest artifacts match target integration scope
102	- Templates render to expected target directories
103	- Real manifest test exists and passes
104	- Dry-run output matches expected artifact plan
105	- Plan document is updated with research evidence and verification notes
106
107	## References
108
109	- SOP: `docs/cc-sdd/sop-new-agent.md`
110	- Plan template: `docs/cc-sdd/templates/agent-plan-template.md`
111	- Migration guide: `references/skills-migration.md`
112	- Plan checklist: `references/plan-output-checklist.md`

People who liked this also viewed

6 picks

Type