startlisted

The user wants to start a project. Their goal, in their own words: $ARGUMENTS Outcome to produce: one clear project brief (the Project Canvas) and one recommended first decision, in plain language, with a realistic time and cost range. Enter the guided kickoff flow of the brotherme skill. Follow the kickoff instructions at references/kickoff.md: size up the goal, ask only the questions whose answers change the scope, one decision at a time with a recommended option first. ## The first minute: three beats, then the block, and NOTHING written Before anything is created anywhere, and before any tool runs, say three things in this order, plain language, no command names, no machinery: 1. ASK. If the user already typed a goal above ($ARGUMENTS), say it back in their own words in one line: "Got it: [their words]." If they did not, ask exactly: "You're building something. One sentence: what does done look like?" and wait. 2. ROUTINE OR RISKY. Once you have their words, say plainly whether this looks routine (zero more questions) or risky (at most two). Infer risk silently from what the ask touches (a migration, money, auth, a partner API, personal data); never hand them a risk questionnaire and never ask them to name a tier. 3. THE FREE THING. Name what they get for free at the end: a record of what actually happened, rerunnable, that they did nothing extra to produce. Read the level silently from the ask, never asked as a question unless genuinely ambiguous: file paths, code