4.3 KiB
Compounding Engineering Plugin Development
Versioning Requirements
IMPORTANT: Routine PRs should not cut releases for this plugin.
The repo uses an automatied release process to prepare plugin releases, including version selection and changelog generation. Because multiple PRs may merge before the next release, contributors cannot know the final released version from within an individual PR.
Contributor Rules
- Do not manually bump
.claude-plugin/plugin.jsonversion in a normal feature PR. - Do not manually bump
.claude-plugin/marketplace.jsonplugin version in a normal feature PR. - Do not cut a release section in
CHANGELOG.mdfor a normal feature PR. - Do update substantive docs that are part of the actual change, such as
README.md, component tables, usage instructions, or counts when they would otherwise become inaccurate.
Pre-Commit Checklist
Before committing ANY changes:
- No manual release-version bump in
.claude-plugin/plugin.json - No manual release-version bump in
.claude-plugin/marketplace.json - No manual release entry added to
CHANGELOG.md - README.md component counts verified
- README.md tables accurate (agents, commands, skills)
- plugin.json description matches current counts
Directory Structure
agents/
├── review/ # Code review agents
├── research/ # Research and analysis agents
├── design/ # Design and UI agents
├── workflow/ # Workflow automation agents
└── docs/ # Documentation agents
skills/
├── ce-*/ # Core workflow skills (ce:plan, ce:review, etc.)
├── workflows-*/ # Deprecated aliases for ce:* skills
└── */ # All other skills
Note: Commands were migrated to skills in v2.39.0. All former
/command-nameslash commands now live underskills/command-name/SKILL.mdand work identically (Claude Code 2.1.3+ merged the two formats).
Command Naming Convention
Workflow commands use ce: prefix to unambiguously identify them as compound-engineering commands:
/ce:plan- Create implementation plans/ce:review- Run comprehensive code reviews/ce:work- Execute work items systematically/ce:compound- Document solved problems/ce:brainstorm- Explore requirements and approaches before planning
Why ce:? Claude Code has built-in /plan and /review commands. The ce: namespace (short for compound-engineering) makes it immediately clear these commands belong to this plugin. The legacy workflows: prefix is still supported as deprecated aliases that forward to the ce:* equivalents.
Skill Compliance Checklist
When adding or modifying skills, verify compliance with skill-creator spec:
YAML Frontmatter (Required)
name:present and matches directory name (lowercase-with-hyphens)description:present and describes what it does and when to use it (per official spec: "Explains code with diagrams. Use when exploring how code works.")
Reference Links (Required if references/ exists)
- All files in
references/are linked as[filename.md](./references/filename.md) - All files in
assets/are linked as[filename](./assets/filename) - All files in
scripts/are linked as[filename](./scripts/filename) - No bare backtick references like
`references/file.md`- use proper markdown links
Writing Style
- Use imperative/infinitive form (verb-first instructions)
- Avoid second person ("you should") - use objective language ("To accomplish X, do Y")
Cross-Platform User Interaction
- When a skill needs to ask the user a question, instruct use of the platform's blocking question tool and name the known equivalents (
AskUserQuestionin Claude Code,request_user_inputin Codex,ask_userin Gemini) - Include a fallback for environments without a question tool (e.g., present numbered options and wait for the user's reply before proceeding)
Quick Validation Command
# Check for unlinked references in a skill
grep -E '`(references|assets|scripts)/[^`]+`' skills/*/SKILL.md
# Should return nothing if all refs are properly linked
# Check description format - should describe what + when
grep -E '^description:' skills/*/SKILL.md
Documentation
See docs/solutions/plugin-versioning-requirements.md for detailed versioning workflow.