Boss plugin
boss-skill
An expert squad for a coding agent: from PRD and architecture to TDD, tests and deploy, with hard requirements for every role
- 550 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- The full chain writes code and runs tests, build and deploy in the project.
- The `ship` stage prepares a release. If you do not want one, stop the chain with `--stop-after`.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/boss-skillDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The full chain writes code and runs tests, build and deploy in the project.
- The `ship` stage prepares a release. If you do not want one, stop the chain with `--stop-after`.
This is third-party code. Review the repository files before installing.
What it does
Boss turns one coding agent into a squad of nine roles: product manager, architect, UI designer, tech lead, scrum master, frontend, backend, QA and DevOps. Each stage writes a real file to `.boss/<project>/`: `prd.md`, `architecture.md`, `tech-review.md`, `plan.md`, `tasks.md`, `qa-report.md` and `deploy-report.md`. Progress is judged by files on disk, not by what the agent says. Every role has a table of required items. A PRD, for example, holds Given-When-Then scenarios, and an architecture compares at least two options. If requirements fail, the next stage is blocked until you explicitly allow it. Development follows TDD: a failing test first, then the minimum code. The `/boss:pm`, `/boss:architect`, `/boss:dev`, `/boss:qa` commands and others start the chain at the chosen stage and run it through `ship`. Say "stop" or pass `--stop-after` to end the chain. It works in Claude Code, Codex, OpenClaw, Antigravity and Hermes.
Who it is for. Developers and small teams who want a predictable path from idea to release with the artifacts of every step in the repository.
Good fit when
- You build a small app from scratch: `/boss Build a local personal todo app --skip-ui` runs the whole path
- You want a safe first run on live code: `/boss:review` reads the project and writes `tech-review.md` and `plan.md`
- You need quality evidence: `/boss:qa` runs tests and saves a `qa-report.md`
- A spec already exists and work should start at architecture with `/boss:architect`
- The project has no UI: the `--skip-ui` flag skips the design stage
Not a fit when
- A one-line fix: a chain of nine roles outweighs the task
- You want a free-form dialog without hard stages and artifacts
- The agent must not ship the result: the last stage prepares build and deploy, so stop it with `--stop-after`
- The project follows a corporate process: Boss brings its own roles and requirements
Example request
/boss:review Review the current project, show the technical findings and a work plan, and do not change code.Limitations
- The full chain writes code, runs tests and reaches the `ship` stage with deploy, so make the first run with `/boss:review`: it changes nothing in the repository.
- It ships through plugin marketplaces only, with no npm package or global binary.
- The summary section heading in stage artifacts is Chinese (`## 摘要`). The docs are translated into seven languages.
- The only network part is opt-in: a local UI preview server on `127.0.0.1`.
How to disable. In Claude Code run `/plugin uninstall boss@boss-skill`. The `.boss/` artifacts folder stays in the project and you delete it by hand.
FAQ
How do I install Boss in Claude Code?
Run `/plugin marketplace add echoVic/boss-skill`, then `/plugin install boss@boss-skill`. Codex uses `codex plugin marketplace add echoVic/boss-skill`, and other agents use `npx skills add echoVic/boss-skill`.
How does `/boss:review` differ from `/boss`?
`/boss:review` starts the tech lead and writes `tech-review.md` and `plan.md`. Plain `/boss` starts at the product manager and runs the whole chain through `ship`.
What do `--quick` and `--skip-ui` do?
`--quick` skips clarifying questions, and `--skip-ui` skips the UI design stage for API-only or CLI projects.
Where does Boss put its results?
In a `.boss/<name>/` folder in the project. Each stage writes its own file there, and Boss decides from those files whether to move on.
Does Boss send data over the network?
No, there is no telemetry or remote model proxy by default. The only network part is opt-in: a local UI preview server on `127.0.0.1`.
Discussion
No questions or reviews yet.
Related
PluginsA 33-skill plugin with gates: question the request, verify facts against sources, test first, review by a second model
A CLI that wires a research-to-delivery pipeline with documents and quality gates into Claude Code, Cursor, Codex and other agents
Eleven skills take an agent from an idea to verified code through a PRD and RFCs kept as files in the repository
A Claude Code plugin that runs a task through stages with review and gates, with a local board of decisions and execution.
A skills library that gives coding agents a development process: brainstorming, planning, TDD, subagents and code review
An OpenAI Codex CLI extension: 27 skills, 16 MCP tools and AGENTS.md rules for PDCA development with a mandatory design document
README in short
The roles, the stage chain from `pm` to `ship`, commands that start at any stage and two layers of quality control are covered: role requirements and command checks. The repository holds a PRIVACY.md and deterministic evals over captured transcripts.