GetRequirement

Fetch and display requirement metadata from local spec files by ID.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Cure-HHT/hht_diary --skill getrequirement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GetRequirement
Source: https://github.com/Cure-HHT/hht_diary/tree/main/tools/anspar-cc-plugins/plugins/simple-requirements/skills/get-requirement
Command: npx skills add https://github.com/Cure-HHT/hht_diary --skill getrequirement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill enables Claude to retrieve the full text and metadata of a system requirement by its ID. It helps when you need to verify content, perform reviews, or understand dependencies without leaving the chat.

Core Features & Use Cases

  • Full text and metadata retrieval: Fetches the complete requirement text plus its metadata (ID, Level, Implements, Status, Hash, Source).
  • Offline, local lookup: Parses local spec files (no external API calls) for offline reliability.
  • Flexible ID handling: Accepts both REQ-d00027 and d00027 formats; case-insensitive.
  • Traceability and validation support: Enables quick verification during design reviews and change tracking.

Quick Start

Use the GetRequirement skill with input REQ-d00027 (or d00027) to retrieve the full text and metadata from the spec files on your device.

Frequently Asked Questions about GetRequirement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fetch a requirement by its ID from local spec files?

Use GetRequirement with a requirement ID in either REQ-d00027 or d00027 format to fetch the complete requirement text and metadata from your local spec files. The Skill performs offline lookup with no external API calls, returning ID, Title, Level, Implements, Status, Hash, Body, and Source fields instantly.

Can I look up requirements offline without making API calls?

Yes. GetRequirement parses local spec files on your device for offline, reliable requirement lookup. No external APIs are called, making it suitable for air-gapped environments or when you need instant access without network dependencies.

What metadata does a requirement lookup return?

Requirement lookup returns full metadata including ID, Title, Level, Implements, Status, Hash, Body, and Source. This integrated data enables verification during code reviews, traceability tracking, and understanding requirement dependencies without switching tools.

Does GetRequirement work with both REQ- prefixed and unprefixed requirement IDs?

Yes, GetRequirement accepts both REQ-d00027 and d00027 formats, and handles IDs case-insensitively. This flexible parsing eliminates formatting friction during requirement verification and change-tracking workflows.

How do I verify requirement content during code reviews?

Query the requirement by ID using GetRequirement to retrieve full text and metadata instantly within your chat. This enables quick verification of requirement details, dependencies, and status without leaving your review workflow.

What happens if I need to track requirement changes and dependencies?

GetRequirement integrates with the system's validation, hash, traceability, and change-tracking pipelines. The returned metadata—including Hash and Implements fields—enables you to track requirement evolution and understand upstream and downstream dependencies.