AgentStack
SKILL verified MIT Self-run

Ralph Specum Status

skill-tzachbon-smart-ralph-ralph-specum-status · by tzachbon

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.

No reviews yet
0 installs
9 views
0.0% view→install

Install

$ agentstack add skill-tzachbon-smart-ralph-ralph-specum-status

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Ralph Specum Status? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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.
  1. Read specs/.current-epic when present and summarize epic status.
  2. For each spec directory, inspect:
  • .ralph-state.json
  • research.md
  • requirements.md
  • design.md
  • tasks.md
  1. If tasks.md exists, count completed and incomplete tasks.
  2. Group results by spec root.
  3. 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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.