{
  "markdown": "# EAI Gofer\n\nEAI Gofer is a business specification-driven delivery workflow for repositories.\nUsers talk to `/eai`, and use `/eai-update` when they need to install or update\nGofer. Gofer manages the pipeline that designs with you, builds with you, and\nvalidates the result. It keeps working artifacts in `.specify/` and ships across\nVS Code, Claude Code, Codex, GitHub Copilot, Gemini, and Grok Build.\n\nEAI Gofer is designed to be easy to adopt in an existing repo:\n\n- helps everyone, not just coders, write good code, that delivers a business\n  outcome\n- Work with AI to generate what you need whether it is business case, executive\n  summary, technical diagram of otherwise for you and your stakeholders to know\n  what will be built, not find out it is wrong later\n- one public `eai` entrypoint backed by the full internal delivery pipeline\n- closed-loop goal reconciliation with repo-owned goal ledgers and drift checks\n- repo-owned artifacts and templates\n- install paths for VS Code and AI coding CLIs\n- generated public command surfaces that stay aligned across hosts\n\n## Quick Start\n\n![EAI Gofer first run demo](./assets/gofer-first-run.svg)\n\n1. Install the VS Code extension or add the public plugin marketplace for your\n   preferred CLI.\n2. Start every request with `/eai`. Use `#eai` in Copilot-style prompts and\n   `$eai` in hosts that use dollar-prefixed skills.\n3. If you only need to add Gofer to an existing repo, run **Gofer: Initialize\n   Repository** in VS Code, then refresh/restart the host command picker.\n4. Gofer checks first-run readiness, workspace health, EAI CLI/login/tenant\n   state, and then routes the internal pipeline for you.\n\nIf `/eai` is unknown, use `/eai-update` in a host where Gofer is already\navailable. It updates the host plugin without requiring a repo or EAI login. For\na first install, use the matching command in the\n[5-minute first run guide](./.tech-docs/first-run.md).\n\nThe guide also includes a public Node.js bootstrap command. It installs Gofer\nwithout a repository for Claude, Codex, Copilot, Gemini, or VS Code.\n\n## App-Native Integration Model\n\nGofer now uses a light-plugin model across AI coding apps. The repo remains the\nsource of truth for `.specify/commands/`, `.specify/scripts/`, templates,\nreferences, specs, and memory. App plugins and app-native customizations provide\nthin entry points that check/bootstrap the repo and then route through the\nrepo-owned internal contracts.\n\n| Surface                         | Clean entry point             | Repo integration                                                                                      |\n| ------------------------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------- |\n| Codex App / Codex IDE           | `eai` or `eai-update` skill   | `AGENTS.md`, `.agents/skills/`, `.specify/scripts/`, `.vscode/mcp.json`                               |\n| VS Code / GitHub Copilot app    | `#eai` or `#eai-update`       | `.github/agents/`, `.github/skills/`, `.github/prompts/`, `.github/instructions/`, `.vscode/mcp.json` |\n| Claude Code app                 | `/eai` or `/eai-update`       | `.claude/skills/`, `.claude/commands/`, `.claude/agents/`, `.specify/scripts/`                        |\n| Gemini CLI / Gemini Code Assist | `/eai` or `/eai-update`       | `.gemini/`, `.specify/scripts/`, `.vscode/mcp.json`                                                   |\n| Grok Build                      | Ask Grok to use the EAI skill | `.grok/skills/`, `.specify/scripts/`                                                                  |\n\nThe UX rule is: users start with `eai`; `eai-update` is the only support\ncommand. Gofer keeps numbered stages and helpers as internal contracts under\n`.specify/commands/`, then chooses the right one based on the current feature\nstate. The `gofer` entrypoint remains as a compatibility alias, but public\ninstructions should teach `/eai`.\n\nFor copy-paste commands across VS Code, Claude Code, Codex, Copilot, Gemini, and\nGrok, see the [5-minute first run guide](./.tech-docs/first-run.md).\n\n## How The Pipeline Works\n\nUsers do not manually run stage commands. Write normal requests as `/eai ...`\nand Gofer will:\n\n1. Check the repo scaffold, EAI CLI, login, tenant, and app-template readiness.\n2. Work out the current feature state from `.specify/specs/`.\n3. Ask business-level questions when the goal, audience, value, risk, or tenant\n   context is unclear.\n4. Run the internal stage contracts for research, specification, planning,\n   tasks, implementation, and validation.\n5. Show the UI as early and as often as practical when an app UI is involved.\n6. Keep business-owner, CTO, CISO, architecture, testing, and validation\n   artifacts current.\n\nThe internal pipeline still has clear stages:\n\n| Internal stage | What Gofer does                                               | Main output                                    |\n| -------------- | ------------------------------------------------------------- | ---------------------------------------------- |\n| Start          | Understands the business outcome and checks EAI readiness     | feature folder, business scenario              |\n| Research       | Explores the repo, EAI platform fit, constraints, and options | `research.md`                                  |\n| Specify        | Turns the need into requirements and acceptance criteria      | `spec.md`                                      |\n| Plan           | Designs architecture, data, contracts, and delivery approach  | `plan.md`, `data-model.md`, `contracts/`       |\n| Tasks          | Breaks the plan into ordered implementation work              | `tasks.md`, `traceability.md`, `issues.md`     |\n| Implement      | Makes code and documentation changes with feedback loops      | code and document changes                      |\n| Validate       | Checks quality, security, evidence, tests, and business fit   | validation artifacts and final review evidence |\n\nValidation is the terminal quality gate. The previous standalone\nengineering-review stage is folded into validation.\n\nGofer now treats the pipeline as a closed loop, not just a straight line:\n\n- Research seeds `goal-ledger.json` with business goals, metrics, owners,\n  delivery states, and re-loop triggers.\n- Tasks keeps `traceability.md` as the requirement-to-task-to-code contract.\n- Validation runs the objective outcome gate, refreshes code/test evidence, and\n  writes `goal-rebaseline-report.md` when goals, assumptions, contracts, UX\n  scope, or implementation drift.\n\nEach stage also maintains a running product-release PR/FAQ in\n`working-backwards-prfaq.md`, with immutable stage snapshots in\n`prfaq-history/`. Gofer uses that same evidence to keep stakeholder review\ndocuments current:\n\n| Persona            | Summary document              | Built from                                                                                                    |\n| ------------------ | ----------------------------- | ------------------------------------------------------------------------------------------------------------- |\n| Business Owner     | `business-owner-summary.md`   | `problem-brief.md`, `discovery.md`, `spec-summary.md`, `business-metrics.md`, value stream evidence, ROI      |\n| CTO / Architecture | `cto-architecture-summary.md` | `plan.md`, `contract-pack.md`, `data-model.md`, C4 diagrams, `service-fit-matrix.md`, EAI preflight           |\n| CISO / Risk        | `ciso-security-summary.md`    | `validation-report.md`, `audit-history.md`, risk heatmap, auth/tenant controls, secret/data handling evidence |\n\nGofer also scores visual communication during validation. Architecture, process,\nsecurity, UI, and EAI Platform visuals must be simple, rendered or\nfallback-safe, source-controlled, traceable to requirements and code/test\nevidence, and safe for public or stakeholder review. Crowded, stale, unrendered,\nor private-data-bearing diagrams fail the architecture compliance gate.\n\nHuman-facing documents should start with a short executive summary in plain\nlanguage. Mermaid is the default for Markdown-native diagrams, Marp is\nrecommended when stakeholders need a slide narrative, D2/Structurizr-style\nsource is acceptable when it makes architecture clearer, and UI behavior should\nbe backed by screenshots, Storybook/component proof, Playwright evidence, or an\nequivalent render check.\n\nOptional helpers stay available internally for problem validation, checkpoints,\nbranding, test generation, stakeholder communications, workspace checks,\nbootstrap, and first-run EAI setup. Users should still ask through `/eai`, for\nexample: `/eai rebrand the stakeholder documents with our company logo`.\n\n## Model And Cost Policy\n\nEAI Gofer bootstraps a repo-owned model policy at:\n\n```text\n.specify/memory/gofer-model-policy.yaml\n```\n\nThe shipped default comes from `.specify/templates/gofer-model-policy.yaml`.\nBootstrap creates the memory copy when it is missing and does not overwrite\nlocal edits.\n\nDefault posture:\n\n- Claude: Haiku for simple scouting, Sonnet for normal work, Opus for hard\n  security/architecture/release gates.\n- Codex/OpenAI: GPT mini for simple coding, GPT nano only for mechanical\n  locate/classify/summarize work, GPT-5.3-Codex or flagship GPT for hard\n  tool-heavy coding and arbitration.\n- Gemini: Flash-Lite for cheap large-context scanning, Flash for normal\n  synthesis, Pro for hard large-context architecture/research gates.\n- Copilot: `Auto` for simple/default work; ask before selecting a paid/high-tier\n  picker model for hard review.\n\n## Install\n\n### VS Code\n\nRecommended: install from the VS Code Marketplace so users receive normal\nMarketplace updates. Manual `.vsix` installs remain supported, but VS Code does\nnot auto-update VSIX installs by default.\n\n- Marketplace listing:\n  [EnterpriseAI.gofer](https://marketplace.visualstudio.com/items?itemName=EnterpriseAI.gofer)\n- Marketplace docs:\n  [Use extensions in Visual Studio Code](https://code.visualstudio.com/docs/getstarted/extensions)\n- Publishing/update behavior:\n  [Publishing Extensions](https://code.visualstudio.com/api/working-with-extensions/publishing-extension)\n- VSIX update note:\n  [Extension Marketplace](https://code.visualstudio.com/docs/editor/extension-marketplace?azure-portal=true)\n\nPublic release assets:\n\n- Latest VSIX:\n  `https://eai-support.github.io/eai-gofer/releases/eai-gofer-latest.vsix`\n- Versioned releases: `https://eai-support.github.io/eai-gofer/releases/`\n\nVS Code and Copilot agent mode also receive repo-local customization files:\n`.github/agents/`, `.github/skills/`, `.github/prompts/`,\n`.github/instructions/`, and `.vscode/mcp.json`.\n\nMaintainer release note: stable releases publish the GitHub Release and public\nGofer feed first, because those are the authoritative artifacts used by\n`eai gofer refresh` and the plugin ZIP install path. GitHub Actions then\nattempts to publish `EnterpriseAI.gofer` to the Visual Studio Marketplace using\nMicrosoft Entra workload identity and `vsce publish --azure-credential`. The\nworkflow expects repository variables `VSCE_AZURE_CLIENT_ID`,\n`VSCE_AZURE_TENANT_ID`, and `VSCE_AZURE_SUBSCRIPTION_ID`, with the federated\nidentity authorized as a Contributor on the `EnterpriseAI` Marketplace\npublisher. `VSCE_PAT` is retained only as a legacy fallback because Azure DevOps\nglobal PATs are being retired.\n\n### Claude Code\n\nRecommended install path:\n\n```bash\nclaude plugin marketplace add eai-support/eai-gofer --scope user --sparse .claude-plugin --sparse plugins/eai-gofer\nclaude plugin install eai-gofer@eai-gofer --scope user\n```\n\nReferences:\n\n- [Discover and install plugins](https://code.claude.com/docs/en/discover-plugins)\n- [Create and distribute a plugin marketplace](https://code.claude.com/docs/en/plugin-marketplaces)\n- [Plugins reference](https://code.claude.com/docs/en/plugins-reference)\n\n### Codex\n\nRecommended install path:\n\n```bash\ncodex plugin marketplace add https://github.com/eai-support/eai-gofer --sparse .agents/plugins --sparse plugins/eai-gofer\ncodex plugin add eai-gofer@eai-gofer\n```\n\nReferences:\n\n- [Codex App](https://developers.openai.com/codex/app)\n- [Codex plugins](https://developers.openai.com/codex/plugins)\n\nThe Codex plugin exposes `eai` as the recommended public skill, with `gofer`\nretained as a compatibility alias. It does not expose a second namespaced copy\nof every stage command. In an initialized repo, start with the plain `eai` skill\nfrom `.agents/skills/`.\n\n### GitHub Copilot CLI\n\nRecommended install path:\n\n```bash\ncopilot plugin marketplace add https://github.com/eai-support/eai-gofer\ncopilot plugin install eai-gofer@eai-gofer\n```\n\nReferences:\n\n- [GitHub Copilot app](https://docs.github.com/en/copilot/how-tos/github-copilot-app)\n- [Finding and installing Copilot CLI plugins](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/plugins-finding-installing)\n- [Copilot CLI plugin marketplace](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot/plugins-marketplace)\n\n### Gemini CLI\n\nRecommended install path:\n\n```bash\ngemini extensions install https://github.com/eai-support/eai-gofer --auto-update\n```\n\nReference:\n\n- [Gemini CLI extensions reference](https://github.com/google-gemini/gemini-cli/blob/main/docs/extensions/reference.md)\n\n### Downloadable Bundle\n\nFor offline testing or pinned installs, use the public agent bundle zip:\n\n```bash\ncurl -fsSL https://eai-support.github.io/eai-gofer/releases/eai-gofer-agent-plugin-latest.zip \\\n  -o /tmp/eai-gofer-agent-plugin-latest.zip\n```\n\nThe public release feed is:\n\n```text\nhttps://eai-support.github.io/eai-gofer/releases.json\n```\n\n## First EAI Platform App Setup\n\n`/eai` replaces the long website setup prompt for users who have installed a\nsupported AI coding host. It can run before `.specify/` exists in the target\nrepo, because Gofer routes first-run setup internally when the machine, login,\ntenant, template, or scaffold is not ready.\n\nWhen first-run setup is needed, Gofer:\n\n- detects Claude Code, Codex, Copilot, Gemini, VS Code, GitHub Codespaces, OS,\n  shell, and workspace folder\n- checks Git, Node.js, npm, the scoped EAI npm registry, and `eai --version`\n- asks before installing Git, Node.js, npm, EAI CLI, opening browser login, or\n  changing tenant/project state\n- uses `npm install -g eai-cli` when EAI CLI installation is approved, with\n  `npm install -g @enterpriseai/cli --@enterpriseai:registry=https://eai-support.github.io/eai/registry/`\n  as the static-registry fallback when npmjs is unavailable\n- runs `eai update --check`, `eai --describe`, `eai whoami`, and\n  `eai tenant list --format json` before assuming CLI syntax or tenant readiness\n- does not invent EAI CLI commands; it verifies command paths and flags with\n  `eai --describe` and command-specific `--help` before suggesting or running\n  them\n- runs `eai agent guide --format json` when advertised, and after `eai` errors\n  uses `eai errors explain <code-or-reason> --format json` before guessing a\n  workaround\n- asks for the project display name, proposes a lowercase kebab-case CLI name,\n  confirms the active tenant, then runs\n  `eai init <project-name> --skip-prompts --company-tenant <active-tenant-id>`\n  when approved\n- treats `E001` from `eai verify`, `eai template check`, or\n  `eai doctor --check-updates` as \"this repo is not yet an EAI app project\",\n  then offers initialization instead of leaving the user at a dead end\n- runs `eai template check --format json` and\n  `eai gofer refresh --check --format json` when the repo already looks like an\n  EAI app so Gofer can see EAI template drift and Gofer scaffold drift early\n- uses `eai resources schema --format json` and\n  `eai workflow readiness --format json` later in the pipeline to ground block,\n  data, and workflow choices in actual platform capabilities\n- verifies `.specify/` and Gofer files created by `eai init`, bootstraps the\n  repo scaffold if it is missing or stale, and writes a safe\n  `.specify/logs/eai-first-run-report.md`\n\nCross-platform behavior:\n\n| Environment       | Behavior                                                                               |\n| ----------------- | -------------------------------------------------------------------------------------- |\n| macOS             | Use Homebrew only when it already exists; otherwise use standard installers.           |\n| Linux             | Prefer existing tools; detect `apt`, `dnf`, `yum`, or `zypper` if install is approved. |\n| Windows           | Use PowerShell-safe commands and prefer `winget`; do not assume Git Bash.              |\n| GitHub Codespaces | Prefer devcontainer/user-level npm and avoid `sudo` unless explicitly approved.        |\n\n## Repository Layout\n\n| Path                  | Purpose                                       |\n| --------------------- | --------------------------------------------- |\n| `extension/`          | VS Code extension package                     |\n| `language-server/`    | Language server and MCP-facing support        |\n| `src/`                | Node-based orchestration and utilities        |\n| `.specify/commands/`  | Canonical command source                      |\n| `.specify/templates/` | Repo bootstrap templates and helpers          |\n| `.specify/specs/`     | Local working artifacts created per feature   |\n| `plugins/eai-gofer/`  | Portable plugin bundle for CLI hosts          |\n| `.claude/skills/`     | Claude Code app/plugin umbrella skill         |\n| `.github/agents/`     | VS Code/GitHub Copilot custom agents          |\n| `.github/skills/`     | VS Code/GitHub Copilot umbrella skill         |\n| `.tech-docs/`         | Public documentation source for the docs site |\n\n## Development\n\n```bash\nnpm install\ncd extension && npm run compile\ncd ..\nnpm run build\nnpm run lint\nnpm run typecheck\nnpm test\nnpm run gofer:closed-loop-audit -- --feature-dir .specify/specs/<feature>\nnpm run gofer:generate\nnpm run gofer:package-plugin -- --sync-repo\n```\n\n## Community\n\n- Questions and usage help:\n  [GitHub Discussions](https://github.com/eai-support/eai-gofer/discussions)\n- Bugs and feature requests:\n  [GitHub Issues](https://github.com/eai-support/eai-gofer/issues)\n- Project wiki: [GitHub Wiki](https://github.com/eai-support/eai-gofer/wiki)\n- Security guidance: [SECURITY.md](./SECURITY.md)\n- Contribution guidance: [CONTRIBUTING.md](./CONTRIBUTING.md)\n- Support policy: [SUPPORT.md](./SUPPORT.md)\n\nRoadmap-fit issues may also receive an automation-generated draft intake PR so a\nhuman reviewer can scope the work before implementation starts.\n\n## Related Projects And References\n\nEAI Gofer sits in the same broader ecosystem as specification-driven and\nagent-oriented developer tooling. Useful references:\n\n- [GitHub Spec Kit docs](https://github.github.com/spec-kit/index.html)\n- [github/spec-kit](https://github.com/github/spec-kit)\n- [GitHub repository best practices](https://docs.github.com/en/repositories/creating-and-managing-repositories/best-practices-for-repositories)\n- [GitHub Discussions quickstart](https://docs.github.com/discussions/quickstart)\n- [Setting guidelines for contributors](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/setting-guidelines-for-repository-contributors?apiVersion=2022-11-28)\n\n## What Helps A Repo Get Forks And Stars\n\nThe basics are not optional:\n\n- a permissive open-source license\n- a 5-minute quick start that actually works\n- clear screenshots or demos\n- active issue triage and visible roadmap items\n- contributor docs, security policy, and support routing\n- predictable releases and changelog discipline\n- public install/update paths for every supported host\n\nEAI Gofer now uses the Apache-2.0 license. `Enterprise AI` and `EnterpriseAI`\nremain Enterprise AI Pty Ltd marks; see [TRADEMARKS.md](./TRADEMARKS.md) and the\ncurrent legal page at\n[enterpriseaigroup.com/terms-of-use](https://enterpriseaigroup.com/terms-of-use).\n\nThe remaining work before a real public launch is the final legacy-enterprise\ncleanup.\n",
  "bytes": 20069,
  "sha": "f839155ffb6069c846e28ab92812d6c080e7165303ba6284c9efd02cd35de779",
  "repo_slug": "eai-support/eai-gofer",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/plg_eai_support_eai_gofer_5d918fef/readme"
}