codezeroexe/levels / skills/levels-status
levels-status
VerifiedShow one dashboard of every layer's current and target level, open gaps and pending actions, read from the project's LEVELS.md. Read-only and cheap. Use when the user runs /levels-status or asks where the project stands across the level skills.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 1.8 KB |
SKILL.md
View on GitHub---
name: levels-status
description: Show one dashboard of every layer's current and target level, open gaps and pending actions, read from the project's LEVELS.md. Read-only and cheap. Use when the user runs /levels-status or asks where the project stands across the level skills.
summary: See every level and open gap in one table
argument-hint: "[layer]"
model: haiku
---
# Levels status
Arguments: `$ARGUMENTS`
Read-only. This skill changes no file, spawns no agent and starts no other skill.
1. Read `LEVELS.md` in the project root. If it does not exist, say so and list the level skills that can create it, one line each, then stop.
2. If the arguments name a layer, show that layer's section in full and stop.
3. Otherwise print, in this order:
- A table from the levels block: layer, current level, target level, distance to target, open gaps, date last updated (the `Date:` line of the layer's section). Sort by distance to target, largest first.
- **Waiting on you**: every pending live step, manual action or unanswered question recorded in any section, with the layer it belongs to.
- **Accepted risks**: each one with its reason.
- **Stale**: any layer not updated in over 30 days, or older than the last commit in the project.
- **Not yet run**: level skills with no row in the block.
- **Flow**: if the block has a `flow:` row, show it on its own line (current phase, skills left) and keep it out of the table. It is written by `levels` and is not a layer.
4. End with one line: the layer furthest from its target. Do not recommend an action. `levels-next` does that.
If the levels block and a section disagree, show both values and say they disagree. Do not guess which is right.
Report only what the file says. Never estimate a level that has not been recorded.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 467k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |