Eai Gofer
Run the Gofer spec-driven pipeline from business scenario through validation with staged slash commands in Claude, Codex, Gemini, or Copilot CLI.
Overview
eai-gofer is a plugin marketplace for the Validate phase that installs the Gofer spec-driven command pipeline from business scenario through gofer_validate across major agent CLIs.
What is this marketplace?
- Core pipeline commands from /0_business_scenario through /6_gofer_validate
- Spec-driven development tag set for multi-agent CLIs (Claude, Codex, Copilot, Gemini)
- Single eai-gofer plugin at marketplace version 3.5.7, Apache-2.0
- Optional helper commands alongside the numbered stage flow
- Public GitHub install path for Claude Code and peer agent CLIs
- 1 plugin in marketplace (eai-gofer)
- plugin and metadata version 3.5.7
- pipeline spans /0_business_scenario through /6_gofer_validate
What problem does it solve?
Solo builders using AI agents often ship code before the business scenario and validation steps are written, so rework piles up.
Who is it for?
Indie builders adopting spec-driven development who use Claude Code, Codex, Copilot CLI, or Gemini and want one shared pipeline slug.
Skip if: Hackathon-style throwaway prototypes with no written requirements or teams that already enforce a rigid external PM tool outside the agent.
What do I get? / Deliverables
After registering the marketplace, you run numbered Gofer commands that walk from scenario to validation so specs lead implementation and a final validate step closes the loop.
- Staged spec artifacts from business scenario through pipeline steps
- Completed /6_gofer_validate checkpoint against the defined spec
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Gofer begins at business scenario and scoping before implementation, so validate is the first journey shelf even though later commands touch build and ship checks. Scope is canonical because /0_business_scenario and early pipeline steps define what to build before coding workflows dominate.
How it compares
Multi-stage spec methodology marketplace, not a single-task codegen or DevOps integration skill.
Common Questions / FAQ
Who is Eai Gofer for?
Solo and small-team builders who want a repeatable spec-driven command pipeline across Claude, Codex, Copilot, and Gemini CLIs.
When should I use Eai Gofer?
Use it at the start of a feature or product slice when you need business scenario clarity before build, then through validate before you call the work done.
How do I add Eai Gofer to my agent?
Install the eai-tools/Eai Gofer marketplace from the public GitHub repository into Claude Code or your supported CLI, then invoke /0_business_scenario and subsequent Gofer commands.