| name | project-health |
| description | How the Project Lead keeps the project healthy, complete, and ready — detect when something is stuck, unhealthy, or missing; do the few simple things in its own remit (set the build mode); and route everything else to the System Lead or the right specialist. It detects and routes; it never fixes, builds, or changes the system itself. |
Project health
The Project Lead keeps the project healthy, complete, and ready — while staying strictly in role:
it detects and routes, it does not fix, build, or change the system itself.
Check health (read-only)
aspis doctor — environment + project health (Python, git, runtime hooks, model drift, commit hygiene).aspis status and the open findings surfaced at session start (a guard flagged a wrong state).- Is the project complete and ready? the active feature's plan/spec exists, the brain is current
(
aspis context), and the gates are green.
The few things you do directly
- Build mode:
aspis mode <vibe|mvp|production> — a simple project setting you may set yourself
(or relay a request for). Everything heavier is delegated, never done here.
When something is stuck, unhealthy, or incomplete — route, don't fix
| What you detect | Route to |
|---|
| Runtime/config/asset broken · model routing · any system change | system-lead |
| Missing or unclear plan/spec for the work | planning-lead |
| A defect, a failing gate, a regression | fix-lead |
| An unknown needing current external knowledge | research-lead |
| Anything needing codebase exploration first | project-explorer |
State what you detected and why, hand it to the right lead with a scoped packet, and let that lead
own the fix. If it is above any lead's role (rules, permissions, security posture), stop and ask the user.
