ce-brainstorm
skillExplore requirements.
docs/skills/ce-brainstorm.md
Open component record →What EveryInc/compound-engineering-plugin is—in plain language
Engineering plugin whose core loop brainstorms, plans, works, simplifies, reviews, and stores solved-problem knowledge for future agent work.
Mental model: This repository provides a directly runnable command or package. You give the command an input, it performs the documented workflow, and it returns files, terminal output, a local interface, or a remote result.
Interfacesplugin, skills
Primary languageNone documented
Typical useRun deliberate feature/debug workflows and optionally /lfg through PR creation/CI watch while retaining human merge control.
Your first 15 minutes
- Complete the linked Installation Guide and its verification step.
- Create a disposable test folder or use non-sensitive sample data.
- Run the small example below and observe what files, ports, or prompts appear.
- Read the result before approving writes, network calls, account access, or costs.
- Only then repeat the workflow with a real project.
Starter workflow
open "https://github.com/EveryInc/compound-engineering-plugin#readme"Complete indexed functionality map
Each card below corresponds to a component identified in the repository research. Open a component record for its path, purpose, capabilities, dependencies, risks, and relationships.
ce-plan
skillCreate implementation plan.
docs/skills/ce-plan.md
Open component record →ce-work
skillExecute plan.
docs/skills/ce-work.md
Open component record →ce-simplify-code
skillRefine code before review.
docs/skills/ce-simplify-code.md
Open component record →ce-code-review
skillMulti-agent report-only review.
docs/skills/ce-code-review.md
Open component record →ce-compound
skillPersist solved-problem knowledge.
docs/skills/ce-compound.md
Open component record →/lfg
workflowBounded autonomous pipeline through PR/CI, no merge.
README.md
Open component record →Upstream feature-by-feature guide
These capabilities are derived from the current first-party README and supporting documentation. Names follow upstream terminology so you can search the source documentation precisely.
Upstream capability
Claude Code
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns claude code. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Cursor
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns cursor. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Grok Bot
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns grok bot. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Codex App
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns codex app. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Codex CLI
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns codex cli. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Philosophy
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns philosophy. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Workflow
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns workflow. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Additional skills
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns additional skills. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Quick Example
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns quick example. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Getting Started
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns getting started. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Full Skill Inventory
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns full skill inventory. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
Upstream capability
Kimi Code CLI
Upstream treats this as a distinct part of EveryInc/compound-engineering-plugin. In plain language, use this area when your task concerns kimi code cli. Begin with the documented default, test it on disposable input, and open the source section for its current options and limitations.
How to use the main workflows
Choose the smallest relevant function
Start with one capability card instead of asking the repository to do everything at once. This makes permissions, inputs, and output easier to understand.
Prepare a disposable input
Use a sample URL, copied repository, test document, or sandbox account. Keep production credentials and irreplaceable files out of the first run.
Run, observe, and stop
Watch Terminal output or the host application's activity view. If the behavior differs from the README, stop with Control + C or cancel inside the host before retrying.
Inspect the result
Check generated files, diffs, API responses, logs, or previews. Never assume “command finished” means the result is correct.
Save a repeatable recipe
Record the working command and non-secret configuration in your project's README. Store secrets in the documented environment file or password manager.
Copy-paste recipes from upstream documentation
These examples are selected from the repository's first-party documentation. Replace obvious placeholders, keep quotation marks intact, and run them only in the context indicated by the surrounding explanation.
Open the live upstream manual
open "https://github.com/EveryInc/compound-engineering-plugin#readme"Configuration, accounts, and files
Configuration files
None documented
A configuration file changes behavior without changing source code. Make one change at a time and keep a backup before editing JSON, TOML, YAML, or environment files.
Important directories
docs/skills/
Paths identify where the relevant implementation or generated files live. Paths beginning with ~ are inside your home folder.
Credentials
None documented
Prefer temporary, least-privileged credentials. Never commit .env, tokens, cookies, private keys, or session exports.
External services
None documented
Check pricing, data retention, rate limits, and account permissions before enabling optional integrations.
Safe operating habits
- Use test data first and keep a current backup or Git commit.
- Read commands before pasting. A README is useful evidence, not a substitute for judgment.
- Review agent-generated file changes with
git diffbefore committing. - Keep local services bound to
127.0.0.1unless you intentionally secure and expose them. - Do not give plugins or MCP servers broader filesystem, browser, GitHub, or cloud access than their current task requires.
- Confirm API costs and model names before running large batches.
- Stop and investigate repeated authentication failures instead of pasting a token into multiple places.
Reference and source trail
The manual reflects first-party files checked on August 18, 2026. It explains the indexed repository rather than promising that every optional third-party integration is available or safe.