Sign in Publish

MCP servers Skills Toolkits Why AgentStack Sell Docs

SKILL verified MIT Self-run

Ralph Specum Requirements

skill-tzachbon-smart-ralph-ralph-specum-requirements · by tzachbon

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.

— No reviews yet

0 installs

8 views

0.0% view→install

Install

$ agentstack add skill-tzachbon-smart-ralph-ralph-specum-requirements

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

✓ Prompt-injection patterns
✓ Secret / credential exfiltration
✓ Dangerous shell & filesystem operations
✓ Untrusted network calls
✓ Known-malicious package signatures

What it can access

✓ Network access No
✓ Filesystem access No
✓ Shell / process execution No
✓ Environment & secrets No
✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Ralph Specum Requirements? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.

Sign up to claim

About

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Author: tzachbon
Source: tzachbon/smart-ralph
License: MIT

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

v0.1.0 Imported from the upstream source.