init
CommandInitialise the planning seed and record the human team, roles, and escalation channels
@jpantsjohaInstall CommandDevelopment
Command
/bootstrap
Bootstrap the operating model and minimal delivery-planning seed (dry-run first, never overwrites)
> /plugin marketplace add jpantsjoha/ai-native-developer-experience> /plugin install join-the-team@join-the-team-marketplace
Command definition
bootstrap.mddescription: Bootstrap the operating model and minimal delivery-planning seed (dry-run first, never overwrites)
Run from the consumer project root. Claude resolves `${CLAUDE_PLUGIN_ROOT}` in this command’s content to the installed package; keep that path quoted. Do not change the working directory to the package or copy its maintainer adapters into the project. If the host has not resolved the path, load `operating-model-bootstrap` and locate its scripts beside the discovered skill file before running anything.
Bootstrap this repository with the team operating model:
1. Ask the user for the project name if not given. 2. Run the preflight dry-run:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/operating-model-bootstrap/scripts/bootstrap_operating_model.py" --dry-run --project-name "<project name>" .3. If the dry-run is clean, run the real initializer (same command without `--dry-run`). It preserves existing vision, workflow, roadmap, status, and changelog files while seeding missing ones. A different operating contract or surface adapter is a blocking conflict—report it instead of forcing replacement. 4. Ground the resulting `docs/operating-model/PROJECT-OPERATING-PROFILE.md`, `docs/VISION.md`, and `docs/operating-model/DELIVERY-WORKFLOW.md` from tracked evidence. Keep the initial roadmap and status free of invented work or progress. Record unknowns with an owner and the trigger that resolves them. 5. Run `/devex-charter:validate` and report the result. Keep the profile at `seed`; only R0/R1 and design work may proceed until the team resolves `active` controls.
Read more
description: Bootstrap the operating model and minimal delivery-planning seed (dry-run first, never overwrites)
Run from the consumer project root. Claude resolves `${CLAUDE_PLUGIN_ROOT}` in this command’s content to the installed package; keep that path quoted. Do not change the working directory to the package or copy its maintainer adapters into the project. If the host has not resolved the path, load `operating-model-bootstrap` and locate its scripts beside the discovered skill file before running anything.
Bootstrap this repository with the team operating model:
1. Ask the user for the project name if not given. 2. Run the preflight dry-run:
python3 "${CLAUDE_PLUGIN_ROOT}/skills/operating-model-bootstrap/scripts/bootstrap_operating_model.py" --dry-run --project-name "<project name>" .3. If the dry-run is clean, run the real initializer (same command without `--dry-run`). It preserves existing vision, workflow, roadmap, status, and changelog files while seeding missing ones. A different operating contract or surface adapter is a blocking conflict—report it instead of forcing replacement. 4. Ground the resulting `docs/operating-model/PROJECT-OPERATING-PROFILE.md`, `docs/VISION.md`, and `docs/operating-model/DELIVERY-WORKFLOW.md` from tracked evidence. Keep the initial roadmap and status free of invented work or progress. Record unknowns with an owner and the trigger that resolves them. 5. Run `/devex-charter:validate` and report the result. Keep the profile at `seed`; only R0/R1 and design work may proceed until the team resolves `active` controls.
Ships withjoin-the-team
**Shared ways of working for you, your team and your AI agents — from a new idea to a change running live.** join-the-team brings planning, delivery and ticket management, model selection, testing, independent review and release practices into one reusable
1325 skills
Stars on GitHub
Momentum
- stars in total
- 13
Other commands on join-the-team.
@jpantsjohaInstall Commandvalidate
CommandValidate the operating-model seed — manual binding, adapter drift, adoption state, checkpoint/evidence
@jpantsjohaInstall CommandMore commands from other plugins.
Auto-invoked
Auto-invoked
build
CommandImplement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
@addyosmaniInstall Command