skills.rest
edercnj
edercnjCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

x-internal-load-story-context

Resolve and load story context from epic and story files.

Updated Aug 27, 2026
Search Tags:#planning#dependencies#bash#epics#internal#state#story-context
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-internal-load-story-context
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: x-internal-load-story-context
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-internal-load-story-context
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-internal-load-story-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Loads and validates a story context to enable downstream planning by resolving the story file, verifying dependencies, and determining scope without mutating state.

Core Features & Use Cases

  • Resolve and read the target story from ai/epics/epic-XXXX/story-XXXX-YYYY.md
  • Validate Section 1 dependencies against execution-state.json (with fallback to the dependency's Status header when needed)
  • Classify planning artifacts and scope to drive Phase 0 decision points in the orchestrator

Quick Start

Provide the story and epic identifiers to load the story context

Frequently Asked Questions about x-internal-load-story-context

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

FAQPage Schema
How do I load and validate story context for epic and story pairs?▼

To load story context, provide the epic and story identifiers so the system can resolve the target story file, verify dependencies, and classify planning scope without mutating files.

How does dependency validation work when checking a story file?▼

Dependency validation checks the story file's dependencies against execution-state.json, falling back to the dependency's Status header when needed to ensure downstream planning can proceed.

What is the best way to classify planning artifacts and scope for Phase 0?▼

Classifying planning artifacts and scope for Phase 0 involves reading the resolved story file and determining scope boundaries to drive orchestrator decision points without altering state.

Can I use this story context loader without affecting my execution state?▼

Yes, the story context loader operates entirely without mutating state, reading files and validating dependencies to prepare data for downstream planning without writing changes.

Why do I need to resolve a story file before starting downstream planning?▼

Resolving the story file extracts the required context, validates dependencies, and determines scope, ensuring the orchestrator has the necessary classified artifacts to proceed with Phase 0.

What format does the story file need to be in for context loading?▼

The story file must follow the naming convention located at ai/epics/epic-XXXX/story-XXXX-YYYY.md to be successfully resolved and read for context loading.

Related Skills

Explore More Software Engineering Skills→
bretbouchardbretbouchard
2

workflow-reconciliation

Reconcile workflow state across sessions to prevent checkpoint drift.

Community
Advanced
curdxcurdx
4

bmad-sprint-planning

Parse epic files and detect story progress to generate sprint-status.yaml.

Community
Advanced
benjaminshoemakerbenjaminshoemaker
39

populate-state

Generate .claude/phase-state.json from EXECUTION_PLAN.md and git history.

Community
Intermediate
thelegendtubaguythelegendtubaguy
33

openspec-ff-change

Scaffold OpenSpec change artifacts and plan dependency-aware generation.

Community
Advanced