john/claude-engineering-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #22 from EveryInc/fix/flatten-workflow-commands

Browse Source 
docs: fix workflow command documentation to use correct syntax
This commit is contained in:
Kieran Klaassen
2025-11-26 21:08:39 -08:00
committed by GitHub
parent ff9fd7cb0f 4b2820bdce
commit 9341872823
12 changed files with 158 additions and 61 deletions
Download Patch File Download Diff File Expand all files Collapse all files

127
docs/index.html
View File

@@ -21,6 +21,106 @@
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.5.1/css/all.min.css" />
<link href="css/style.css" rel="stylesheet" type="text/css" />
<script src="js/main.js" type="text/javascript" defer></script>
<!-- Pillar styles (inline for reliability) -->
<style>
.philosophy-pillars {
display: grid;
grid-template-columns: 1fr;
gap: var(--space-xl);
margin-bottom: var(--space-xxl);
}
@media (min-width: 768px) {
.philosophy-pillars { grid-template-columns: repeat(2, 1fr); }
}
.pillar {
display: flex;
gap: var(--space-l);
padding: var(--space-xl);
background: var(--color-background);
border-radius: var(--radius-l);
border: 1.5px solid transparent;
background-image: linear-gradient(var(--color-background), var(--color-background)), linear-gradient(135deg, var(--color-accent-light), var(--color-border));
background-origin: border-box;
background-clip: padding-box, border-box;
transition: all 0.35s cubic-bezier(0.4, 0, 0.2, 1);
position: relative;
overflow: hidden;
box-shadow: 0 4px 12px rgba(0, 0, 0, 0.05);
}
.pillar:hover {
transform: translateY(-2px);
border-color: var(--color-accent);
box-shadow: 0 8px 24px rgba(129, 140, 248, 0.2);
}
.pillar-icon {
flex-shrink: 0;
width: 72px;
height: 72px;
display: flex;
align-items: center;
justify-content: center;
background: linear-gradient(135deg, var(--color-accent), var(--color-accent-hover));
border-radius: var(--radius-l);
font-size: 36px;
color: var(--color-on-accent);
box-shadow: 0 8px 20px rgba(129, 140, 248, 0.3);
transition: all 0.35s cubic-bezier(0.4, 0, 0.2, 1);
}
.pillar:hover .pillar-icon {
transform: scale(1.1);
box-shadow: 0 12px 30px rgba(129, 140, 248, 0.5);
}
.pillar-content h3 {
margin: 0 0 var(--space-xs) 0;
font-size: 28px;
font-weight: 700;
color: var(--color-text-primary);
letter-spacing: -0.02em;
}
.pillar-tagline {
margin: 0 0 var(--space-m) 0;
font-size: 16px;
background: linear-gradient(135deg, var(--color-accent), var(--color-accent-hover));
-webkit-background-clip: text;
-webkit-text-fill-color: transparent;
background-clip: text;
font-weight: 600;
font-style: italic;
}
.pillar-description {
margin: 0 0 var(--space-l) 0;
font-size: 15px;
color: var(--color-text-secondary);
line-height: 1.7;
}
.pillar-tools {
display: flex;
flex-wrap: wrap;
gap: var(--space-s);
}
.tool-tag {
font-family: var(--font-mono);
font-size: 11px;
padding: 6px 12px;
background-color: var(--color-surface-hover);
color: var(--color-text-secondary);
border-radius: var(--radius-s);
border: 1px solid var(--color-border);
transition: all 0.25s ease;
font-weight: 500;
}
.tool-tag:hover {
background: linear-gradient(135deg, var(--color-accent-lighter), var(--color-surface-hover));
border-color: var(--color-accent);
color: var(--color-accent);
}
@media (max-width: 767px) {
.pillar { flex-direction: column; text-align: center; }
.pillar-icon { margin: 0 auto; }
.pillar-tools { justify-content: center; }
}
</style>
</head>
<body>
@@ -37,9 +137,6 @@
<a href="#skills" class="nav-link">Skills</a>
<a href="#mcp-servers" class="nav-link">MCP Servers</a>
<a href="pages/getting-started.html" class="nav-link">Docs</a>
<div class="button-group stacked margin-top-l mobile-only">
<a href="#install" class="button primary">Install Plugin</a>
</div>
</nav>
<div class="button-group">
<a href="https://github.com/EveryInc/every-marketplace" class="button ghost compact hide-on-mobile">
@@ -127,7 +224,7 @@
<h3>Plan</h3>
<p class="pillar-tagline">Stop starting over from scratch</p>
<p class="pillar-description">
You know that moment when you open a ticket and think "how did we solve this last time?" The framework-docs-researcher already knows. The git-history-analyzer remembers what worked in March. Run <code>/workflows:plan</code> and three research agents work in parallel—one reading docs, one analyzing your repo's history, one finding community patterns. In 60 seconds, you have a plan built on institutional memory instead of starting cold.
You know that moment when you open a ticket and think "how did we solve this last time?" The framework-docs-researcher already knows. The git-history-analyzer remembers what worked in March. Run <code>/plan</code> and three research agents work in parallel—one reading docs, one analyzing your repo's history, one finding community patterns. In 60 seconds, you have a plan built on institutional memory instead of starting cold.
</p>
<div class="pillar-tools">
<span class="tool-tag">framework-docs-researcher</span>
@@ -144,11 +241,11 @@
<h3>Delegate</h3>
<p class="pillar-tagline">Work with experts who never forget</p>
<p class="pillar-description">
The <code>security-sentinel</code> has checked 10,000 PRs for SQL injection. The <code>kieran-rails-reviewer</code> never approves a controller with business logic. They don't get tired, don't skip Friday afternoon reviews, don't forget the conventions you agreed on in March. Run <code>/workflows:work</code> and watch your plan execute with quality gates that actually enforce your standards—every single time.
The <code>security-sentinel</code> has checked 10,000 PRs for SQL injection. The <code>kieran-rails-reviewer</code> never approves a controller with business logic. They don't get tired, don't skip Friday afternoon reviews, don't forget the conventions you agreed on in March. Run <code>/work</code> and watch your plan execute with quality gates that actually enforce your standards—every single time.
</p>
<div class="pillar-tools">
<span class="tool-tag">23 specialized agents</span>
<span class="tool-tag">/workflows:work</span>
<span class="tool-tag">/work</span>
<span class="tool-tag">dhh-ruby-style skill</span>
<span class="tool-tag">git-worktree skill</span>
</div>
@@ -161,7 +258,7 @@
<h3>Assess</h3>
<p class="pillar-tagline">Get twelve opinions without twelve meetings</p>
<p class="pillar-description">
Type <code>/workflows:review PR#123</code> and go get coffee. When you come back, you'll have a security audit (did you sanitize that user input?), performance analysis (N+1 spotted on line 47), architecture review (this breaks the pattern from v2.3), data integrity check (that migration will fail in production), and eight more specialized reviews. All running in parallel. All categorized by severity. All stored as actionable P1/P2/P3 todos you can knock out in order.
Type <code>/review PR#123</code> and go get coffee. When you come back, you'll have a security audit (did you sanitize that user input?), performance analysis (N+1 spotted on line 47), architecture review (this breaks the pattern from v2.3), data integrity check (that migration will fail in production), and eight more specialized reviews. All running in parallel. All categorized by severity. All stored as actionable P1/P2/P3 todos you can knock out in order.
</p>
<div class="pillar-tools">
<span class="tool-tag">security-sentinel</span>
@@ -178,10 +275,10 @@
<h3>Codify</h3>
<p class="pillar-tagline">Make sure you never solve the same bug twice</p>
<p class="pillar-description">
Remember that CORS issue you debugged for three hours last month? Neither do I. That's the problem. Run <code>/workflows:codify</code> right after you fix something and it captures the solution as searchable documentation with YAML frontmatter. Next time someone hits the same issue, they grep for "CORS production" and find your answer in five seconds instead of re-debugging for three hours. That's how you compound.
Remember that CORS issue you debugged for three hours last month? Neither do I. That's the problem. Run <code>/codify</code> right after you fix something and it captures the solution as searchable documentation with YAML frontmatter. Next time someone hits the same issue, they grep for "CORS production" and find your answer in five seconds instead of re-debugging for three hours. That's how you compound.
</p>
<div class="pillar-tools">
<span class="tool-tag">/workflows:codify</span>
<span class="tool-tag">/codify</span>
<span class="tool-tag">codify-docs skill</span>
<span class="tool-tag">file-todos skill</span>
</div>
@@ -429,7 +526,7 @@
<i class="fa-solid fa-terminal color-accent"></i> 18 Powerful Commands
</h2>
<p class="paragraph m secondary">
Slash commands that replace entire workflows. <code>/workflows:review</code> is your code review committee. <code>/workflows:plan</code> is your research team. <code>/triage</code> sorts 50 todos in the time it takes you to read five. Each one automates hours of work into a single line.
Slash commands that replace entire workflows. <code>/review</code> is your code review committee. <code>/plan</code> is your research team. <code>/triage</code> sorts 50 todos in the time it takes you to read five. Each one automates hours of work into a single line.
</p>
</div>
@@ -439,28 +536,28 @@
<div class="grid columns-2">
<div class="command-card">
<div class="command-header">
<code class="command-name">/workflows:plan</code>
<code class="command-name">/plan</code>
<span class="command-type-badge">core</span>
</div>
<p class="command-description">Create comprehensive implementation plans with research agents and stakeholder analysis.</p>
</div>
<div class="command-card">
<div class="command-header">
<code class="command-name">/workflows:review</code>
<code class="command-name">/review</code>
<span class="command-type-badge">core</span>
</div>
<p class="command-description">Run exhaustive code reviews using 12 or more parallel agents, ultra-thinking, and worktrees.</p>
</div>
<div class="command-card">
<div class="command-header">
<code class="command-name">/workflows:work</code>
<code class="command-name">/work</code>
<span class="command-type-badge">core</span>
</div>
<p class="command-description">Execute work items systematically with progress tracking and validation.</p>
</div>
<div class="command-card">
<div class="command-header">
<code class="command-name">/workflows:codify</code>
<code class="command-name">/codify</code>
<span class="command-type-badge">core</span>
</div>
<p class="command-description">Document solved problems for the knowledge base. Turn learnings into reusable patterns.</p>
@@ -798,7 +895,7 @@
<h3>Ship Faster</h3>
<div class="card-code-block">
<pre><code># Run a 12-agent code review
/workflows:review PR#123
/review PR#123
# Get a security audit
claude agent security-sentinel

2
docs/pages/changelog.html
View File

@@ -323,7 +323,7 @@
<li><code>/prime</code> - Prime/setup command</li>
<li><code>/create-agent-skill</code> - Create or edit Claude Code skills</li>
<li><code>/heal-skill</code> - Fix skill documentation issues</li>
<li><code>/workflows:codify</code> - Document solved problems for knowledge base</li>
<li><code>/codify</code> - Document solved problems for knowledge base</li>
</ul>
<h4>New Skills (10)</h4>

30
docs/pages/commands.html
View File

@@ -72,7 +72,7 @@
<article class="docs-article">
<h1><i class="fa-solid fa-terminal color-accent"></i> Command Reference</h1>
<p class="lead">
Here's the thing about slash commands: they're workflows you'd spend 20 minutes doing manually, compressed into one line. Type <code>/workflows:plan</code> and watch three agents launch in parallel to research your codebase while you grab coffee. That's the point—automation that actually saves time, not busywork dressed up as productivity.
Here's the thing about slash commands: they're workflows you'd spend 20 minutes doing manually, compressed into one line. Type <code>/plan</code> and watch three agents launch in parallel to research your codebase while you grab coffee. That's the point—automation that actually saves time, not busywork dressed up as productivity.
</p>
<!-- Workflow Commands -->
@@ -82,7 +82,7 @@
<div class="command-detail" id="workflows-plan">
<div class="command-detail-header">
<code class="command-detail-name">/workflows:plan</code>
<code class="command-detail-name">/plan</code>
</div>
<p class="command-detail-description">
You've got a feature request and a blank page. This command turns "we need OAuth" into a structured plan that actually tells you what to build—researched, reviewed, and ready to execute.
@@ -116,14 +116,14 @@
</div>
</div>
<div class="card-code-block">
<pre><code>/workflows:plan Add OAuth integration for third-party auth
/workflows:plan Fix N+1 query in user dashboard</code></pre>
<pre><code>/plan Add OAuth integration for third-party auth
/plan Fix N+1 query in user dashboard</code></pre>
</div>
</div>
<div class="command-detail" id="workflows-review">
<div class="command-detail-header">
<code class="command-detail-name">/workflows:review</code>
<code class="command-detail-name">/review</code>
</div>
<p class="command-detail-description">
Twelve specialized reviewers examine your PR in parallel—security, performance, architecture, patterns. It's like code review by committee, except the committee finishes in two minutes instead of two days.
@@ -154,16 +154,16 @@
</div>
</div>
<div class="card-code-block">
<pre><code>/workflows:review 42
/workflows:review https://github.com/owner/repo/pull/42
/workflows:review feature-branch-name
/workflows:review latest</code></pre>
<pre><code>/review 42
/review https://github.com/owner/repo/pull/42
/review feature-branch-name
/review latest</code></pre>
</div>
</div>
<div class="command-detail" id="workflows-work">
<div class="command-detail-header">
<code class="command-detail-name">/workflows:work</code>
<code class="command-detail-name">/work</code>
</div>
<p class="command-detail-description">
Point this at a plan file and watch it execute—reading requirements, setting up environment, running tests, creating commits, opening PRs. It's the "just build the thing" button you wish you always had.
@@ -203,14 +203,14 @@
</li>
</ol>
<div class="card-code-block">
<pre><code>/workflows:work plans/user-authentication.md
/workflows:work todos/042-ready-p1-performance-issue.md</code></pre>
<pre><code>/work plans/user-authentication.md
/work todos/042-ready-p1-performance-issue.md</code></pre>
</div>
</div>
<div class="command-detail" id="workflows-codify">
<div class="command-detail-header">
<code class="command-detail-name">/workflows:codify</code>
<code class="command-detail-name">/codify</code>
</div>
<p class="command-detail-description">
Just fixed a gnarly bug? This captures the solution before you forget it. Seven agents analyze what you did, why it worked, and how to prevent it next time. Your future self will thank you.
@@ -236,8 +236,8 @@
<h4>Auto-Triggers</h4>
<p>Phrases: "that worked", "it's fixed", "working now", "problem solved"</p>
<div class="card-code-block">
<pre><code>/workflows:codify
/workflows:codify N+1 query optimization</code></pre>
<pre><code>/codify
/codify N+1 query optimization</code></pre>
</div>
</div>
</section>

24
docs/pages/getting-started.html
View File

@@ -131,16 +131,16 @@
<p>Let's see what this thing can actually do. I'll show you three workflows you'll use constantly:</p>
<h3>Run a Code Review</h3>
<p>This is the big one. Type <code>/workflows:review</code> and watch it spawn 10+ specialized reviewers:</p>
<p>This is the big one. Type <code>/review</code> and watch it spawn 10+ specialized reviewers:</p>
<div class="card-code-block">
<pre><code># Review a PR by number
/workflows:review 123
/review 123
# Review the current branch
/workflows:review
/review
# Review a specific branch
/workflows:review feature/my-feature</code></pre>
/review feature/my-feature</code></pre>
</div>
<h3>Use a Specialized Agent</h3>
@@ -331,11 +331,11 @@ claude agent git-history-analyzer "Show changes to user model"</code></pre>
<h3>Running Commands</h3>
<div class="card-code-block">
<pre><code># Workflow commands (prefix: /workflows:)
/workflows:plan
/workflows:review 123
/workflows:work
/workflows:codify
<pre><code># Workflow commands
/plan
/review 123
/work
/codify
# Utility commands
/changelog
@@ -344,7 +344,7 @@ claude agent git-history-analyzer "Show changes to user model"</code></pre>
</div>
<h3>The Review Workflow</h3>
<p>Let me show you what happens when you run <code>/workflows:review</code>. Here's the sequence:</p>
<p>Let me show you what happens when you run <code>/review</code>. Here's the sequence:</p>
<ol>
<li><strong>Detection</strong> - Figures out what you want reviewed (PR number, branch name, or current changes)</li>
<li><strong>Isolation</strong> - Spins up a git worktree so the review doesn't mess with your working directory</li>
@@ -406,10 +406,10 @@ skill: gemini-imagegen
<h3>Basic Review</h3>
<div class="card-code-block">
<pre><code># Review a PR
/workflows:review 123
/review 123
# Review current branch
/workflows:review</code></pre>
/review</code></pre>
</div>
<h3>Understanding Findings</h3>

4
docs/pages/skills.html
View File

@@ -435,8 +435,8 @@ bash scripts/worktree-manager.sh cleanup</code></pre>
</div>
<h4>Integration</h4>
<ul>
<li>Works with <code>/workflows:review</code> for isolated PR analysis</li>
<li>Works with <code>/workflows:work</code> for parallel feature development</li>
<li>Works with <code>/review</code> for isolated PR analysis</li>
<li>Works with <code>/work</code> for parallel feature development</li>
</ul>
<h4>Requirements</h4>
<ul>

2
plans/landing-page-launchkit-refresh.md
View File

@@ -41,7 +41,7 @@ Review and enhance the `/docs/index.html` landing page using LaunchKit elements
**Potential Improvements:**
- Add `→` arrow to "Install Plugin" button
- Consider adding animated terminal GIF below buttons showing `/workflows:review` in action
- Consider adding animated terminal GIF below buttons showing `/review` in action
### 2. Stats Section (lines 81-104)

4
plugins/compounding-engineering/CHANGELOG.md
View File

@@ -100,7 +100,7 @@ Major reorganization consolidating agents, commands, and skills from multiple so
- `/prime` - Prime/setup command
- `/create-agent-skill` - Create or edit Claude Code skills
- `/heal-skill` - Fix skill documentation issues
- `/workflows:codify` - Document solved problems for knowledge base
- `/codify` - Document solved problems for knowledge base
**New Skills (10)**
- `andrew-kane-gem-writer` - Write Ruby gems following Andrew Kane's patterns
@@ -125,7 +125,7 @@ Major reorganization consolidating agents, commands, and skills from multiple so
**Commands Restructured**
- Workflow commands moved to `commands/workflows/` subdirectory
- `/plan`, `/review`, `/work` now accessed as `/workflows:plan`, `/workflows:review`, `/workflows:work`
- `/plan`, `/review`, `/work`, `/codify` accessible via short names (autocomplete) or full path
### Summary

2
plugins/compounding-engineering/CLAUDE.md
View File

@@ -35,7 +35,7 @@ agents/
└── docs/ # Documentation agents
commands/
├── workflows/ # Core workflow commands (/workflows:*)
├── workflows/ # Core workflow commands (/plan, /review, /work, /codify)
└── *.md # Utility commands
skills/

10
plugins/compounding-engineering/README.md
View File

@@ -67,14 +67,14 @@ Agents are organized into categories for easier discovery.
### Workflow Commands
Access via `/workflows:command`:
Core workflow commands (use the short form for autocomplete):
| Command | Description |
|---------|-------------|
| `/workflows:plan` | Create implementation plans |
| `/workflows:review` | Run comprehensive code reviews |
| `/workflows:work` | Execute work items systematically |
| `/workflows:codify` | Document solved problems for knowledge base |
| `/plan` | Create implementation plans |
| `/review` | Run comprehensive code reviews |
| `/work` | Execute work items systematically |
| `/codify` | Document solved problems for knowledge base |
### Utility Commands

2
plugins/compounding-engineering/commands/generate_command.md
View File

@@ -127,7 +127,7 @@ Implement #$ARGUMENTS following these steps:
## Creating the Command File
1. **Create the file** at `.claude/commands/[name].md` or `.claude/commands/workflows/[name].md`
1. **Create the file** at `.claude/commands/[name].md` (subdirectories like `workflows/` supported)
2. **Start with YAML frontmatter** (see section above)
3. **Structure the command** using the template above
4. **Test the command** by using it with appropriate arguments

2
plugins/compounding-engineering/skills/file-todos/SKILL.md
View File

@@ -184,7 +184,7 @@ Work logs serve as:
| Trigger | Flow | Tool |
|---------|------|------|
| Code review | `/workflows:review` → Findings → `/triage` → Todos | Review agent + skill |
| Code review | `/review` → Findings → `/triage` → Todos | Review agent + skill |
| PR comments | `/resolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |
| Code TODOs | `/resolve_todo_parallel` → Fixes + Complex todos | Agent + skill |
| Planning | Brainstorm → Create todo → Work → Complete | Skill |

10
plugins/compounding-engineering/skills/git-worktree/SKILL.md
View File

@@ -20,8 +20,8 @@ This skill provides a unified interface for managing Git worktrees across your d
Use this skill in these scenarios:
1. **Code Review (`/workflows:review`)**: If NOT already on the PR branch, offer worktree for isolated review
2. **Feature Work (`/workflows:work`)**: Always ask if user wants parallel worktree or live branch work
1. **Code Review (`/review`)**: If NOT already on the PR branch, offer worktree for isolated review
2. **Feature Work (`/work`)**: Always ask if user wants parallel worktree or live branch work
3. **Parallel Development**: When working on multiple features simultaneously
4. **Cleanup**: After completing work in a worktree
@@ -29,7 +29,7 @@ Use this skill in these scenarios:
### In Claude Code Workflows
The skill is automatically called from `/workflows:review` and `/workflows:work` commands:
The skill is automatically called from `/review` and `/work` commands:
```
# For review: offers worktree if not on PR branch
@@ -182,7 +182,7 @@ bash .claude/skills/git-worktree/scripts/worktree-manager.sh cleanup
## Integration with Workflows
### `/workflows:review`
### `/review`
Instead of always creating a worktree:
@@ -195,7 +195,7 @@ Instead of always creating a worktree:
- no → proceed with PR diff on current branch
```
### `/workflows:work`
### `/work`
Always offer choice: