-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathagent-plugins.sdd
More file actions
57 lines (52 loc) · 3.64 KB
/
agent-plugins.sdd
File metadata and controls
57 lines (52 loc) · 3.64 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
Spec: SpecDD Agent Plugins Repository
Purpose:
Provide reusable SpecDD-guided agent skills from one source tree.
Build product-specific plugin repositories for supported agent targets from shared sources.
Build an Agent Skills standard distribution from the same shared skill sources.
Help agents work inside SpecDD projects by following each project's local SpecDD bootstrap chain.
Structure:
./.gitmodules: Submodule mapping for generated output repositories.
./plugins/codex: Codex plugin output submodule.
./plugins/claude: Claude plugin output submodule.
./plugins/copilot: GitHub Copilot plugin output submodule.
./plugins/junie: Junie plugin output submodule.
./plugins/cline: Cline plugin output submodule.
./plugins/antigravity: Antigravity plugin output submodule.
./plugins/agentskills: Agent Skills standard distribution output submodule.
./Makefile: Build entry points for generated outputs.
./package.json: Yarn project metadata and build scripts.
./plugin-versions.json: Generated target version map used during build.
./yarn.lock: Locked Node dependencies for reproducible builds.
./src/**: Source templates, shared files, generated package templates, fragments, and build scripts.
./CHANGELOG.md: Common Changelog release history for this repository.
./README.md: Repository and build documentation.
./DEVELOPMENT.md: Contributor workflow and release documentation.
Can modify:
./**
Must:
Act as an agent behavior layer for SpecDD projects.
Support Codex, Claude Code, GitHub Copilot, Junie, Cline, Antigravity, and Agent Skills generated targets.
Publish generated plugin repositories and the Agent Skills standard distribution from `./plugins/*` submodules.
Keep generated metadata aligned with the GitHub repositories and SpecDD publisher identity.
Keep generated target versions in `./plugin-versions.json`.
Keep `./CHANGELOG.md` formatted according to Common Changelog when updating release history.
Treat `./src/skills`, `./src/fragments`, `./src/shared`, and `./src/plugins` as the source of truth for generated output.
Generate output submodule contents from source templates with `make build` or `yarn build`.
Provide Makefile targets for initializing, releasing, and resetting generated output submodules.
Provide Makefile targets for validating built outputs with target-specific validators.
Keep configured generated output submodules committed and matching the build output.
Keep skill instructions concise, reusable, and directed at each target project's active SpecDD bootstrap chain.
Keep every skill frontmatter `description` optimized for agent discovery by clearly stating what the skill does, when it should trigger, common target artifacts, and important boundaries before the skill body is loaded.
Use and enforce the use of the target project's `.specdd/bootstrap.md` as the primary source of SpecDD rules.
Use target project and local bootstrap files when they exist.
Make the target project's active bootstrap chain authoritative for spec discovery, write authority, stop conditions, checks, and reporting expectations.
Treat target project specs as source-adjacent contracts under the active bootstrap rules.
Must not:
Replace the `specdd` CLI.
Install or update SpecDD framework files.
Embed a static copy of SpecDD framework rules as the plugin's own authority.
Use this repository's bootstrap files as authority for other SpecDD projects.
Override, loosen, or ignore a target project's active bootstrap chain.
Invent project-specific contracts.
Turn uncertain or accidental project behavior into a permanent contract.
Treat generated files in `./plugins/*` as the source of truth.