Racecraft Plugins Public

Racecraft Plugins Public is the open-source plugin marketplace from
Racecraft Lab. It currently publishes
SpecKit Pro for both Claude Code and Codex.

The short version: install this marketplace if you want Racecraft-maintained
agent workflows you can inspect, version, and update through your coding-agent
plugin system.

Trust check: Plugins can change how an agent reads files, writes files,
launches tools, or delegates work. Review the plugin README and source before
installing or updating.

Should I Install This?

Available Plugins

Install The Marketplace

This repository exposes the same marketplace through two runtime surfaces:

Claude Code

Add the marketplace, then install the plugin:

/plugin marketplace add racecraft-lab/racecraft-plugins-public
/plugin install speckit-pro@racecraft-plugins-public
/reload-plugins

Verify the installed plugin from Claude Code's /plugin UI, then use
namespaced plugin skills such as /speckit-pro:speckit-status and
/speckit-pro:speckit-coach.

Codex

Claude Code commands are the separate DOC-003-owned path; use the
Claude Code install guide
for that runtime. For Codex, open this repository in Codex, then open the plugin
directory:

codex
/plugins

Codex reads the repo-scoped marketplace from
.agents/plugins/marketplace.json. That
marketplace points SpecKit Pro at the generated Codex payload,
dist/codex/speckit-pro/. Do not install Codex
from the mixed authoring tree at speckit-pro/.

After installing SpecKit Pro, run the plugin's Codex install skill so its
bundled custom-agent TOML files are copied into Codex's agent registry:

@SpecKit Pro -> install

or:

$install

The default destination is ~/.codex/agents/; choose .codex/agents/ only when
you intentionally want project-scoped custom agents. Verify these ten
installer-copied TOML files only:

• autopilot-fast-helper.toml
• phase-executor.toml
• clarify-executor.toml
• checklist-executor.toml
• analyze-executor.toml
• implement-executor.toml
• codebase-analyst.toml
• spec-context-analyst.toml
• domain-researcher.toml
• uat-runbook-author.toml

Then restart Codex. Also restart Codex after plugin enablement changes,
custom-agent refreshes, or relevant Codex config edits.

Codex loads installed plugins from the installed plugin cache at
~/.codex/plugins/cache/$MARKETPLACE_NAME/$PLUGIN_NAME/$VERSION/. Treat that as
runtime state, not the source of truth. If SpecKit Pro looks stale after an
update, check the marketplace source or copied personal payload, the generated
payload, the installed plugin cache, the selected custom-agent destination, and
whether Codex was restarted. Rerun @SpecKit Pro -> install or $install after
a plugin update that changes bundled custom-agent TOML files, then restart
Codex again. Do not edit the installed plugin cache.

Install safety stays bounded here: Codex sandbox, approval, and network policy
still apply. Git-backed marketplace setup can require network access or network
approval. Writing to ~/.codex/agents/ is outside most project workspaces, so
approve only the expected local write of the named SpecKit Pro TOML files, or
rerun with .codex/agents/ or narrower permissions. The generated Codex payload
can include lifecycle hook configuration such as codex-hooks.json; hook
behavior remains governed by Codex sandbox, approval, hook trust, and configured
policy controls.

For personal Codex installs, follow the official local-plugin layout: copy or
sync the generated Codex payload, then point
~/.agents/plugins/marketplace.json at that copied payload, not the mixed
authoring tree:

dist/codex/speckit-pro/

For deeper Codex file-layout details, use the
DOC-007 reference shell. For
trust, hook policy, update, rollback, permission repair, and stale-cache
forensics, use the
DOC-008 security and trust
and DOC-008 troubleshooting
shells.

How This Repo Is Organized

Contributor Path

Use this lane when changing documentation, skills, agents, hooks, scripts, or
marketplace packaging.

1. Edit source files under speckit-pro/ or this root README.

2. Rebuild generated install payloads through the Python runner gate:

   cd speckit-pro
   python3 -m speckit_pro_runner < ../tests/speckit-pro/unit/fixtures/installed-plugin-release/requests/payload-completeness-apply.json
   

3. Run the default validation suite:

   Use the repository default validation suite documented in the contributor guide.

4. For structural-only changes, this narrower check is useful while iterating:

   Use the repository structural validation suite documented in the contributor guide.

5. Open a PR with a Conventional Commit title, for example:

   docs(speckit-pro): clarify plugin install paths
   

What Not To Edit Directly

• Do not hand-edit dist/** payload files except to inspect a generated result.
  Regenerate them from source.
• Do not install speckit-pro/ directly as a Codex personal plugin. Use
  dist/codex/speckit-pro/.
• Do not change marketplace versions manually as part of normal docs work.
  Release automation owns version synchronization.

Official Platform Docs

The README install and packaging guidance is grounded in these official docs:

Repo-specific behavior is grounded in the checked-in manifests, payload builder,
tests, and plugin source.

License

This repository is licensed under the MIT License. See each plugin
README for plugin-specific details.