tech-lead-setups
Tech Lead Setup
Stand up the project skeleton so every developer can start their first card without blocking anyone. This is the Sprint 0 scaffold: structure, tooling, hooks, and stubs, executed from the decisions already made upstream.
This runs after task-breakdown (the cards, including any Sprint 0 scaffold cards, exist) and before coding-standard (the standards describe the skeleton this skill creates). Two phases: grill to lock the setup, then execute it.
CI workflows are not written here. github-project-init owns .github/, and its CI runs the aggregate check command this skill defines.
Running project (adopt mode). If the repository already has code, do not scaffold. Audit what exists against the list in Phase 1, show the gaps, and add only the missing pieces, most often the test harness. Never restructure existing folders.
Phase 1: Grill
Read docs/technical-specs/ first; it is the source of truth for this scaffold. The repository structure, tech stack, module definitions, and environment configuration are already decided there: read the repository-structure spec for the directory tree, the tech-stack spec for the runtime, tooling, and versions, the module-definitions spec for the per-module surface, and the environment-configuration spec for the env vars. In the current layout these are 03-, 04-, 05-, and 11-; in an older layout, match them by topic name. Also read the Sprint 0 cards in docs/task-breakdown/sprint-0.md (or docs/TASK_BREAKDOWN.md in an older project), the endpoint contracts in docs/api-specs/, and any conventions in CLAUDE.md. Pull every decision you can from these and confirm it rather than re-deciding; the grill only fills genuine gaps. If docs/technical-specs/ does not exist, say so and run technical-spec first, because scaffolding without it means inventing architecture the rest of the pipeline has not agreed to.
Interview the user one question at a time, recommending an answer each, until the setup is fully pinned. This is a grill, not a form: ask the live question, give your recommendation and the one reason it wins, wait, then walk the branch that answer opens before starting the next topic. Don't paste the list below as a questionnaire.