| name | ralphharness-requirements |
| description | This skill should be used only when the user explicitly asks to use `$ralphharness-requirements`, or explicitly asks RalphHarness in Codex to run the requirements phase. |
| metadata | {"surface":"helper","action":"requirements"} |
RalphHarness Requirements
Use this for the requirements phase.
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.
- Write or rewrite
requirements.md.
- Merge state with
phase: "requirements" and awaitingApproval: true.
- 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.
- In quick mode, 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.