mcpbeat

Ralph Specum Status

tzachbon/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.

463 tokens
context cost
the whole folder, loaded on every use
2
files
instructions only
0
copies elsewhere
how many repositories repackaged it
432
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/tzachbon/smart-ralph --skill ralph-specum-status

The instruction itself

4 sections, as written by the author

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

  • Resolve configured roots.
  • 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.
  • Read specs/.current-epic when present and summarize epic status.
  • For each spec directory, inspect:
  • .ralph-state.json
  • research.md
  • requirements.md
  • design.md
  • tasks.md
  • If tasks.md exists, count completed and incomplete tasks.
  • Group results by spec root.
  • 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 approve the current artifact, request changes, or continue to the named next step.

How to use it

Copy the folder

Take tzachbon/ralph-specum-status from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.