Ralph specum requirements

Skill tzachbon/smart-ralph/plugins/ralph-specum-codex/skills/ralph-specum-requirements

Spec-driven development with smart compaction. Claude Code plugin combining Ralph Wiggum loop with structured specification workflow.

Install

npx -y skills add tzachbon/smart-ralph --skill ralph-specum-requirements

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

This skill should be used only when the user explicitly asks to use `$ralph-specum-requirements`, or explicitly asks Ralph Specum in Codex to run the requirements phase.

SKILL.md

2.2 KB, as published. Nobody here has run it

Ralph Specum Requirements

You are a coordinator, not a product manager -- delegate ALL work to a product-manager sub-agent.

Contract

Resolve the active spec by explicit path, exact name, or .current-spec
Require the spec directory to exist
Merge state fields only
Keep the Ralph disk contract unchanged

Action

Resolve the active spec. If none exists, stop.
Read research.md when present, .progress.md, and the current state.
Clear any prior approval gate by merging awaitingApproval: false before generation.
Use the current brainstorming interview style unless quick mode is active.
Delegate requirements generation to a product-manager sub-agent. Pass research context, goal, and interview results. The sub-agent writes requirements.md. Do NOT write requirements.md yourself.
Read the sub-agent's output and validate it exists.
Merge state with phase: "requirements" and awaitingApproval: true (or false when --quick is active).
Update .progress.md with approved research context, user decisions, blockers, next step, and any epic constraints that must carry forward.
If spec commits are enabled, commit only the spec artifacts.

Stop Behavior

Without --quick: STOP HERE. Display the walkthrough summary and approval prompt. Do NOT continue to design. Wait for the user to explicitly approve and request the next phase.
With --quick: Continue directly into design.

Output Shape

The result should include user stories, acceptance criteria, functional requirements, non-functional requirements, dependencies, exclusions, and success criteria.

Response Handoff

After writing requirements.md, name requirements.md and summarize the requirements briefly.
End with exactly one explicit choice prompt:
- approve current artifact
- request changes
- continue to design
Treat continue to design as approval of requirements.md.