routines
Start here
Say in one line what you'll make: a ready-to-paste /schedule line for each routine you pick, adapted to this repo.
What the champion typed after the command, if anything: $ARGUMENTS
If that's blank, run the guided flow below. If it has text, or they already told you some of this, use what it answers and ask only for what's still missing.
Before asking, say that /schedule needs a claude.ai login, isn't available with an API key or through a cloud provider, and can be turned off by an org. Note this folder's name so the lines can name the repo.
Then ask:
- Which routines? Use AskUserQuestion with two questions in one call, each letting them pick more than one. Weekly: "Weekly patterns digest" (recommended) and "Weekly question digest". Monthly or quarterly: "Stale guidance check" (recommended), "Monthly lead update", and "Quarterly maturity check".
- What's your timezone, and do you want a time of day? A plain question. The default is no set time.
- Only if they picked the question digest: which issue tracker should it read? A plain question.
How to ask: one question at a time, or a small batch of related choices, and wait for the answer before you go on. When the answer is one of a few options, use the AskUserQuestion tool with up to four options, the recommended or most common one first. If AskUserQuestion isn't available, give the same options as a short numbered list and wait for the answer. Ask a plain question only when the answer is open, such as a goal or team names, and suggest a default. When a question asks how someone works or what score fits, mark no option as recommended. A consent question, about reading through git, gh, chat, or a connector, or about writing a file, puts the safe choice, such as "Not yet", first as the recommended one. A pick counts as a yes only for the exact read or write it names. If the champion says "go", list the defaults you'll take for the remaining questions, then take them, but still stop at every consent question. A default never counts as a yes.