Agent Skills
› tzachbon/smart-ralph
› ralph-specum-requirements
ralph-specum-requirements
GitHub协调Ralph Specum需求阶段,委派产品代理生成需求文档。需明确触发,读取研究上下文,更新状态并请求审批或进入设计。
Trigger Scenarios
用户明确要求使用 $ralph-specum-requirements
用户明确要求Ralph Specum在Codex中运行需求阶段
Install
npx skills add tzachbon/smart-ralph --skill ralph-specum-requirements -g -y
SKILL.md
Frontmatter
{
"name": "ralph-specum-requirements",
"metadata": {
"action": "requirements",
"surface": "helper"
},
"description": "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."
}
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.mdwhen present,.progress.md, and the current state. - Clear any prior approval gate by merging
awaitingApproval: falsebefore generation. - Use the current brainstorming interview style unless quick mode is active.
- Delegate requirements generation to a
product-managersub-agent. Pass research context, goal, and interview results. The sub-agent writesrequirements.md. Do NOT write requirements.md yourself. - Read the sub-agent's output and validate it exists.
- Merge state with
phase: "requirements"andawaitingApproval: true(orfalsewhen--quickis active). - Update
.progress.mdwith 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, namerequirements.mdand summarize the requirements briefly. - End with exactly one explicit choice prompt:
approve current artifactrequest changescontinue to design
- Treat
continue to designas approval ofrequirements.md.
Version History
- 1b33202 Current 2026-07-05 09:17


