Close batches of graalvm-reachability-metadata pull requests that either have the `human-intervention` label or failing CI, and revert their linked issues by clearing assignees and moving project status to `Todo`.
Close or reject pull requests that add support for a new library in graalvm-reachability-metadata. Use when asked to close a `library-new-request` PR and roll the linked issue back by removing assignees and changing project status from `In Progress` to `Todo` without downgrading `Done`.
Create, update, or manage decision records in homeracker. Use this skill when comparing alternative solutions and choosing one, changing behavior of CLI tools or build processes or model conventions, making trade-offs that future contributors need to understand, or superseding a previous decision. USE FOR: creating new decision records, looking up existing decisions, superseding outdated decisions, documenting rationale behind tooling or architecture choices. DO NOT USE FOR: routine config changes, version bumps, dependency updates, or changes that are self-explanatory from the code or commit message.
Relentlessly interview the user about a plan or proposal — release plans, refactors, model rollouts, architectural changes — until every branch of the decision tree is resolved. Then fold the resolved plan into the right artifact: a decision record, a release roadmap, a PR description, or a tracking issue. USE FOR: stress-testing a plan before execution, pressure-testing scope and trade-offs, surfacing hidden assumptions, drafting MakerWorld/release rollouts, shaping a refactor or migration before code is touched, producing the artifact the plan needs. DO NOT USE FOR: grilling a built model's parameters and geometry (use grill-my-model), writing OpenSCAD code (use the @makerworld-model agent), routine config/version/dependency bumps.
Universal challenge tracker with flexible cadence, intelligent insights, and cross-challenge learning detection. Use when user wants to track any personal challenge - learning, habits, building, fitness, creative, or custom. Supports daily, weekly, or N-day check-ins with type-adaptive preferences, backlog, and context files.
Web app MVP launch checklist knowledge. Auto-triggered when conversation involves "launch readiness", "MVP checklist", "production ready", "go live", or pre-launch verification. Provides the 10-point criteria for what counts as "done" in each area. Based on "Realistic MVP Launch Checklist (from building 30+ apps)".
Use when working in this Spec Kit repository and the user wants a requirements-quality checklist for the active feature, generated from the current spec, plan, and tasks artifacts.
Use when working in this Spec Kit repository and the user wants to execute the active tasks.md plan, respecting checklist gates, task dependencies, and phase-by-phase implementation.