project-checkup

Generate a prioritized health report with the next concrete action first.

Updated Nov 8, 2025
One-click install
npx skills add https://github.com/berad217/human-training --skill project-checkup-berad217
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-checkup
Source: https://github.com/berad217/human-training/tree/main/skills-source/project-checkup
Command: npx skills add https://github.com/berad217/human-training --skill project-checkup-berad217

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Returning to a hobby software project after a weeks- or months-long break often feels like cold-starting a stranger's codebase, with no clear idea of what was in progress, current project state, or what to work on next. This Skill eliminates that re-entry friction by generating a prioritized, state-aware health report with your next concrete action listed first.

Core Features & Use Cases

  • State-aware routing: Runs only the relevant audits for your project's current activity level (active, dormant, abandoned) to avoid wasting time on unnecessary checks.
  • Unified health report: Combines workflow orientation, robustness audits, friction scans, and a next-move inventory into a single easy-to-digest output.
  • Use case: Ideal for hobby projects you haven't touched in months, right before starting a new sprint, or any time you're unsure what to work on next.

Quick Start

Invoke the project-checkup skill in your AI coding agent to receive a full project health report with your highest-priority next action listed at the top.

Frequently Asked Questions about project-checkup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I figure out what to work on next when returning to a dormant hobby project?

To figure out the next step for a dormant hobby project, run a project health check to receive a prioritized report with your next concrete action surfaced first. This eliminates re-entry friction by auditing the codebase state and workflow inventory.

What is a project health check and when do I need one for my codebase?

A project health check is a state-aware audit that combines workflow orientation, robustness checks, and friction scans into a unified report. You need one when returning to a project after a multi-week break, starting a new sprint, or lacking an obvious pending task.

How to start sprint planning for a hobby project with no obvious pending work?

Start sprint planning by generating a next-move inventory that scans the codebase for friction and robustness issues. This produces a prioritized health report routing only relevant audits based on project activity levels to avoid unnecessary work.

Can I use this workflow audit on abandoned software projects or only active ones?

You can use this workflow audit on abandoned, dormant, and active software projects. It applies state-aware routing to run only the relevant audits for the specific activity level, avoiding wasted time on unnecessary checks for abandoned codebases.

What's the best way to reduce re-entry friction for a dormant codebase?

The best way to reduce re-entry friction is to generate a state-aware health report that surfaces your next concrete action first. By combining workflow orientation and friction scans, it quickly orients you to the current codebase state without manual investigation.