Set up a project

Run on an explicit setup request, including a runtime-expanded invocation. Learn the project's needs; do not assume a team size, engineering role, scale, or architecture. This command configures the working agreement, not the application.

Use normal file and shell tools. No particular agent SDK, literal Skill tool, subagents, or model service is required. Operating-document authoring ships here; domain work requires the maintained domain-modeling companion, and GitHub creation/configuration requires github-repo-setup. Locate applicable companions through runtime skill discovery and read them completely. Missing or incompatible companions block their affected routes; ask before installing or replacing anything. Never silently substitute a different procedure.

Read-only procedure library

A delivery caller may discover this package and read tracker integration, especially its native-graph procedure, without invoking /setup-project or executing the setup steps below. Record the resolved source/revision and check semantic compatibility: native hierarchy/blockers, identity/pagination, conflict checks, additive writes and both-direction read-back. Target-project policy and exact caller approval govern operations; library access grants no setup, label/settings audit or mutation authority. The optional helper supports only its documented one-repository additive blocker scope; parentage, labels and unsupported cases stay with the procedure. Missing capability blocks the affected route rather than causing installation or silent prose fallback.

1. Inspect before asking or changing

Read applicable instructions and inspect Git status, remotes, existing entry points, operating/domain docs, ADRs, tracker conventions, changelog/version sources, release automation, and discoverable build/check commands. Follow document pointers. Inspect relevant organization requirements through authorized access; unavailable information remains unknown.

Read the documentation contract. Map every required responsibility to an existing authoritative file or proposed new file. A valid existing layout wins over the default layout. Inspect both AGENTS and CLAUDE files, symlinks, nested instructions, and any context map before choosing where to write.

Select local-only, new GitHub repository, or existing GitHub repository. A remote already present selects configuration, not another repository creation. Inspect permissions/settings read-only when the GitHub route is requested; local-only setup needs no GitHub login. Do not initialize Git, install tools, change labels, or write project documents during discovery.

Read model-use agreement to discover and propose none or exact bounded permissions without exercising them. Setup requires no model/service calls, startup, credentials, downloads or installations.