understanding-specs

Load complete hierarchical specification documents for a work item.

1|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/outcomeengineering/spx-claude --skill understanding-specs-outcomeengineering
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: understanding-specs
Source: https://github.com/outcomeengineering/spx-claude/tree/main/plugins/specs/skills/understanding-specs
Command: npx skills add https://github.com/outcomeengineering/spx-claude --skill understanding-specs-outcomeengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Ensures you have all necessary specification documents before starting implementation, preventing costly rework and missed requirements.

Core Features & Use Cases

  • Hierarchical Context Loading: Reads specs from product down to the story level.
  • Mandatory Document Verification: Fails fast if any required spec (capability, feature, story) is missing.
  • Decision Record Inclusion: Loads all relevant ADRs and PDRs for architectural and product constraints.
  • Use Case: Before coding a new feature, use this skill to confirm you have the capability spec, feature spec, and all related architectural decisions documented, ensuring you understand the full scope.

Quick Start

Invoke this skill with the full path to the story you are working on, for example: /understanding-specs capability-10_cli/feature-20_commands/story-30_build.

Frequently Asked Questions about understanding-specs

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

FAQPage Schema
How do I load complete specification context before starting feature implementation?

Loading specification context requires reading all hierarchical spec documents from product level down to the target story. This includes capability specs, feature specs, and related architectural decisions to ensure complete requirements understanding.

What happens if required specification documents are missing when loading work item context?

When required specs are missing, the loading process fails fast with actionable errors. This mandatory document verification prevents implementation from starting without complete context, avoiding costly rework.

When do I need to verify hierarchical requirements and architectural decision records before coding?

You need hierarchical requirements and decision record verification before coding any new feature or story. This confirms you have the capability spec, feature spec, and all ADRs and PDRs documenting architectural constraints.

How do I read product specifications and story requirements hierarchically using a file path?

To read product specifications hierarchically, invoke the context loading process with the full path to your target story, such as capability-10_cli/feature-20_commands/story-30_build. It reads all specs from product down to the story level.

Does understanding-specs include architectural decision records when loading work item context?

Yes, the context loading process includes all relevant ADRs and PDRs. This ensures implementation skills have complete knowledge of architectural and product constraints before starting work.