← ClaudeAtlas

team-kickofflisted

Bootstrap a brand-new project with the full agent council from day zero — gather the vision, scan the (possibly empty) directory, run the council on the vision, and write an initial `.council/project-profile.md` and CLAUDE.md. Use when starting a new project and you want multi-perspective input before the first line of code.
TokiDEV/team-skills · ★ 4 · AI & Automation · score 77
Install: claude install-skill TokiDEV/team-skills
# team-kickoff New-project bootstrap. Brings the council in before there's any code, so the project's direction and conventions are shaped by the full team rather than defaulted. Reuses `team-council` internally. ## Flow ``` 1. Gather vision → ask the user: what, who, why 2. team-scan → run on the directory (even if empty — detects global tools) 3. Dispatch council → full council with the vision as decision context 4. PO synthesis → team input → project brief 5. CEO approval → present brief, iterate 6. Write foundations → .council/project-profile.md + initial CLAUDE.md 7. Hand off → existing project setup / scaffolding workflow ``` ### 1. Gather vision Ask the user for the project vision if not already given: - **What** — what is being built, in one or two sentences. - **Who** — the users and their context. - **Why** — the problem, the value, the ambition. ### 2. Scan Run `team-scan` on the target directory. On an empty directory it still detects globally available skills, agents, and MCP tools, and records the intended stack from the vision. ### 3. Council on the vision Invoke `team-council` with the vision as the decision context. The roles debate the shape of the project — scope, architecture direction, UX principles, first-principles soundness, and ambitious alternatives — before anything is committed. Run the council through its synthesis but **skip its CEO gate**: step 5 is the single gate for kickoff. ### 4. Synthesis → bri