project-kickofflisted

# Project kickoff Turn a product idea into a repository whose method is already decided and whose board is already populated. The template `romain-nicod/kickoff` carries everything that does not change from one project to the next. **This skill carries what does**: reading a brief, deriving a backlog from it, sizing it against a real capacity, and naming the rules that are specific to this product. Never re-type what the template already holds. If a document exists there, it is filled in, not rewritten. --- ## 1. Establish the ground before writing anything Ask only what you cannot deduce, and ask it once: | Value | Why it matters | |---|---| | Project name and one-sentence pitch | Every document's first line | | GitHub owner and repository name | The scripts deduce it from the remote afterwards | | Stack | Picks the layer: `rails`, `static`, or `none` | | Development days, team size | Capacity — the number that governs the plan | | Demo or delivery date | Milestone dates, backwards from it | | Where the product specification lives | A document, a conversation, or nothing yet | If the user has no specification, say so plainly and offer to write one with them before touching GitHub. **A board generated from a vague brief is a hundred issues nobody trusts.** ## 2. Create the repository from the template ```bash gh repo create <owner>/<name> --template romain-nicod/kickoff --private --clone ``` Then fill `kickoff.yml` with the eight values and run: ```bash bin/kickof