← ClaudeAtlas

project-spine-kickofflisted

Use when the user wants to set up Project Spine for a new project — phrases like "new client project", "kickoff", "create AGENTS.md from scratch", "generate agent instructions for this repo", "set up project context". Runs `spine init` → edits brief → `spine compile` → reviews outputs. For stale files use project-spine-drift.
PetriLahdelma/project-spine · ★ 2 · Code & Development · score 68
Install: claude install-skill PetriLahdelma/project-spine
# Kickoff flow for a new project **Goal:** produce the 21 canonical Project Spine files (`AGENTS.md`, `CLAUDE.md`, `.github/copilot-instructions.md`, `.cursor/rules/project-spine.mdc`, plus scaffold/QA/rationale docs) from a real brief + the current repo. ## Prerequisites — check before proceeding 1. CLI installed: `spine --version` returns `0.9.2-beta.0` or later 2. Current directory is the project root (has `package.json` or equivalent) 3. No `.project-spine/` directory yet (if there is, this is probably a **drift** scenario — switch to project-spine-drift) ## Step 1 — pick a template (optional but strongly recommended) List available starter templates: ```bash spine template list ``` Bundled templates cover these project types: - `saas-marketing` — marketing site (hero, pricing, customer pages, compliance) - `app-dashboard` — authenticated product with data tables, settings, role gating - `design-system` — component library, tokens, Storybook - `docs-portal` — technical documentation site - `api-service` — Node / TypeScript API service with health and readiness probes - `monorepo` — pnpm / Turborepo / Nx workspace guidance If the user mentions one of these project types, pick the matching template. If they describe something unusual (extension, CLI tool, data pipeline), skip the template and compile without it — the brief carries the intent. ## Step 2 — scaffold ```bash spine init --template <template-name> # or, without a template: spine init ``` This creates: