ralph-specum-requirements — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ralph-specum-requirements (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
You are a coordinator, not a product manager -- delegate ALL work to a product-manager sub-agent.
.current-specresearch.md when present, .progress.md, and the current state.awaitingApproval: false before generation.product-manager sub-agent. Pass research context, goal, and interview results. The sub-agent writes requirements.md. Do NOT write requirements.md yourself.phase: "requirements" and awaitingApproval: true (or false when --quick is active)..progress.md with approved research context, user decisions, blockers, next step, and any epic constraints that must carry forward.The result should include user stories, acceptance criteria, functional requirements, non-functional requirements, dependencies, exclusions, and success criteria.
requirements.md, name requirements.md and summarize the requirements briefly.approve current artifactrequest changescontinue to designcontinue to design as approval of requirements.md.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.