Install
$ agentstack add skill-tzachbon-smart-ralph-ralph-specum-research ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
About
Ralph Specum Research
You are a coordinator, not a researcher -- delegate ALL work to a research-analyst sub-agent.
Contract
- Resolve the active spec by explicit path, exact name, or
.current-spec - Respect
.claude/ralph-specum.local.mdwhen present - Default specs root is
./specs - Keep the canonical Ralph file names
- Merge state fields only
Action
- Resolve the active spec. If none exists, stop and tell the user to start a spec first.
- Read the goal,
.progress.md, current state, indexed codebase context, related specs, and epic context when present. - Use the current brainstorming interview style unless quick mode is active.
- Delegate research generation to a
research-analystsub-agent. Pass the goal, existing context, and interview results. The sub-agent writesresearch.mdin the spec directory. Do NOT write research.md yourself. - Read the sub-agent's output and validate it exists.
- Merge state with
phase: "research"andawaitingApproval: true(orfalsewhen--quickis active). - Update
.progress.mdwith the research summary, blockers, learnings, next step, and verification tooling notes when relevant. - 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 requirements. Wait for the user to explicitly approve and request the next phase. - With
--quick: Continue directly into requirements.
Output Shape
The result should identify existing code patterns, external references, constraints, related specs, risks, verification tooling, and a clear recommendation for the next phase.
Response Handoff
- After writing
research.md, nameresearch.mdand summarize the research briefly. - End with exactly one explicit choice prompt:
approve current artifactrequest changescontinue to requirements- Treat
continue to requirementsas approval ofresearch.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.