the-own-lab/requirements
skills/requirements/SKILL.md
Elicit and structure requirements through systematic questioning. Use when a feature needs to be scoped before design.
testing
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add the-own-lab/Claude-company-of-one requirementsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 10:05 PM35.1s1 file scanned
SKILL.md
- name:
- requirements
- description:
- Elicit and structure requirements through systematic questioning. Use when a feature needs to be scoped before design.
Requirements Elicitation
Systematic requirements gathering for the product-owner agent.
Process
- Ask clarifying questions ONE AT A TIME — Do not overwhelm with a list. Ask one question, wait for the answer, then ask the next. Each question should build on previous answers.
- Identify implicit requirements — Listen for unstated assumptions. Surface them explicitly and confirm.
- Structure into template — Once sufficient understanding is reached, produce the requirements document.
Requirements Template
Summary
A single paragraph describing what the feature does and why it exists.
Acceptance Criteria
A numbered list of testable criteria. Each criterion must be verifiable with a concrete test — no subjective language.
- Bad: "The page should load quickly."
- Good: "The page loads in under 2 seconds on a 3G connection."
Scope
In scope:
- Explicit list of what this feature includes.
Out of scope:
- Explicit list of what this feature does NOT include, especially things someone might assume are included.
Constraints
Technical, business, or timeline constraints that affect implementation choices.
Open Questions
Unresolved items that need answers before or during implementation.
Template
Read the template before producing output:
Read ${CLAUDE_PLUGIN_ROOT}/templates/REQUIREMENTS.md
Quality Checks
Before finalizing a requirements document, verify:
- [ ] Every acceptance criterion is testable with a concrete pass/fail condition.
- [ ] Scope is explicit — both in-scope and out-of-scope are defined.
- [ ] No technical implementation details have leaked into requirements (requirements describe WHAT, not HOW).
- [ ] Open questions are captured rather than silently assumed away.
Related Skills
the-own-lab/write-brief
documentation
VerifiedTrustedCommunity
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/verify
development
VerifiedTrustedCommunity
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/update-docs
documentation
VerifiedTrustedCommunity
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/spec-writing
content-media
VerifiedTrustedCommunity
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
SKILL.mdUpdated Apr 22, 2026