ralph-specum-status
This skill should be used only when the user explicitly asks to use `$ralph-specum-status`, or explicitly asks Ralph Specum in Codex for status or active spec progress.
npx skills add majiayu000/claude-skill-registry --skill ralph-specum-status --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Ralph Specum Status Use this to report Ralph state across configured spec roots. ## Contract - Read `.claude/ralph-specum.local.md` when present - Default specs root is `./specs` - `.current-spec` lives in the default specs root - Hidden directories do not count as specs ## Action 1. Resolve configured roots. 2. Read `.current-spec` to identify the active spec. - If `.current-spec` is missing or empty, report that there is no active spec and continue listing specs across roots. 3. Read `specs/.current-epic` when present and summarize epic status. 4. For each spec directory, inspect: - `.ralph-state.json` - `research.md` - `requirements.md` - `design.md` - `tasks.md` 5. If `tasks.md` exists, count completed and incomplete tasks. 6. Group results by spec root. 7. Show the active spec, current phase, backlog state, approval state, granularity when present, and which artifacts exist. ## Output - Specs in the default root can be shown by name. - Specs in other roots should include the root suffix for disambiguation. - Include the next likely command when it is obvious. - If an epic is active, include the next unblocked spec. - If approval is pending, explicitly tell the user to approv
- Contract
- Action
- Output
What does the ralph-specum-status skill do?
This skill should be used only when the user explicitly asks to use `$ralph-specum-status`, or explicitly asks Ralph Specum in Codex for status or active spec progress.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill ralph-specum-status --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.