* Update create-agent-skills to match 2026 official docs, add /triage-prs command
- Rewrite SKILL.md to document that commands and skills are now merged
- Add new frontmatter fields: disable-model-invocation, user-invocable, context, agent
- Add invocation control table and dynamic context injection docs
- Fix skill-structure.md: was incorrectly recommending XML tags over markdown headings
- Update official-spec.md with complete 2026 specification
- Add local /triage-prs command for PR triage workflow
- Add PR triage plan document
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* [2.31.0] Reduce context token usage by 79%, include recent community contributions
The plugin was consuming 316% of Claude Code's description character budget
(~50,500 chars vs 16,000 limit), causing components to be silently excluded.
Now at 65% (~10,400 chars) with all components visible.
Changes:
- Trim all 29 agent descriptions (move examples to body)
- Add disable-model-invocation to 18 manual commands
- Add disable-model-invocation to 6 manual skills
- Include recent community contributions in changelog
- Fix component counts (29 agents, 24 commands, 18 skills)
Contributors: @trevin, @terryli, @robertomello, @zacwilliams,
@aarnikoskela, @samxie, @davidalley
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Fix: keep disable-model-invocation off commands called by /lfg, rename xcode-test
- Remove disable-model-invocation from test-browser, feature-video,
resolve_todo_parallel — these are called programmatically by /lfg and /slfg
- Rename xcode-test to test-xcode to match test-browser naming convention
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* Fix: keep git-worktree skill auto-invocable (used by /workflows:work)
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* feat(converter): support disable-model-invocation frontmatter
Parse disable-model-invocation from command and skill frontmatter.
Commands/skills with this flag are excluded from OpenCode command maps
and Codex prompt/skill generation, matching Claude Code behavior where
these components are user-only invocable.
Bump converter version to 0.3.0.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
* fix: protect plan and solution files from review/resolve deletion
The review/resolve pipeline could flag docs/plans/*.md and
docs/solutions/*.md files for deletion, contradicting /workflows:work
which treats them as living documents.
Adds protection at three layers:
- review.md: Protected Artifacts section + synthesis filter
- code-simplicity-reviewer.md: YAGNI exception for pipeline artifacts
- resolve_todo_parallel.md: Safety check to skip/wont_fix such todos
Fixes#140
* fix: protect plan and solution files from review/resolve deletion
The review/resolve pipeline could flag docs/plans/*.md and
docs/solutions/*.md files for deletion, contradicting /workflows:work
which treats them as living documents.
Adds protection at four layers:
- review.md: Protected Artifacts section and synthesis filter
- code-simplicity-reviewer.md: YAGNI exception for pipeline artifacts
- resolve_todo_parallel.md: Skip and wont_fix todos targeting these paths
- git-history-analyzer.md: Note not to characterize them as unnecessary
Fixes#140
---------
Co-authored-by: Axl Ottle <axl@Axls-Virtual-Machine.local>
The plugin had hardcoded references to 'CORA' (Every's internal project)
throughout the documentation workflow, making it project-specific rather
than generic. This affected users trying to use the plugin on non-CORA
projects.
Changes:
- Replace 'cora-critical-patterns.md' with 'critical-patterns.md'
- Replace 'Which CORA module' with 'Which module or component'
- Replace 'CORA-Specific Resources' with 'Project-Specific Resources'
- Replace 'CORA-MODULES.md' with 'modules documentation'
- Replace 'CORA system' with 'System-wide' in templates
- Update cora-test-reviewer description to be generic
Files modified:
- learnings-researcher.md: Fixed critical patterns file reference
- compound-docs/SKILL.md: Removed module and filename hardcoding
- compound-docs/assets/*.md: Generalized template references
- workflows/compound.md: Changed 'CORA schema' to 'solution schema'
- workflows/work.md: Made test reviewer description generic
This makes the plugin truly project-agnostic as advertised.
* fix(compound-docs): correct severity enum in validation example
The example error message referenced [critical, moderate, minor] but
the yaml-schema.md defines severity as [critical, high, medium, low].
* refactor(agents): standardize search tool recommendations
- Update repo-research-analyst to recommend built-in Grep tool instead
of CLI rg (Grep uses ripgrep under the hood)
- Add TypeScript example for ast-grep alongside Ruby
- Update pattern-recognition-specialist to use built-in Grep tool
- Keep ast-grep for AST-based structural matching (language-specific)
* feat(agents): add learnings-researcher for institutional knowledge
Add new research agent that efficiently searches docs/solutions/ for
relevant past solutions before implementing features or fixing bugs.
Key features:
- Grep-first filtering strategy for efficiency with 100+ files
- Category-based narrowing to reduce search scope
- Parallel Grep calls with synonym support (OR patterns)
- Frontmatter-only reads before full document reads
- Always checks critical patterns file
- Uses haiku model for speed (structured task, recipe-based)
Integrates with /workflows:plan to run in parallel with
repo-research-analyst during local research phase.
Closes the loop on compound engineering: solutions documented via
/workflows:compound are now discoverable during planning.
Add deprecation/sunset checks to research agents before they recommend
external APIs, OAuth flows, or third-party services.
Changes:
- framework-docs-researcher: Added step 2 "Deprecation/Sunset Check"
and updated Quality Standards
- best-practices-researcher: Added Phase 1.5 "MANDATORY Deprecation Check"
This prevents wasted development time on deprecated APIs. For example,
Google Photos Library API scopes were deprecated in March 2025, and
without validation, developers can spend hours debugging OAuth errors
on dead APIs.
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
- Update "current year is 2025" to 2026 in 4 research agents
- Update year ranges to 2024-2026 for content searches in deepen-plan
and create-agent-skills workflows
- Change "currency" to "recency" for clarity in domain expertise skill
- Add Phase 1: Discover and read relevant SKILL.md files before going online
- Add skill mappings for common technologies (Rails, Frontend, AI, etc.)
- Only proceed to online research if skills don't provide enough coverage
- Prioritize skill-based guidance with clear source attribution
- Synthesize findings from skills + online sources
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
All 26 agents now use `model: inherit` so they match whatever model
the user has configured in their main conversation.
Only `lint` keeps `model: haiku` since it's a simple task.
Fixes#69
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
BREAKING: Plugin renamed from compounding-engineering to compound-engineering.
Users will need to reinstall with the new name:
claude /plugin install compound-engineering
Changes:
- Renamed plugin directory and all references
- Updated documentation counts (24 agents, 19 commands)
- Added julik-frontend-races-reviewer to docs
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
