---
name: Ralph Specum Requirements
slug: ralph-specum-requirements
category: AI Engineering
description: Ralph Specum Requirements coordinates the requirements phase for an active spec and delegates the work to a product-manager sub-agent. Use it when explicitly running the Ralph Specum requirements step.
github: "https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-specum-codex/skills/ralph-specum-requirements"
language: Shell
stars: 527
forks: 47
install: "npx degit https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-specum-codex/skills/ralph-specum-requirements ~/.claude/skills/ralph-specum-requirements"
installs_to: ~/.claude/skills/ralph-specum-requirements
source_path: plugins/ralph-specum-codex/skills/ralph-specum-requirements/SKILL.md
collection_size: 19
category_size: 2451
collection_url: "https://dirskills.com/collections/tzachbon/smart-ralph"
added: 2026-08-26T05:12:05.988Z
last_synced: 2026-08-26T05:12:05.988Z
canonical_url: "https://dirskills.com/skills/ralph-specum-requirements"
---

# Ralph Specum Requirements

Ralph Specum Requirements coordinates the requirements phase for an active spec and delegates the work to a product-manager sub-agent. Use it when explicitly running the Ralph Specum requirements step.

**Install:**

```bash
npx degit https://github.com/tzachbon/smart-ralph/tree/main/plugins/ralph-specum-codex/skills/ralph-specum-requirements ~/.claude/skills/ralph-specum-requirements
```

## README

# 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

1. Resolve the active spec. If none exists, stop.
2. Read `research.md` when present, `.progress.md`, and the current state.
3. Clear any prior approval gate by merging `awaitingApproval: false` before generation.
4. Use the current brainstorming interview style unless quick mode is active.
5. **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.
6. Read the sub-agent's output and validate it exists.
7. Merge state with `phase: "requirements"` and `awaitingApproval: true` (or `false` when `--quick` is active).
8. Update `.progress.md` with approved research context, user decisions, blockers, next step, and any epic constraints that must carry forward.
9. 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`.