skills.rest
outcomeeng
outcomeengOFFICIAL
Explore all skills by this author →
WebsiteGitHub

understanding-spx

Ingest and validate hierarchical SPX context from ADRs, PDRs, and specs.

1|Updated Jan 6, 2026
Search Tags:#adr#story#prd#specs#capability#spx#context-ingestion
One-click install
npx skills add https://github.com/outcomeeng/claude --skill understanding-spx-outcomeeng
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: understanding-spx
Source: https://github.com/outcomeeng/claude/tree/main/plugins/spx-legacy/skills/understanding-spx
Command: npx skills add https://github.com/outcomeeng/claude --skill understanding-spx-outcomeeng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill ensures that every SPX work item has complete, hierarchical context loaded before any work begins, preventing incomplete implementations and downstream rework.

Core Features & Use Cases

  • Load product-level guidance from spx/CLAUDE.md and read all product ADRs and PDRs.
  • Read capability, feature, and story specifications and their associated ADRs and PDRs to build a full context graph.
  • Abort fast with clear remediation when required documents are missing and offer to generate specs from available PRDs when present.

Quick Start

Invoke this skill to load complete context for a work item by reading product, capability, feature, and story specifications and their ADRs/PDRs in SPX.

Frequently Asked Questions about understanding-spx

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

FAQPage Schema
How do I load complete hierarchical context for SPX work items before implementation?▼

To load SPX context, ingest and validate product, capability, feature, and story level specifications along with all required ADRs and PDRs to output a structured context summary for safe execution.

What happens when required spec documents are missing during SPX context ingestion?▼

When required SPX spec documents are missing, the process aborts fast with actionable errors and offers to generate missing specs from available PRDs if they are present in the repository.

How do I read product ADRs and PDRs to build a full context graph for feature implementation?▼

Read product-level guidance from spx/CLAUDE.md then ingest all capability, feature, and story specifications alongside their associated ADRs and PDRs to build a complete hierarchical context graph.

Do I need PRDs present to generate missing specs for SPX stories?▼

Yes, PRDs must be present to generate missing SPX specs. The context ingestion process offers to create missing specifications from available PRDs to prevent incomplete implementations.

Why does my SPX work item implementation fail due to incomplete hierarchical context?▼

SPX implementation fails because required hierarchical context was not loaded. Ingesting and validating all product guides, ADRs, PDRs, and spec documents beforehand prevents incomplete implementations and downstream rework.

Can I use SPX context ingestion for work items organized across product, capability, and story levels?▼

Yes, SPX context ingestion applies to work items organized under product, capability, feature, and story levels, reading all required and optional decision records to validate complete context before execution.

Related Skills

Explore More Software Engineering Skills→
outcomeengineeringoutcomeengineering
1

managing-spx

Create and organize spx/ specifications using templates and BSP numbering.

Official
Intermediate
bingeli1379bingeli1379
2

esdd-propose

Generate proposal, design, specs, and tasks artifacts using SDD and DDD patterns.

Community
Advanced
amitmishra-bylddamitmishra-byldd

bmad-dev-story

Execute story implementation from context-filled spec files with status transitions.

Community
Advanced
jscraikjscraik
8

compound-engineering-router

Route compound-engineering requests to workflow prompts or meta-modes in the Codex configuration repository.

Community
Advanced