harnessloop-statuslisted

Use when the user references harnessloop:status, asks for Harnessloop status, wants to inspect the active goal, round, evidence health, open handoffs, control state, environment state, self-audit state, next proposed action, or blocking reason. This skill is strictly read-only and must not mutate files or continue work.
litianyi-007/harnessloop · ★ 0 · AI & Automation · score 67

Install: claude install-skill litianyi-007/harnessloop

# Harnessloop Status Read Harnessloop state safely. This skill reports current loop state; it must not create files, update contracts, archive handoffs, run business execution, or continue the task. ## Input Contract Accept an explicit skill invocation such as `$harnessloop-status`, or natural language asking for current Harnessloop state. Treat `harnessloop:status` and `harnessloop status` as natural-language aliases only; `$harnessloop:status` is not a valid skill invocation. Useful input includes: - `target-project`: defaults to the current working directory. - Optional state path, usually `.harnessloop/state/current.md`. - Optional scope: active goal, active round, evidence, handoffs, control, environment, self-audit, or next action. If `.harnessloop/` is missing, report `not-initialized` and suggest `$harnessloop-init`. Do not initialize it from this skill. If `.harnessloop/` exists but `check_setup.py` reports `complete: false`, report `setup-incomplete`, surface `field_todo_count` and `selfcheck_todo_count` and every non-`filled` file's `missing_sections`, and suggest `$harnessloop-setup`. Do not run the wizard from this skill. ## Processing Contract 1. Read `.harnessloop/state/current.md` first when present. 2. Run `python3 -B <plugin-root>/skills/harnessloop-loop/scripts/check_setup.py --project <target-project> --json` (the `-B` flag, or `PYTHONDONTWRITEBYTECODE=1`, guarantees no `__pycache__` bytecode is written, keeping this step strictly read-only). If i