pushup-setup

name	pushup-setup
description	First-time setup for The Push-Up Challenge tracker. Use when the user wants to start tracking the challenge, set up push-up logging/nagging, or hasn't created a config yet. Examples - "set up the pushup challenge", "/pushup-setup", "start my push-up challenge tracker".
user_invocable	true

pushup-setup

Set up the user's Push-Up Challenge tracker config. This is a quick, friendly interview. The tracker only logs + nags locally — it never submits to the official website.

Steps

1. Ask which challenge they signed up for. Use AskUserQuestion with two options:

   • Half challenge — the lighter commitment (default total ≈ 1,654 reps).
   • Full challenge — the full commitment (default total ≈ 3,249 reps). Tell them plainly: this only affects the minimum pace the tracker nags toward. Either way it's a floor, not a stick — overachieving is welcome, skipping is guilt-free. Mention the numbers are rough defaults; they can override with their exact total from the site.

2. Confirm dates (optional). Default start = today, end = start + 23 days (the standard ~24-day June run). If they tell you different dates, use them.

3. Write the config:

   python3 ~/.config/pushup-challenge/tracker.py --init --challenge <half|full> [--total N] [--start YYYY-MM-DD] [--end YYYY-MM-DD]
   

   (Add --force only if overwriting an existing config.)

4. Relay the plan it prints — the per-day minimum, the comfy-max, and the no-guilt reminder. Then tell them how to log day to day: /pushup-log 20, or just describe a set in chat. To check standing any time: /pushup-log with no number, or "pushup status".

5. If they want automatic nagging (Claude Code only), point them at the Stop-hook snippet in the kit's hooks/README.md — it makes the assistant gently ask them to log a set during the day. In Codex, logging is manual via the /pushup-log prompt.

Keep the whole thing short and upbeat. The point is to make showing up easy, not to add pressure.