- Add design-conformance-reviewer agent for reviewing code against design docs
- Add weekly-shipped skill for stakeholder summaries from Jira/GitHub
- Fix component counts across marketplace.json, plugin.json, and README
- Add worktree constraints to ce-review and resolve_todo_parallel skills
- Fix typo in resolve_todo_parallel SKILL.md
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
New issue-intelligence-analyst agent that fetches GitHub issues via
gh CLI, clusters by root-cause themes, and returns structured analysis
with trend direction, confidence scores, and source mix. Designed for
both ce:ideate integration and standalone use.
Agent design:
- Priority-aware fetching with label scanning for focus targeting
- Truncated bodies (500 chars) in initial fetch to avoid N+1 calls
- Single gh call per fetch, no pipes or scripts (avoids permission spam)
- Built-in --jq for all field extraction and filtering
- Mandatory structured output with self-check checklist
- Accurate counts from actual data, not assumptions
- Closed issues as recurrence signal only, not standalone evidence
ce:ideate gains:
- Issue-tracker intent detection in Phase 0.2
- Conditional agent dispatch in Phase 1 (parallel with existing scans)
- Dynamic frame derivation from issue clusters in Phase 2
- Hybrid strategy: cluster-derived frames + default padding when < 4
- Resume awareness distinguishing issue vs non-issue ideation
- Numbered table format for rejection summary in ideation artifacts
Research agents (repo-research-analyst, git-history-analyzer,
best-practices-researcher, framework-docs-researcher) were using
shell commands like find, rg, cat, and chained pipelines for routine
codebase exploration. This triggers permission prompts in Claude Code
and degrades the user experience when these agents run as sub-agents.
Updated all research agents with platform-agnostic tool selection
guidance that prefers native file-search/glob, content-search/grep,
and file-read tools over shell equivalents. Shell is now reserved for
commands with no native equivalent (ast-grep, bundle show, git).
Git-history-analyzer additionally limits shell to one simple git
command per call with no chaining or piping.
Added tool selection rules to AGENTS.md so future agents follow
the same pattern by default.
Incorporates 163 upstream commits (origin/main) while preserving all
local skills, agents, and commands. Metadata descriptions updated to
reflect actual component counts (30 agents, 56 skills, 7 commands).
file-todos/SKILL.md merged with both upstream command rename and local
assessment fields.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The every-style-editor agent file was a duplicate of the existing
every-style-editor skill. Agent files are eagerly loaded into the
Task tool definition on every API call (~100-200 tokens each),
while skills are lazy-loaded only when invoked. Removing the
duplicate saves tokens and eliminates potential runtime errors
when the agent is invoked via Task tool instead of Skill tool.
Changes:
- Delete agents/workflow/every-style-editor.md (skill version
in skills/every-style-editor/ already exists)
- Update README.md workflow agent count from 5 to 4
- Update plugin.json agent counts from 29 to 28
Fixes#156
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
* 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>
- New agent: schema-drift-detector for catching unrelated schema.rb changes in PRs
- Compares schema.rb diff against migrations in the PR
- Detects columns, indexes, tables from other branches
- Provides clear fix instructions
- Essential pre-merge check for database changes
Also updates component counts in README (were outdated)
Co-Authored-By: Claude Opus 4.5 <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
Skills are auto-loaded in context, no need to manually cat files.
Simplified Step 0 to just reference loaded skill context.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Added "Step 0: Discover and Load Design Skills (MANDATORY)"
- Discovers skills from all locations (plugin, global, project)
- Maps user context to relevant skills (Swiss → swiss-design, etc.)
- Changed iteration approach: ONE change per iteration, not 3-5
- Updated output format: focus on single most impactful change
- Added rule: "If you can't identify ONE clear improvement, stop"
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- 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>
- Remove Playwright MCP server from plugin
- Add new agent-browser skill for CLI-based browser automation
- Rename /playwright-test to /test-browser command
- Update all commands and agents to use agent-browser CLI
- Update README and plugin.json
agent-browser is Vercel's headless browser CLI designed for AI agents.
It uses ref-based selection (@e1, @e2) from accessibility snapshots
and provides a simpler CLI interface compared to MCP tools.
Key benefits:
- No MCP server required
- Simpler Bash-based workflow
- Same ref-based element selection
- Better for quick automation tasks
🤖 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>
* [2.17.0] Expand agent-native skill with mobile app learnings
Major expansion of agent-native-architecture skill based on real-world
learnings from building the Every Reader iOS app.
New reference documents:
- dynamic-context-injection.md: Runtime app state in system prompts
- action-parity-discipline.md: Ensuring agents can do what users can
- shared-workspace-architecture.md: Agents and users in same data space
- agent-native-testing.md: Testing patterns for agent-native apps
- mobile-patterns.md: Background execution, permissions, cost awareness
Updated references:
- architecture-patterns.md: Added Unified Agent Architecture, Agent-to-UI
Communication, and Model Tier Selection patterns
Enhanced agent-native-reviewer with comprehensive review process covering
all new patterns, including mobile-specific verification.
Key insight: "The agent should be able to do anything the user can do,
through tools that mirror UI capabilities, with full context about the
app state."
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
* [2.18.0] Add Dynamic Capability Discovery and iCloud sync patterns
New patterns in agent-native-architecture skill:
- **Dynamic Capability Discovery** - For agent-native apps integrating with
external APIs (HealthKit, HomeKit, GraphQL), use a discovery tool (list_*)
plus a generic access tool instead of individual tools per endpoint.
(Note: Static mapping is fine for constrained agents with limited scope.)
- **CRUD Completeness** - Every entity needs create, read, update, AND delete.
- **iCloud File Storage** - Use iCloud Documents for shared workspace to get
free, automatic multi-device sync without building a sync layer.
- **Architecture Review Checklist** - Pushes reviewer findings earlier into
design phase. Covers tool design, action parity, UI integration, context.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
---------
Co-authored-by: Claude <noreply@anthropic.com>
New review agents for validating database migrations and risky data deployments:
- data-migration-expert: Validates ID mappings match production reality, checks
for swapped values, verifies rollback safety, provides SQL verification snippets
- deployment-verification-agent: Produces Go/No-Go deployment checklists with
pre/post-deploy SQL queries, data invariants, rollback procedures, monitoring
Updated /workflows:review to conditionally run these agents when PRs contain
database migrations (db/migrate/*.rb), data backfills, or ID/enum mappings.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add agent-native-reviewer agent to verify features are agent-accessible
- Add agent-native-architecture skill for prompt-native design patterns
- Add agent-native-reviewer to /review command parallel agents
- Move agent-native skill to correct plugin folder
- Update component counts (25 agents, 12 skills)
- Include mermaid dark mode fix from PR #45🤖 Generated with [Claude Code](https://claude.com/claude-code)
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>
