context-extractor

Extract All Needed Context sections from PRD markdown files into structured JSON bundles.

50|9|Updated Oct 15, 2025
One-click install
npx skills add https://github.com/jpoley/flowspec --skill context-extractor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-extractor
Source: https://github.com/jpoley/flowspec/tree/main/.claude/skills/context-extractor
Command: npx skills add https://github.com/jpoley/flowspec --skill context-extractor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PRDs often contain dispersed information required for successful implementation. This Skill extracts the "All Needed Context" from PRD files and converts it into a structured JSON bundle to fuel automated flows and reduce manual data gathering.

Core Features & Use Cases

  • Context extraction: Locate the All Needed Context section and parse its subsections (Code Files, Docs / Specs, Examples, Gotchas, External Systems) into a consistent machine-readable JSON schema.
  • Markdown table parsing: Convert markdown tables into structured arrays for ingestion by downstream flows such as /flow:implement, /flow:generate-prp, and /flow:validate.
  • Use Case: Given a PRD, generate a reusable context bundle that guides implementation and validation workflows.

Quick Start

To use the context-extractor, provide a PRD markdown file path containing an All Needed Context section. The extractor outputs a JSON representation of the extracted context ready for AI processing.

Frequently Asked Questions about context-extractor

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

FAQPage Schema
How do I extract structured data from PRD markdown files?

Context extraction converts PRD markdown files into structured JSON by parsing the All Needed Context section and its subsections—Code Files, Docs/Specs, Examples, Gotchas, and External Systems—into machine-readable format for downstream AI workflows.

Can I parse markdown tables from PRDs into JSON?

Yes, the extractor converts markdown tables embedded in PRDs into structured JSON arrays, enabling deterministic data ingestion by implementation, validation, and proposal-generation workflows.

What input format does context extraction require?

Provide a PRD markdown file containing an All Needed Context section with labeled subsections. The extractor outputs a JSON bundle ready for AI processing and downstream automation flows.

How does context extraction reduce manual work in AI workflows?

By automatically parsing dispersed PRD information into structured JSON, it eliminates manual data gathering and enables deterministic context delivery to /flow:implement, /flow:generate-prp, and /flow:validate workflows.

Does context extraction work with any PRD structure?

The extractor targets PRDs with a defined All Needed Context section. Unstructured or differently formatted PRDs may require preprocessing to match the expected markdown subsection layout.

What happens after I extract context from a PRD?

The generated JSON bundle feeds downstream flows for implementation guidance, proposal generation, and validation—enabling automated processing of extracted Code Files, documentation, examples, and external system references.