ralph-specum-requirements
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.
Install / Use
npx skills add tzachbon/smart-ralph --skill ralph-specum-requirementsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Product ManagementSupported Platforms
Tags
Our assessment of ralph-specum-requirements
ralph-specum-requirements scores 81/100 on our quality scale, 57th of 61 Product Management skills we index.
Its SKILL.md is 6.5 KB long, split into 7 sections and no code examples: a thorough specification that gives an agent plenty to work with.
It has 550 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so ralph-specum-requirements is actively maintained.
- Our last check on 2026-11-08 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
ralph-specum-requirements compared with similar skills
All 4 of these similar skills score higher than ralph-specum-requirements; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| ralph-specum-requirements (this skill)by tzachbon | 81 | 550 | 2mo ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 57d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 57d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 7d ago | SKILL.md |
| ad-creativeby coreyhaines31 | 100 | 60.1k | 7d ago | SKILL.md |
Frequently asked questions
- How do I install ralph-specum-requirements?
- Run
npx skills add tzachbon/smart-ralph --skill ralph-specum-requirements. The install tabs above show the steps for each supported agent. - Which AI agents does ralph-specum-requirements work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is ralph-specum-requirements safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is ralph-specum-requirements still maintained?
- The repository was last updated about 2 months ago, so ralph-specum-requirements is actively maintained.
Skill content
View source on GitHubname: ralph-specum-requirements
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.
metadata:
surface: helper
action: requirements
Ralph Specum Requirements
You are a coordinator, not a product manager -- delegate ALL work to a product-manager sub-agent.
Derive RALPH_CODEX_PLUGIN_ROOT from this loaded skill by resolving two parent directories from the SKILL.md directory. Never derive it from the project working directory.
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. - Run
phase_gate.py modethrough"$RALPH_CODEX_PLUGIN_ROOT/scripts/phase_gate.py"withSTATEand exact--quick, exact--interactive, or no flag. Reject both,-q, variants, and natural-language substitutes. - When
research.mdexists, require its artifact approval in interactive mode; exact quick mode continues with the validated file. When it is absent, record that there is no upstream research artifact and require no prior-artifact approval. - When
research.mdexists, require skill discovery pass 2 against the goal plus final research. When it is absent, require pass 1 against the goal alone. Run the applicable pass when the state lacks its revision. Select explicitly named skills and record harness-shadowed duplicates. - Load
"$RALPH_CODEX_PLUGIN_ROOT/skills/interview-framework-codex/SKILL.md", its required algorithm and domain-modeling references, and all selected domain contracts in both interactive and quick mode. In interactive mode, use its focused brainstorming method for critical user outcomes, scope exclusions, acceptance thresholds, and material non-functional requirements. Inspect existing behavior and terminology instead of asking. - Clear any prior approval gate by merging
awaitingApproval: falsebefore generation. - In interactive mode, require explicit
approve and delegate; in exact quick mode, recordbypassed_quick. In both modes, runphase_gate.py check-delegationwith the current loaded-manifest identity before creating the child. Apply the shared hard-transition invariant before requirements writer dispatch. A failedcheck-delegationin either mode ends this invocation before phase transition, child dispatch, or target-artifact write; after a normal-mode failure, the next explicit invocation creates a fresh manifest/interview identity and does not create an alternate quick bypass. After an exact--quickdelegation failure, the next explicit invocation reruns discovery, records a freshphaseSkillLoadand interview identity, and does not reuse a terminalbypassed_quickinterview or its discovery revision. Only a matching in-progresscollectingorawaiting_confirmationinterview is resumable. - Delegate requirements generation to a
product-managersub-agent. Pass the absolute helper path, state path, identity tuple, unique teammate dispatch identity, verbatim manifest, research context, goal, and interview results. The child reloads and records the manifest, passescheck-agent-writewith that unique identity, and 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 exact--quickis active). - Update
.progress.mdwith approved research context, user decisions, blockers, next step, skill discovery, and any epic constraints that must carry forward. - If spec commits are enabled, commit only the spec artifacts.
- In normal mode only, when the user selects
continue to prototype, treatrequirements.mdas approved and route to$ralph-specum-prototype --suggested --return-phase designwith the same resolved base path. Let that skill own prototype behavior and its return handoff.
Quick Prototype Gate
After requirements validation and review in quick mode:
- Select the oldest prototype that blocks design. If none blocks design, select the highest-risk grounded, falsifiable question from
research.mdandrequirements.md; let the prototype coordinator record a skipped result when no suitable question exists. - Make exactly one request:
$ralph-specum-prototype --quick --return-phase design. - Treat the request as
requestAttempt: 1. Keep it separate frombuilderExecutionAttempt; duplicate reuse, supersession, conflict resolution, skip, and lock failure consume the request without adding a builder execution. - Own every capture, conflict, verdict, retry, cleanup, and handoff decision. Ask no user questions and preserve unrelated active prototypes.
- Continue to design after every result. Treat a completed request as the one request on resume and never invoke the prototype skill a second time.
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 exact
--quick: Run the Quick Prototype Gate once, then continue directly into design for every outcome.
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. - When normalized
quickModeis false, end with exactly one explicit choice prompt:approve current artifactrequest changescontinue to designcontinue to prototype
- Treat
continue to designas approval ofrequirements.md. - Treat
continue to prototypeas approval ofrequirements.mdand route through$ralph-specum-prototypewithreturnPhase: design. - With exact
--quick, do not show this prompt; continue directly to design after the phase gates and single Quick Prototype Gate request complete. - During artifact review,
apply the changesimmediately delegates already-recorded feedback through a new unique dispatch, redisplays the artifact, and stays at this approval gate. Ask one focused change question only when no feedback is pending. Control-onlycontinue,proceed, andgo aheadapprove nothing.
Related Skills
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
ad-creative
60.1kWhen the user wants to write or judge ad creative, or asks which ad, hook, or angle to run or kill: headlines, primary text, and variations for Google, Meta, LinkedIn, and TikTok, fresh angles when creative fatigues. Test hypotheses name the metric, comparison, and expected direction.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
