load-requirements

Load archived requirements from the knowledge base with selectable detail options.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/nexus-a1/claude-skills --skill load-requirements
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: load-requirements
Source: https://github.com/nexus-a1/claude-skills/tree/main/skills/load-requirements
Command: npx skills add https://github.com/nexus-a1/claude-skills --skill load-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill loads full details of archived requirements from the knowledge base to inform current development work.

Core Features & Use Cases

  • Quick access to historical requirements, decisions, and lessons learned for reference.
  • Supports loading full requirements (spec, plan, and tasks) or specific sections, plus agent outputs for broader context.
  • Helps validate current implementations against past patterns and constraints.

Quick Start

Invoke the skill with an identifier to load archived requirements and choose a loading option.

Frequently Asked Questions about load-requirements

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

FAQPage Schema
How do I load archived requirements from a knowledge base for current development context?

You can load archived requirements from a knowledge base by invoking the skill with an identifier, then selecting a loading option such as a quick summary, full spec-driven triad, or targeted sections to provide context for current development.

What is the spec-driven triad format for retrieving historical project documentation?

The spec-driven triad format for historical project documentation consists of three files: spec.md, plan.md, and tasks.md, which together provide a complete specification, execution plan, and task breakdown for archived requirements.

Can I retrieve specific sections of an archived requirement instead of the full document?

Yes, you can retrieve specific sections of an archived requirement instead of the full document by selecting the targeted sections loading option, which also supports pulling optional agent outputs for broader context.

Do I need to search the knowledge base before loading archived requirements?

Yes, you need to search the knowledge base first to discover relevant work using a search command, after which you can load the full details of the archived requirements using the available loading options.

What's the best way to validate current implementations against past patterns and constraints?

The best way to validate current implementations against past patterns and constraints is to load quick summaries or full historical requirements from your knowledge base, allowing you to reference past decisions and lessons learned during active development.