Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,11 +34,12 @@ Codex output is written to `~/.codex/prompts` and `~/.codex/skills`, with each C
## Workflow

```
Plan → Work → Review → Compound → Repeat
Brainstorm → Plan → Work → Review → Compound → Repeat
```

| Command | Purpose |
|---------|---------|
| `/workflows:brainstorm` | Explore requirements and approaches through collaborative dialogue |
| `/workflows:plan` | Turn feature ideas into detailed implementation plans |
| `/workflows:work` | Execute plans with worktrees and task tracking |
| `/workflows:review` | Multi-agent code review before merging |
Expand Down
26 changes: 22 additions & 4 deletions plugins/compound-engineering/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,27 @@ AI-powered development tools that get smarter with every use. Make each unit of

| Component | Count |
|-----------|-------|
| Agents | 27 |
| Commands | 20 |
| Skills | 14 |
| Agents | 28 |
| Commands | 24 |
| Skills | 15 |
| MCP Servers | 1 |

## The Workflow

The core workflow commands form a connected development cycle:

```
Brainstorm → Plan → Work → Review → Compound → Repeat
```

| Phase | Command | Purpose |
|-------|---------|---------|
| **Brainstorm** | `/workflows:brainstorm` | Clarify WHAT to build. Explore requirements, compare approaches, document decisions. |
| **Plan** | `/workflows:plan` | Design HOW to build it. Create implementation steps, identify files, define verification. |
| **Work** | `/workflows:work` | Execute the plan. Follow steps systematically, verify each change. |
| **Review** | `/workflows:review` | Multi-agent code review. Catch issues from multiple perspectives before merging. |
| **Compound** | `/workflows:compound` | Document learnings. Capture solved problems so future work is easier. |

## Agents

Agents are organized into categories for easier discovery.
Expand All @@ -34,13 +50,14 @@ Agents are organized into categories for easier discovery.
| `security-sentinel` | Security audits and vulnerability assessments |
| `julik-frontend-races-reviewer` | Review JavaScript/Stimulus code for race conditions |

### Research (4)
### Research (5)

| Agent | Description |
|-------|-------------|
| `best-practices-researcher` | Gather external best practices and examples |
| `framework-docs-researcher` | Research framework documentation and best practices |
| `git-history-analyzer` | Analyze git history and code evolution |
| `learnings-researcher` | Search institutional learnings for past solutions and patterns |
| `repo-research-analyst` | Research repository structure and conventions |

### Design (3)
Expand Down Expand Up @@ -125,6 +142,7 @@ Core workflow commands use `workflows:` prefix to avoid collisions with built-in

| Skill | Description |
|-------|-------------|
| `brainstorming` | Explore requirements and approaches before planning implementation |
| `every-style-editor` | Review copy for Every's style guide compliance |
| `file-todos` | File-based todo tracking system |
| `git-worktree` | Manage Git worktrees for parallel development |
Expand Down