Run all engineering plugin setup steps in sequence — set up OpenSpec, scaffold project-context.json, and set up rules-ex infrastructure.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add atman-33/workhub --skill setup-all --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Setup All?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/atman-33-setup-all)More formats (shields.io, HTML) on the badges page.
---
name: setup-all
description: Run all engineering plugin setup steps in sequence — set up OpenSpec, scaffold project-context.json, and set up rules-ex infrastructure.
disable-model-invocation: true
allowed-tools: Bash(node --version) Bash(npm list *) Bash(npm install *) Bash(openspec *) Read Write
---
Run all engineering plugin setup steps in sequence. Each phase is independent — a failure in one phase is reported and the next phase continues.
---
## Phase 1 — Set up OpenSpec
1. Run `node --version`. If Node.js is missing or older than 20.19.0, report the version and skip to Phase 2 with a note.
2. Check whether OpenSpec CLI is already installed globally:
```bash
npm list -g @fission-ai/openspec --depth=0
```
If not installed, install it:
```bash
npm install -g @fission-ai/openspec@latest
```
3. Run:
```bash
openspec init --tools claude
```
---
## Phase 2 — Scaffold project-context.json
4. Read `.claude/project-context.json` in the current project root.
- If it already exists: show its current contents and note that it was left unchanged.
- If it does not exist: create it with the following template (placeholder paths must be replaced by the user):
```json
{
"roleBasedDelegation": true,
"openspecPath": "<absolute path to the openspec docs folder>",
"projects": [
{
"name": "example-project",
"path": "<absolute path to a frequently-used project>",
"summary": "short one-line description (optional)"
}
]
}
```
---
## Phase 3 — Scaffold rules-ex infrastructure
5. Read `.claude/rules/rules-ex-authoring.md`.
- If it already exists: show its path and note it was left unchanged.
- If it does not exist: read `skills/setup-rules-ex/assets/templates/rules-ex-authoring.md`
(relative to this plugin's root; the canonical template, shared with the
`setup-rules-ex` skill) and write its exact contents to
`.claude/rules/rules-ex-authoring.md`.
6. Read `.claude/rules-ex/README.md`.
- If it already exists: show its path and note it was left unchanged.
- If it does not exist: read `skills/setup-rules-ex/assets/templates/rules-ex-readme.md`
(relative to this plugin's root) and write its exact contents to
`.claude/rules-ex/README.md`.
---
## Output Format
After all three phases complete, print a summary table:
| Phase | Status | Notes |
|-------|--------|-------|
| 1 — OpenSpec | ✓ / ✗ | skipped / installed / already installed |
| 2 — project-context.json | ✓ / ✗ | created / already existed |
| 3 — rules-ex infrastructure | ✓ / ✗ | created / already existed (per file) |
Then remind the user:
- Edit the placeholder paths in `.claude/project-context.json` before starting a new session.
- Changes to `project-context.json` take effect on the next session start (not `/reload-plugins`).
- Use absolute paths matching your environment (Windows: `C:/repos/...`, WSL: `/mnt/c/repos/...`).
- Add cross-cutting rules as `*.md` files under `.claude/rules-ex/` — each must have a `paths:` front matter.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!