groove-utilities-task-doctor
Outcome
All task backend health checks pass. User knows if the task backend is correctly configured, installed, and reachable.
Acceptance Criteria
- Each check is reported with ✓ or ✗
- Each failure includes a specific remediation command
- Checks cover config, CLI installation, and reachability
Checks (run in order)
.groove/index.mdexists at git roottasks.backendkey is present and has a valid value (beans,linear,github, ornone)- If
tasks.backend: none— report no-op and exit (all green) - Backend CLI is installed:
beans:beans versionlinear:linear --versiongithub:gh --version
- Backend-specific config file exists:
beans:.beans.ymlat git rootlinear: auth token configuredgithub:gh auth status
- Backend is reachable (lightweight read operation):
beans:beans list --json(or equivalent)linear: list one issuegithub:gh issue list --limit 1
AGENTS.mdcontains<!-- groove:task:start -->section (iftasks: beans)
Remediation hints
| Failure | Remediation |
|---|---|
.groove/index.md missing | /groove-utilities-task-config or /groove config |
| Backend not installed | /groove-utilities-task-install |
.beans.yml missing | /groove-utilities-task-install (will scaffold) |
| Backend unreachable | Check auth / network, re-run /groove-utilities-task-install |
AGENTS.md section missing | /groove install |
Constraints
- Report all checks even if an early one fails — give the full picture
- Do not attempt to fix issues — report and suggest only
- If
tasks: none, show one green line: "tasks: none — task commands disabled" and exit