* feat(commands): add /compound-engineering-setup for configurable agents Adds a new setup command that allows users to configure which review agents to use instead of hardcoding them in workflows. This enables: - Multi-step onboarding with AskUserQuestion for easy setup - Auto-detection of project type (Rails, Python, TypeScript, etc.) - Three setup modes: Quick (smart defaults), Advanced, and Minimal - Configuration stored in .claude/compound-engineering.json - Support for both global (~/.claude/) and project-specific config Updated workflows to read from config: - /workflows:review - reads reviewAgents from config - /plan_review - reads planReviewAgents from config - /workflows:work - references config for reviewer agents - /workflows:compound - references config for specialized agents 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat: auto-trigger setup when no config exists Workflows now detect missing config and offer inline quick setup: - "Quick Setup" - auto-detect project type, create config, continue - "Full Setup" - run /compound-engineering-setup for customization - "Skip" - use defaults just this once This ensures users get onboarded automatically when running any workflow for the first time, without needing to know about the setup command beforehand. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * feat(review): wire all conditionalAgents categories Extended /workflows:review to invoke conditional agents for: - migrations (existing) - frontend (new): JS/TS/Stimulus changes - architecture (new): structural changes, 10+ files - data (new): model/ActiveRecord changes Each category reads from conditionalAgents.* config key and runs appropriate specialized agents when file patterns match. Resolves: todos/001-ready-p2-conditional-agents-not-invoked.md Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: mark todo #001 as complete * feat(setup): add custom agent discovery and modify flow - Auto-detect custom agents in .claude/agents/ and ~/.claude/agents/ - Add modify existing config flow (add/remove agents, view config) - Include guide for creating custom review agents - Add customAgents mapping in config to track agent file paths - Update changelog with new config schema including customAgents Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * chore: remove completed todos directory Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * [2.29.1] Improve /workflows:brainstorm question flow - Add "Ask more questions" option at handoff phase - Clarify that Claude should ask the user questions (not wait for user) - Require resolving ALL open questions before offering to proceed Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com> * Simplify plugin settings: replace 486-line wizard with .local.md pattern - Rewrite setup.md (486 → 95 lines): detect project type, create .claude/compound-engineering.local.md with smart defaults - Make review.md and work.md config-aware: read agents from .local.md frontmatter, fall back to auto-detected defaults - Wire schema-drift-detector into review.md migrations conditional block - Delete technical_review.md (duplicated /plan_review) - Add disable-model-invocation to setup.md - Bump to v2.32.0 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Rewrite .claude/ paths for OpenCode/Codex targets, add npm publish workflow - Converters now rewrite .claude/ → .opencode/ (OpenCode) and .codex/ (Codex) in command bodies and agent bodies so .local.md settings work cross-platform - Apply transformContentForCodex to agent bodies (was only commands before) - Add GitHub Action to auto-publish to npm on version bump merge to main - Bump to v0.4.0 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * feat(workflows-work): require post-deploy monitoring section Add a mandatory Post-Deploy Monitoring & Validation section to the /workflows:work PR template, include no-impact fallback guidance, and enforce it in the quality checklist. * Add learnings-researcher to review workflow, fix docs site counts - Add learnings-researcher as parallel agent #14 in /workflows:review so past solutions from docs/solutions/ are surfaced during code review - Make /release-docs command invocable (remove disable-model-invocation) - Fix stale counts across docs site (agents 28→29, commands 19→24, skills 15→18, MCP servers 2→1) - Bump version to 2.32.1 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Move /release-docs to local .claude/commands/, bump to 2.32.2 Repo maintenance command doesn't need to be distributed to plugin users. Update command count 24 → 23 across plugin.json, marketplace.json, and docs. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Move settings to project root: compound-engineering.local.md Tool-agnostic location — works for Claude, Codex, OpenCode without path rewriting. No global fallback, just project root. Update commands (setup, review, work) and converter tests. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Make /compound-engineering-setup interactive with auto-detect fast path Two paths: "Auto-configure" (one click, smart defaults) or "Customize" (pick stack, focus areas, review depth). Uses AskUserQuestion throughout. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Replace /compound-engineering-setup command with setup skill Setup is now a skill invoked on-demand when compound-engineering.local.md doesn't exist. Review and work commands just say "invoke the setup skill" instead of inlining the full setup flow. - Remove commands/setup.md (command) - Add skills/setup/SKILL.md (skill with interactive AskUserQuestion flow) - Simplify review.md and work.md to reference the skill - Counts: 29 agents, 22 commands, 19 skills Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * Prepare v2.33.0 release: setup skill, configurable review agents - Bump version to 2.33.0 - Consolidate CHANGELOG entries for this branch - Fix README: update counts (29/22/19), add setup + resolve-pr-parallel skills - Remove stale /compound-engineering-setup command reference Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
212 lines
6.0 KiB
Markdown
212 lines
6.0 KiB
Markdown
---
|
|
name: release-docs
|
|
description: Build and update the documentation site with current plugin components
|
|
argument-hint: "[optional: --dry-run to preview changes without writing]"
|
|
---
|
|
|
|
# Release Documentation Command
|
|
|
|
You are a documentation generator for the compound-engineering plugin. Your job is to ensure the documentation site at `plugins/compound-engineering/docs/` is always up-to-date with the actual plugin components.
|
|
|
|
## Overview
|
|
|
|
The documentation site is a static HTML/CSS/JS site based on the Evil Martians LaunchKit template. It needs to be regenerated whenever:
|
|
|
|
- Agents are added, removed, or modified
|
|
- Commands are added, removed, or modified
|
|
- Skills are added, removed, or modified
|
|
- MCP servers are added, removed, or modified
|
|
|
|
## Step 1: Inventory Current Components
|
|
|
|
First, count and list all current components:
|
|
|
|
```bash
|
|
# Count agents
|
|
ls plugins/compound-engineering/agents/*.md | wc -l
|
|
|
|
# Count commands
|
|
ls plugins/compound-engineering/commands/*.md | wc -l
|
|
|
|
# Count skills
|
|
ls -d plugins/compound-engineering/skills/*/ 2>/dev/null | wc -l
|
|
|
|
# Count MCP servers
|
|
ls -d plugins/compound-engineering/mcp-servers/*/ 2>/dev/null | wc -l
|
|
```
|
|
|
|
Read all component files to get their metadata:
|
|
|
|
### Agents
|
|
For each agent file in `plugins/compound-engineering/agents/*.md`:
|
|
- Extract the frontmatter (name, description)
|
|
- Note the category (Review, Research, Workflow, Design, Docs)
|
|
- Get key responsibilities from the content
|
|
|
|
### Commands
|
|
For each command file in `plugins/compound-engineering/commands/*.md`:
|
|
- Extract the frontmatter (name, description, argument-hint)
|
|
- Categorize as Workflow or Utility command
|
|
|
|
### Skills
|
|
For each skill directory in `plugins/compound-engineering/skills/*/`:
|
|
- Read the SKILL.md file for frontmatter (name, description)
|
|
- Note any scripts or supporting files
|
|
|
|
### MCP Servers
|
|
For each MCP server in `plugins/compound-engineering/mcp-servers/*/`:
|
|
- Read the configuration and README
|
|
- List the tools provided
|
|
|
|
## Step 2: Update Documentation Pages
|
|
|
|
### 2a. Update `docs/index.html`
|
|
|
|
Update the stats section with accurate counts:
|
|
```html
|
|
<div class="stats-grid">
|
|
<div class="stat-card">
|
|
<span class="stat-number">[AGENT_COUNT]</span>
|
|
<span class="stat-label">Specialized Agents</span>
|
|
</div>
|
|
<!-- Update all stat cards -->
|
|
</div>
|
|
```
|
|
|
|
Ensure the component summary sections list key components accurately.
|
|
|
|
### 2b. Update `docs/pages/agents.html`
|
|
|
|
Regenerate the complete agents reference page:
|
|
- Group agents by category (Review, Research, Workflow, Design, Docs)
|
|
- Include for each agent:
|
|
- Name and description
|
|
- Key responsibilities (bullet list)
|
|
- Usage example: `claude agent [agent-name] "your message"`
|
|
- Use cases
|
|
|
|
### 2c. Update `docs/pages/commands.html`
|
|
|
|
Regenerate the complete commands reference page:
|
|
- Group commands by type (Workflow, Utility)
|
|
- Include for each command:
|
|
- Name and description
|
|
- Arguments (if any)
|
|
- Process/workflow steps
|
|
- Example usage
|
|
|
|
### 2d. Update `docs/pages/skills.html`
|
|
|
|
Regenerate the complete skills reference page:
|
|
- Group skills by category (Development Tools, Content & Workflow, Image Generation)
|
|
- Include for each skill:
|
|
- Name and description
|
|
- Usage: `claude skill [skill-name]`
|
|
- Features and capabilities
|
|
|
|
### 2e. Update `docs/pages/mcp-servers.html`
|
|
|
|
Regenerate the MCP servers reference page:
|
|
- For each server:
|
|
- Name and purpose
|
|
- Tools provided
|
|
- Configuration details
|
|
- Supported frameworks/services
|
|
|
|
## Step 3: Update Metadata Files
|
|
|
|
Ensure counts are consistent across:
|
|
|
|
1. **`plugins/compound-engineering/.claude-plugin/plugin.json`**
|
|
- Update `description` with correct counts
|
|
- Update `components` object with counts
|
|
- Update `agents`, `commands` arrays with current items
|
|
|
|
2. **`.claude-plugin/marketplace.json`**
|
|
- Update plugin `description` with correct counts
|
|
|
|
3. **`plugins/compound-engineering/README.md`**
|
|
- Update intro paragraph with counts
|
|
- Update component lists
|
|
|
|
## Step 4: Validate
|
|
|
|
Run validation checks:
|
|
|
|
```bash
|
|
# Validate JSON files
|
|
cat .claude-plugin/marketplace.json | jq .
|
|
cat plugins/compound-engineering/.claude-plugin/plugin.json | jq .
|
|
|
|
# Verify counts match
|
|
echo "Agents in files: $(ls plugins/compound-engineering/agents/*.md | wc -l)"
|
|
grep -o "[0-9]* specialized agents" plugins/compound-engineering/docs/index.html
|
|
|
|
echo "Commands in files: $(ls plugins/compound-engineering/commands/*.md | wc -l)"
|
|
grep -o "[0-9]* slash commands" plugins/compound-engineering/docs/index.html
|
|
```
|
|
|
|
## Step 5: Report Changes
|
|
|
|
Provide a summary of what was updated:
|
|
|
|
```
|
|
## Documentation Release Summary
|
|
|
|
### Component Counts
|
|
- Agents: X (previously Y)
|
|
- Commands: X (previously Y)
|
|
- Skills: X (previously Y)
|
|
- MCP Servers: X (previously Y)
|
|
|
|
### Files Updated
|
|
- docs/index.html - Updated stats and component summaries
|
|
- docs/pages/agents.html - Regenerated with X agents
|
|
- docs/pages/commands.html - Regenerated with X commands
|
|
- docs/pages/skills.html - Regenerated with X skills
|
|
- docs/pages/mcp-servers.html - Regenerated with X servers
|
|
- plugin.json - Updated counts and component lists
|
|
- marketplace.json - Updated description
|
|
- README.md - Updated component lists
|
|
|
|
### New Components Added
|
|
- [List any new agents/commands/skills]
|
|
|
|
### Components Removed
|
|
- [List any removed agents/commands/skills]
|
|
```
|
|
|
|
## Dry Run Mode
|
|
|
|
If `--dry-run` is specified:
|
|
- Perform all inventory and validation steps
|
|
- Report what WOULD be updated
|
|
- Do NOT write any files
|
|
- Show diff previews of proposed changes
|
|
|
|
## Error Handling
|
|
|
|
- If component files have invalid frontmatter, report the error and skip
|
|
- If JSON validation fails, report and abort
|
|
- Always maintain a valid state - don't partially update
|
|
|
|
## Post-Release
|
|
|
|
After successful release:
|
|
1. Suggest updating CHANGELOG.md with documentation changes
|
|
2. Remind to commit with message: `docs: Update documentation site to match plugin components`
|
|
3. Remind to push changes
|
|
|
|
## Usage Examples
|
|
|
|
```bash
|
|
# Full documentation release
|
|
claude /release-docs
|
|
|
|
# Preview changes without writing
|
|
claude /release-docs --dry-run
|
|
|
|
# After adding new agents
|
|
claude /release-docs
|
|
```
|