Skip to content

Choose a workflow

Select Elephant-Goldfish and describe the task, or name one of these skills. Give it the repository, document, or change you want examined.

Skill Use it for Result
eg-brainstorm Comparing possible directions Alternatives, tradeoffs, and validation steps
eg-prd Turning an idea into requirements Requirements grounded in supplied evidence, with open questions
eg-new-feature Checking a design or building a feature Separate comprehension, critique, and readiness checks before implementation
eg-fix-bug Diagnosing or fixing a failure A reproduction, separate diagnosis, and verification if a repair is requested
eg-precommit-review Reviewing a diff, branch, PR, or pending changes Findings tied to the exact reviewed artifact
Use $eg-brainstorm to compare ways to add offline reading to this app.
Keep the existing account model. Compare approaches before building.

The workflow tests the alternatives against the constraints. It does not start implementation simply because an option looks promising.

Use $eg-prd to turn these interview notes into requirements.
Separate observed needs from assumptions and unresolved decisions.

The result stays within the supplied evidence. A PRD request ends with the document unless you also ask for implementation.

Use $eg-new-feature to review this export design.
Check whether it is clear, where it could fail, and whether it is ready to build.
Do not implement it yet.

Fresh comprehension, critic, and readiness passes inspect the same design version. They do not receive each other’s conclusions. Unresolved material decisions keep implementation from starting.

Use $eg-fix-bug to diagnose this failing reproduction.
Give the fresh reviewer the symptoms and evidence, without my suspected cause.
Report the diagnosis before editing.

If you request a fix, the workflow first establishes the failure, applies the repair, checks the same reproduction, and reviews the resulting change.

Use $eg-precommit-review to review only the staged diff.
Exclude unstaged changes. Report findings without fixing them.

The workflow distinguishes staged, unstaged, untracked, and committed changes. For a branch or PR, it resolves the actual comparison base. It does not assume that the base is main.

The Elephant verifies each finding. If repairs are authorized, it freezes the revised artifact and sends that version to a new reviewer. Earlier findings stay in a separate ledger so they can be checked without steering the new review.

The default limit is an initial review plus at most two repair or revision rounds. A tighter repository or user limit takes precedence. Remaining findings are reported when the limit is reached. Missing evidence, failed tools, and checks that did not run are never reported as passes.

Return to the quickstart.