crew-setup

Bootstrap and configure a repository for the crew workflow through nine resumable phases.

2|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill crew-setup-mbadali25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crew-setup
Source: https://github.com/mbadali25/useful-claude-add-ons/tree/main/plugin/crew/skills/crew-setup
Command: npx skills add https://github.com/mbadali25/useful-claude-add-ons --skill crew-setup-mbadali25

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up a repository for the crew multi-agent workflow involves many interdependent decisions — platform detection, provider configuration, tracker wiring, smoke harnesses, and promotion gates — and doing it ad hoc leaves repos half-configured with gates that pass vacuously. This Skill walks the setup as nine resumable, gated phases so nothing is silently skipped. ## Core Features & Use Cases - Phased, resumable setup: Tracks progress in .crew/STATUS.md across nine phases (platform, config, providers, smoke harness, code map, verification map, browser tests, promotion gates, first ticket), stopping after each for review. - Platform and toolchain detection: Scripts detect OS, WSL, CRLF issues, repo stack, and resolve tools to forms that actually run on the machine. - Guarded configuration: Creates .crew/config.json from a template, wires trackers (files, Jira, ServiceDesk Plus, Obsidian), and enforces gitignore rules for secrets before any exist. - Use Case: A developer says "set up crew in this repo" and the Skill detects the platform, asks three scoping questions, creates the config and verification scaffolding, and stops until the smoke harness runs green. ## Quick Start Ask the assistant to set up crew in this repository and follow the guided phases it proposes.

Frequently Asked Questions about crew-setup

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

FAQPage Schema
How do I set up the crew workflow in an existing repository?

Invoke the crew-setup skill or run /crew:init, which runs nine resumable phases tracked in .crew/STATUS.md. It detects the platform, asks about reviewer, tracker, and memory choices, then creates .crew/config.json, a CLAUDE.md, and a _verify/ smoke harness.

How do I resume an interrupted crew setup?

The setup reads .crew/STATUS.md and resumes at the first phase not marked done. It reports which phase you are on and what is outstanding before doing anything else, so resuming always beats restarting.

Does crew setup work on Windows and WSL?

Yes, platform.sh or platform.ps1 detects native Windows, Git Bash, WSL1, and WSL2 and records the result in config. It flags the three WSL pitfalls: slow repos under /mnt/c, localhost not reaching the Windows host under WSL2, and CRLF line endings breaking shell scripts.

Which ticket trackers does crew setup support?

It supports local files, Jira, ServiceDesk Plus, and Obsidian Kanban boards. Jira and ServiceDesk Plus are only offered when their MCP tools are actually reachable, and Obsidian requires an existing vault directory on the machine.

Why does crew setup stop after each phase instead of finishing at once?

Each phase ends with something the user can verify personally, and stopping prevents building later phases on top of unverified work. Chaining phases without approval is explicitly disallowed so a half-working setup cannot be marked done.