keelokit

Entry point of the Keelokit harness. Use when the user says "keelokit", "/keelokit", "dónde estamos", "qué sigue", "what's next", "estado del proyecto", "retomemos", or opens a session in a Keelokit p

SKILL.md

GitHub

Keelokit — where are we, what's next

Answer three things, in this order, in at most ten lines:

  1. Where we are — gate or backlog progress.
  2. What's next — the one concrete next action.
  3. What waits for the human — pending approvals or decisions, as a short package (options + recommendation).

Procedure

  1. Find the project root: the nearest directory with .keelokit/ (walk up from the cwd).
    • None found, empty folder or no code → offer a new product (/keelokit:project-new).
    • None found, existing code → offer to bring it under the harness (/keelokit:project-adopt). Do not install or scaffold anything without the user's answer.
  2. Run python3 .keelokit/bin/doctor.py --brief. If Python is missing, say so and stop.
  3. Route:
    State Next action
    A gate is pending Continue /keelokit:project-new (new product) or /keelokit:project-adopt (existing repo) from that gate
    Harness errors reported /keelokit:check-health
    The profile is unknown, or the doctor reports profile drift /keelokit:check-health to bring .keelokit/profile.toml up to date
    The project's harness (_commit in .keelokit/answers.yml) is older than the plugin Offer /keelokit:harness-upgrade
    The profile has mobile and no [local] block (the doctor warns RUN-1), or the user wants to see the app Offer /keelokit:run-local (macOS)
    Blocking context gaps Ask the gap questions (owner = the user) and update docs/context/
    Several sessions or worktrees running, or the user asks how they are doing /keelokit:coordinate (python3 .keelokit/bin/status.py)
    The CI of main is red or cancelled twice in a row (python3 .keelokit/bin/ci.py health) ci.py jobs for the failing job and step; fix before starting stories
    Stories ready Propose /keelokit:build-story on the first ready story (or N of the same wave)
    A wave just finished, or a release is near Propose /keelokit:check-bugbash
    A wave is done and its bug bash is clean Propose /keelokit:ship-release (and /keelokit:check-security before the first production release)
    The skeleton exists but docs/deploy.md doesn't, or an environment's checklist has open steps Propose /keelokit:ship-setup
    Nothing ready, backlog not empty Show which dependency blocks the next wave
    Backlog empty or done Offer /keelokit:plan-backlog for the next slice, or a new feature intake
  4. If the user already said what they want, skip the report and do it.
  5. Offer the dashboard (/keelokit:project-dashboard) with the answer, and open it without asking when a gate is pending or the user is resuming a half-finished run: it shows the stages, what waits for their review and the next step. To share the project's state with someone or keep a copy, it's /keelokit:project-report (read-only, every stage and document).