Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/ralph-specum-status-tzachbon-smart-ralph
Metadata
Additional technical details for this skill
- action
- status
- surface
- helper
SKILL.md
Ralph Specum Status
Use this to report Ralph state across configured spec roots.
Contract
- Read
.claude/ralph-specum.local.mdwhen present - Default specs root is
./specs .current-speclives in the default specs root- Hidden directories do not count as specs
Action
- Resolve configured roots.
- Read
.current-specto identify the active spec.- If
.current-specis missing or empty, report that there is no active spec and continue listing specs across roots.
- If
- Read
specs/.current-epicwhen present and summarize epic status. - For each spec directory, inspect:
.ralph-state.jsonresearch.mdrequirements.mddesign.mdtasks.md
- If
tasks.mdexists, 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.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?