MySpec for Claude Code

Two plugins, one marketplace

The marketplace is named myspec and has two plugins. Install myspec-mcp first - myspec-factory needs it.

myspec-mcp skills

• /myspec-mcp:setup - sign in, use an API token, switch organization, fix connection errors.
• implement - build a spec bundle one task at a time: ask about open points, write tests from acceptance criteria, check the constitution, mark the task done on MySpec.
• analyze - check a bundle for gaps and conflicts, and check whether the code matches the spec (read-only).
• spec-authoring - write or update constitution, requirements, solution, tasks, change proposals, and OpenSpec changes in MySpec's formats, then push them.
• reverse-bridge - share a local repository with a MySpec brownfield spec session.

Only setup is a slash command. The other skills start on their own when you describe the task in plain words, for example "implement the next task from project X".

Before you start

• Claude Code with plugin support (/plugin works).
• Node.js 22 or newer, with npx on your PATH.
• A MySpec account - app.myspec.dev, free during Open Beta.
• A spec bundle to build from. Create one in the MySpec workflow, or write one with the spec-authoring skill.

myspec-factory needs more - see section 08.

Add the marketplace and install

Inside Claude Code:

/plugin marketplace add myspecs/claude-plugins
/plugin install myspec-mcp@myspec

Or from a terminal:

claude plugin marketplace add myspecs/claude-plugins
claude plugin install myspec-mcp@myspec

Then restart Claude Code. Plugins load at startup, so the MCP server and skills appear only in a new session.

Sign in to MySpec

Run this from a terminal, or inside Claude Code with the ! prefix:

npx -y @myspec/mcp-server login

• Add --org <slug> to pick an organization if you belong to more than one.
• Add --paste on a remote machine without a browser: open the printed URL anywhere and paste the whole <code>.<state> value back within 60 seconds.

For CI, containers, or shared machines, create an API token in the MySpec webapp (avatar menu → API tokens) and export it in the shell that starts claude:

export MYSPEC_API_TOKEN=msp_pat_...
claude

Check it works

1. /mcp shows myspec as connected.
2. /plugin lists myspec-mcp as enabled.
3. Run /myspec-mcp:setup, or ask Claude: "Set up MySpec and check I'm signed in." The setup skill runs the checks and fixes what it can.

Build from your spec

Describe the task in plain words. The matching skill starts on its own:

Set up MySpec and check I'm signed in.
Implement the next task from the "inventory-service" project on MySpec.
Analyze the spec bundle for project X and show requirement coverage.
Does the code in this repo match the MySpec spec? What's missing?
Pull the specs for project X into .specs/ and summarise the requirements.
Write a requirements.md for this feature in MySpec format and push it to project X.
Draft an OpenSpec change proposal for adding rate limiting to the billing module.
Share this repo with my MySpec brownfield session.

How implement works

1. Resume. Read the tasks.md checkboxes on MySpec, the local .specs/<bundle>/progress.md, and git history.
2. Read. The constitution in full, then only the requirement and solution sections the next task cites.
3. Ask. At most five multiple-choice questions about open decisions, with the answers written back into the bundle.
4. Build. One test per acceptance criterion, then the code, then a check against the constitution.
5. Record. Mark the task [x] on MySpec, update the progress note, and commit if you asked for commits.
6. Stop at milestones. Run the full test suite, check the code against the spec, and wait for your review.

The other skills

• analyze reports constitution alignment, requirement-to-task coverage with a percentage, unclear wording, dependency cycles, and drift between code and spec. It adds gap tasks only when you approve.
• spec-authoring writes EARS+ requirements, brownfield proposals and AR/BR/CR deltas, and OpenSpec changes in the exact formats MySpec's reviewers expect.
• reverse-bridge runs npx -y @myspec/mcp-server reverse so a MySpec brownfield session can read your local code.

Share it with your team

Commit this to the repository's .claude/settings.json. Team members are offered the marketplace and myspec-mcp when they open the repository:

{
  "extraKnownMarketplaces": {
    "myspec": { "source": { "source": "github", "repo": "myspecs/claude-plugins" } }
  },
  "enabledPlugins": {
    "myspec-mcp@myspec": true
  }
}

• Each person still signs in (or exports MYSPEC_API_TOKEN) on their own machine.
• Add .specs/ to the repository's .gitignore. That folder holds spec files downloaded from MySpec and local progress notes.
• Leave myspec-factory out of shared settings, so worker sessions do not load the manager skills.

The Software Factory (myspec-factory)

myspec-factory turns Claude Code into a Software Factory Manager. The manager never writes feature code. It groups related tasks from tasks.md into waves, starts one Claude Code worker session per group (in the cloud, or in a local git worktree as a fallback), checks and merges their pull requests, marks tasks done on MySpec, and stops at each milestone for your review. New to the idea? Read what an AI software factory is and how to build one.

Extra prerequisites

• myspec-mcp installed and signed in.
• The GitHub CLI (gh) signed in with push and pull-request rights on the target repository, and a local clone with its default branch pushed to GitHub.
• For cloud workers: Claude Code on the web, the Claude GitHub App on the repository, and MYSPEC_API_TOKEN set in the cloud environment at claude.ai/code.

Set it up

1. Install it on the manager's machine only:
   Inside Claude Code text COPY

   /plugin install myspec-factory@myspec

2. In the repository you want to manage, run /myspec-factory:setup. It checks MySpec and GitHub access, cloud readiness, and branch protection, and proposes repository settings. It writes nothing until you approve.
3. Turn on the manager persona for that repository only - /config → Output style → Software Factory Manager, or in .claude/settings.local.json:
   .claude/settings.local.json json COPY

   { "outputStyle": "myspec-factory:Software Factory Manager" }

4. Start the manager with Remote Control, so it can see and message its cloud workers (or run /remote-control in a running session):
   From a terminal bash COPY

   claude --remote-control "factory <bundle>"

5. Ask: "Run the factory for project X, bundle Y."

Autonomy levels

At every level the manager still asks about spec questions, changes beyond the spec, and starting the next milestone. It never force-pushes, bypasses branch protection, or merges a red pull request.

Set up the factory for this repository.
Run the factory for project "inventory-service", bundle "v1".
Plan the waves: which tasks can run in parallel?
Dispatch wave 2 in the cloud, at most 3 workers.
Integrate the open factory pull requests.
Schedule a factory shift every night at 2am.

Update, remove, troubleshoot

/plugin marketplace update myspec
/plugin update myspec-mcp@myspec
/plugin update myspec-factory@myspec

Restart Claude Code after updating. To remove a plugin: /plugin uninstall <plugin>@myspec.

• Plugin not found on install - add the marketplace first and use the @myspec suffix. Check with /plugin marketplace list.
• myspec shows as failed in /mcp - check node -v is 22 or newer, run npx -y @myspec/mcp-server --version once to fill the npx cache, then restart.
• Not authenticated or "run login" - run npx -y @myspec/mcp-server login, or export MYSPEC_API_TOKEN.
• missing required claims (sub, org), or HTTP 404 for a project you can see in the webapp - sign in to the right organization: npx -y @myspec/mcp-server login --org <slug>.
• Two sets of MySpec tools - a project .mcp.json or claude mcp add also registers myspec. Remove that entry (or run claude mcp remove myspec) and keep the plugin.
• A tool a skill mentions is missing - your cached server is old. Run npx -y @myspec/mcp-server@latest --version, then restart.
• /plugin update does nothing - run /plugin marketplace update myspec first.

Or ask Claude to "troubleshoot my MySpec setup" - the setup skill walks through the checks. Full guides live in the myspecs/claude-plugins repository.

Frequently asked questions