setup

Validates MySpec, GitHub, and cloud access before starting a software factory run.

Updated Sep 12, 2026
One-click install
npx skills add https://github.com/myspecs/claude-plugins --skill setup-myspecs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: setup
Source: https://github.com/myspecs/claude-plugins/tree/main/plugins/myspec-factory/skills/setup
Command: npx skills add https://github.com/myspecs/claude-plugins --skill setup-myspecs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before a MySpec software factory run can start, the manager session, worker sessions, and the MySpec platform all need correct access and configuration. This Skill checks every prerequisite in order, stops at the first failure with a concrete fix, and ends by selecting the MySpec project and opening its live event feed. ## Core Features & Use Cases - Access verification: Confirms MySpec sign-in via the myspec-mcp plugin, GitHub CLI permissions, branch protection rules, and Remote Control connectivity for cloud worker visibility. - Worker readiness checks: Validates cloud session prerequisites (claude.ai sign-in, network egress, MYSPEC_API_TOKEN) and local worktree fallback with per-worker credentials. - Opt-in repository configuration: Offers to add plugin marketplace settings, .gitignore entries, and a managed CLAUDE.md block, never writing without user approval. - Use Case: Before the first factory run in a repository, run the setup to discover that the Claude GitHub App is missing and Remote Control is not connected, fix both, then pick the MySpec project and start listening to its event stream. ## Quick Start Ask Claude to set up the factory for this repository and pick your MySpec project, for example by saying "set up the factory for project X".

Frequently Asked Questions about setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the MySpec software factory in a repository?▼

Run the /myspec-factory:setup command or ask to "set up the factory". The skill checks MySpec sign-in, GitHub access, cloud readiness, and repository configuration in order, then lets you pick a MySpec project and opens its event feed.

What prerequisites does a MySpec factory run need?▼

You need the myspec-mcp plugin installed and signed in, the GitHub CLI authenticated with push and pull-request rights, Node.js 22+, and optionally cloud session readiness with a MYSPEC_API_TOKEN. The setup skill verifies each and reports fixes.

Can factory workers run locally instead of in the cloud?▼

Yes, workers fall back to local git worktree sessions when cloud dispatch is refused or unavailable. Local workers need git worktree support, the claude CLI with --worktree and --bg flags, and their own MySpec PAT from .claude/settings.local.json.

Why does the factory manager not see its cloud worker sessions?▼

Cloud sessions are invisible unless the manager session is connected to Remote Control with a claude.ai sign-in. Start the manager with claude --remote-control or run /remote-control inside the session, then confirm with /list-agents.

Does the setup skill modify my repository automatically?▼

No, every repository write is opt-in. The skill describes each proposed change to .claude/settings.json, .gitignore, and CLAUDE.md, asks for confirmation with AskUserQuestion, and only writes after approval.

Why do factory workers need their own MySpec API token?▼

Two MySpec servers sharing ~/.myspec/oauth_creds.json conflict when one refreshes the token, causing Refresh token rejected errors that take the manager's tools down mid-run. Each worker gets its own PAT scoped to the correct organisation.