RequirementsHub Resident
Requirements intelligence that never leaves your machine
Resident is RequirementsHub's scoring engine, delivered as a Claude Skill. Your documents are parsed and read locally — only an anonymized structural summary is ever sent to RequirementsHub for scoring. No document text, titles, or descriptions leave your environment.
What you're actually paying for
Resident isn't a download you pay for once — it's ongoing access to three things: a license key that authenticates every analysis against RequirementsHub's scoring engine, the BABOK-aligned engine itself (deterministic, continuously updated detection rules), and a generated report — Executive Summary, six scored dimensions, and prioritized gap findings — produced fresh from your current documents every time you ask.
Once generated, your report is a real Claude Artifact — viewable, editable, and exportable to Word or PDF directly in the conversation.
How it works
- 01
Share your documents with Claude
Drop your requirements documents into a conversation with Claude. Nothing is uploaded to RequirementsHub.
- 02
Resident parses locally
Parsing and entity extraction run on your machine, inside the skill's own code execution sandbox.
- 03
Only a skeleton is transmitted
A validated structural skeleton — anonymized IDs, salted hashes, boolean flags, zero free text — is sent to RequirementsHub.
- 04
The deterministic engine scores it
BABOK-aligned detection rules run against the skeleton. Zero AI calls in scoring itself, so the same input always returns the same result.
- 05
Results re-hydrate locally
Scores and findings are mapped back to your real entity names on your machine, producing a full Requirements Intelligence Report with an Executive Summary.
See a real report
Overall Project Health
66/100Developing
- Requirements Integrity
- 75
- Developing
- Traceability Health
- 60
- Developing
- Outcome Readiness
- 50
- Needs work
- Risk Health
- 72
- Developing
Critical · 1 finding
Objective “Reduce manual data entry time” has no supporting requirements.
→ Recommended fix: Define at least one requirement that explicitly supports this objective.
Real output from Resident's own test pipeline — not a mockup.
What never leaves your environment
Never transmitted
- Requirement, objective, and stakeholder text and titles
- Descriptions, notes, and free-form content
- Document files, file names, and raw excerpts
What does get sent
- Entity counts by type
- Category and enum values
- Salted-hash identifiers
- Boolean structural signals
The full skeleton schema and licensing terms ship inside the skill package (SKELETON-SCHEMA.md and LICENSE-AND-PRIVACY.md) — see the Resident reference page to download it, or read our data handling policy.
Pricing
Resident is included free with RequirementsHub Pro and Consultant subscriptions. Standalone licenses are available below.
Resident
RequirementsHub Resident
Local, privacy-first scoring for your AI client. Includes a Resident license key — it does not include Pro app access.
Availability
- Claude SkillAvailable now
- ChatGPT AppComing soon
- Microsoft Copilot AgentComing soon
Frequently asked
- Does my data ever touch RequirementsHub's servers?
- No document content does. Only the anonymized skeleton described above — counts, enums, salted-hash IDs and boolean signals — is transmitted for scoring.
- What am I paying for?
- Your license key, continuous access to the scoring engine, and the reports it generates — not a file you download once.
- What if I don't have a license?
- Local parsing and extraction still work. Scored analysis specifically requires a license key to authenticate against the engine.