spec-context-loader

Extract requirements, design, and QA test references into structured context.

1|Updated Jun 15, 2025
One-click install
npx skills add https://github.com/einja-inc/einja-management-template --skill spec-context-loader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-context-loader
Source: https://github.com/einja-inc/einja-management-template/tree/main/.claude/skills/einja-spec-context-loader
Command: npx skills add https://github.com/einja-inc/einja-management-template --skill spec-context-loader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns scattered specification documents into a single, structured context to guide task implementation in ATDD workflows.

Core Features & Use Cases

  • Context extraction: Pulls requirements.md, design.md, and qa-tests references into a unified context.
  • Structured output: Produces a consistent data model for downstream tasks.
  • Use Case: Given a spec directory with a requirements and design and qa-tests, returns a ready-to-use context for a task group.

Quick Start

Run this command to generate context from a spec directory: spec-context-loader /docs/specs/issues/auth/issue21-login-feature/ --task-group-id 1.1

Frequently Asked Questions about spec-context-loader

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

FAQPage Schema
How do I extract structured context from specification directories for ATDD workflows?

You can extract structured context from specification directories by parsing requirements.md, design.md, and qa-tests files into a unified, machine-consumable format for ATDD workflows.

What is the best way to parse Given-When-Then acceptance criteria into a structured data model?

Parsing Given-When-Then acceptance criteria involves identifying spec directories with requirements and design documents, then extracting QA test references into a consistent context output for task groups.

Can I use this context extraction tool if my spec directory only has requirements and design files but no qa-tests?

Context extraction targets spec directories containing requirements.md, design.md, and qa-tests. Missing qa-tests may limit the completeness of the structured output for ATDD workflows.

How do I generate context for a specific task group from a spec directory?

Generate context for a specific task group by running the loader command with the spec directory path and a task-group-id parameter to get a ready-to-use structured context model.

Why does my ATDD workflow need structured context from specification documents?

ATDD workflows need structured context to turn scattered specification documents into a single, machine-consumable data model, ensuring downstream tasks receive consistent requirements and parsed acceptance criteria.