devmesh-in

autopilot

EXPERIMENTAL, opt-in only - one bounded tick of self-directed company operation (triage red gates, in-flight work, worries, CRs, then backlog; deliver; surface). Intended for the end phase of a product - backlog burn-down and polish after the main build exists - not for mainline development. Runs ONLY when the user types /autopilot (or wires it into /loop or /schedule themselves); never invoke this skill on your own initiative, and never treat phrases like "keep going" as an invocation.

release

Prepare a release for the owner to ship - verify the readiness list mechanically, then assemble the changelog, semver proposal, and release notes into the filled RELEASE-TEMPLATE, ending at a proposal entry on DECISIONS.md. Owner/CEO invoked only. Use when the user says /release, "prepare a release", "cut a release", or "are we ready to ship". It NEVER tags, publishes, or deploys - deploy is a manual owner step, always.

brainstorm

Run a company ideation engagement - parallel ideation-strategist agents diverge with different lenses (perspectives, inversion, extreme scaling, competitive positioning, journey friction), the CEO synthesizes and scores, and the client gets an options memo with a recommendation. Use when the user says /brainstorm, asks for ideas ("what should we build", "how could we solve X", "come up with approaches"), brings a fuzzy product direction, or when any engagement risks converging on the first workable idea.

company-init

Found the company in a NEW (greenfield) project autonomously - the founding spec, architecture, ownership map, frozen surfaces, and gates are all generated by the agents; the owner answers at most one question. Use when the user says /company-init or asks to set up claude-company in a fresh or nearly-empty repo. Existing codebase - use onboard. Note - /orchestrator self-initializes too; this skill exists for doing the founding explicitly.

feature

Run ONE feature through the company's full SDLC - spec (product-manager), spec-ready gate, sealed brief, tech-lead build with developers and QA screenshots, evidence verification, integration. Use when the user says /feature <description>, or asks to build a specific feature "properly" / "through the process" in a claude-company project. For a batch of work or ongoing operation, use /orchestrator; for tiny fixes just classify quick there.

onboard

Adopt claude-company into an EXISTING codebase autonomously - audit the repo, recover architecture and tribal conventions, auto-wire the real test/lint/build commands as gates, apply opinionated frozen-surface defaults, and generate the canon from evidence. Zero owner interviews; the owner gets a findings memo with veto rights. Use when the user says /onboard or asks to set up claude-company in a repo that already has code. Note - /orchestrator self-initializes too; this skill is the explicit, thorough version.

orchestrator

Become the CEO of this project's AI software company and deliver whatever the user asks - features, bugs, whole products - through tech leads who run their own developer and QA teams, with hard-gated verification. Use whenever the user says /orchestrator, asks to build/fix/ship ANYTHING in a project containing a company/ directory, gives work to parallelize, or returns to continue company-run work. The user is the client; the company does all process itself - prefer this over ad-hoc building here.

standup

The company standup - report current state from the company/ state files (done / in-flight / blocked / decisions-needed), gate status, open CRs, and top worries, without starting any work. Use when the user says /standup, "status?", "where are we", "what is in flight", or returns to a claude-company project and wants orientation before deciding anything.

Data & Documents Listed

cr

File or decide a change request against a frozen surface (schema, contracts, kernel, migrations, anything in company/frozen-surfaces.json). Use when the user says /cr, when a hook blocked an edit to a frozen surface and the change is genuinely needed, when an agent's report filed a CR that needs a decision, or when the user asks to "unfreeze"/"change the contract/schema/kernel".

gates

Run the project's full gate ladder (company/run-gates.sh) and stamp the result, or configure the gates themselves. Use when the user says /gates, "run the gates", "are we green", before any commit/merge in a claude-company project, or when a commit was hook-blocked for red/stale gates and you need current truth.