spec-load

Load specification documents from .workflow/specs by category or keyword.

511|63|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/catlog22/Maestro-Flow --skill spec-load
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-load
Source: https://github.com/catlog22/Maestro-Flow/tree/main/.codex/skills/spec-load
Command: npx skills add https://github.com/catlog22/Maestro-Flow --skill spec-load

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The spec-load skill streamlines retrieving specification and guideline documents from the repository so agents and workflows receive the precise context they need without manual searching.

Core Features & Use Cases

  • Category-based loading: map logical categories (general, planning, execution, debug, test, review, validation) to specific files and load only the relevant spec documents.
  • Keyword filtering: search within the selected files for matching sections and return results with file:line references when a keyword is provided.
  • Fallback and diagnostics: automatically fall back to loading all specs if category files are missing and surface clear error and warning codes (E001 for missing specs directory, W001 for no keyword matches).
  • Use Case: During planning or execution, invoke this skill to supply agents with coding conventions, quality rules, or debugging notes filtered to the current task.

Quick Start

Run the spec-load skill with an optional --category flag and a keyword to load and filter the repository's spec files into context.

Frequently Asked Questions about spec-load

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

FAQPage Schema
How do I load project specification documents into context for automated workflows?

To load project specs into context, use a skill that retrieves specification documents from the .workflow/specs directory. It maps logical categories like planning or execution to specific files and loads them for downstream agents.

How do I filter specification files by keyword during code planning or debugging?

You can filter specs by keyword using grep-based section extraction. When a keyword is provided, the skill searches selected files and returns matching sections with file:line references for precise context retrieval.

What happens if a requested specification category is missing from the repository?

If requested category files are missing, the system automatically falls back to loading all available specs. It also surfaces diagnostic warnings like W001 for no keyword matches or E001 if the specs directory is entirely missing.

Can I load only coding conventions and quality rules relevant to a specific execution task?

Yes, you can load only relevant coding conventions by using category-based retrieval. Map your task to a logical category like execution or review to load only the specific spec documents needed.

What is the best way to supply downstream agents with debugging notes and validation rules?

The best way to supply agents with debugging notes is category-based spec loading. By targeting the debug or validation category, you inject only the precise guidelines needed for the current task.

Why does my workflow fail to find specification files when loading context?

Your workflow fails to find specification files if the .workflow/specs directory is missing, triggering error E001. Ensure your repository maintains the correct directory structure before loading context.