Verified:GitHub

context

Generates epic and story context documents from sprint data with YAML frontmatter.

2|Updated Mar 25, 2026

Search Tags:#documentation #project-management #sprint-data #context-docs #epic-context #story-context #tandem-observations

Ready to run

npx skills add https://github.com/slabgorb/sidequest --skill context-slabgorb

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: context
Source: https://github.com/slabgorb/sidequest/tree/main/.pennyfarthing/skills/pf-context
Command: npx skills add https://github.com/slabgorb/sidequest --skill context-slabgorb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of epic and story context documents from sprint data, ensuring consistent structure and frontmatter for downstream teams.

Core Features & Use Cases

Epic context creation: reads the sprint data, applies the epic context template, and writes to sprint/context/context-epic-{id}.md with proper frontmatter.
Story context creation: reads story and parent epic data, optionally spawns tandem observations, applies the story context template, and writes to sprint/context/context-story-{id}.md with a parent reference.
Validation and compliance: schema-driven sections and output location constraints to ensure governance and traceability.

Quick Start

Run /pf-context create epic {id} to generate an epic context document, or /pf-context create story {id} to generate a story context document.

Frequently Asked Questions about context

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

FAQPage Schema

How do I generate context documentation from sprint data for epics and stories?▼

You can generate epic and story context documents from sprint data to support downstream TEA and Dev teams. The output creates YAML frontmatter and context content files in the sprint/context/ directory with strict schema validation.

What is the best way to automate sprint planning documentation with consistent frontmatter?▼

Automating sprint planning documentation ensures consistent structure and YAML frontmatter for governance workflows. It reads sprint data, applies context templates, and writes validated markdown files for traceability.

How does tandem partner input work when creating story context documents?▼

Story context creation optionally spawns tandem observations to enrich story context documents. It reads parent epic data alongside story data, then applies the story context template to generate output with parent references.

Can I use schema validation to enforce output location and structure for context docs?▼

Schema-driven sections and output location constraints enforce governance and compliance for context documents. This ensures generated epic and story files maintain traceability and follow strict structural rules.

Do I need to provide parent epic data to generate story context files?▼

Story context generation reads both story and parent epic data to write context documents with a parent reference. The parent epic data is required to properly link the story context to its epic.

Why does my generated context doc fail schema validation during sprint planning?▼

Schema validation enforces specific sections and output locations for context documents. Generated files must be written to sprint/context/context-epic-{id}.md or sprint/context/context-story-{id}.md to pass compliance checks.