load-feature-context

Loads feature design docs and summarizes goals, architecture, and gating before story implementation.

Updated May 2, 2024
One-click install
npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill load-feature-context-cman131
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: load-feature-context
Source: https://github.com/cman131/EatSomethingSourWhenYoureTired/tree/main/.claude/skills/load-feature-context
Command: npx skills add https://github.com/cman131/EatSomethingSourWhenYoureTired --skill load-feature-context-cman131

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When implementing or reviewing a story that belongs to a larger feature, developers often lack the overarching design context, leading to code that conflicts with the feature's intent, architecture, or gating decisions. This Skill locates the relevant feature design doc and surfaces a focused summary so the feature's constraints are active before writing code. ## Core Features & Use Cases - Automatic Feature Resolution: Detects the parent feature from a story file's **Parent Feature:** line, accepts a direct feature slug or path, or falls back to listing all available feature docs for user selection. - Structured Context Summary: Presents the feature's problem context, goals, architecture decisions, affected areas, gating flags, and out-of-scope constraints in a consistent format. - Open Question Flagging: Surfaces unresolved items from the feature doc's Open Questions section so they can be addressed before implementation. - Use Case: Before starting work on a story in .claude/stories/, run this Skill to load the parent feature doc from .claude/features/ and confirm the design decisions and gating requirements that the story must respect. ## Quick Start Ask the AI to load the feature context for the story you are about to implement, optionally providing a story or feature slug as an argument.

Frequently Asked Questions about load-feature-context

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

FAQPage Schema
How do I load a feature design doc before implementing a story?▼

Invoke the Skill with a story slug, feature slug, or file path as an argument. It checks the story's Parent Feature line first, then tries the argument as a feature name, and finally lists all feature docs in .claude/features for you to choose from.

How does the Skill find the parent feature of a story?▼

It reads the story file in .claude/stories and looks for a line matching **Parent Feature:** <slug> in the Dev Notes section. If the corresponding file exists in .claude/features, it loads that doc directly.

What happens if no feature docs exist yet?▼

If the .claude/features directory contains no markdown files, the Skill tells you no feature docs exist and suggests running /author-feature to create one, then stops.

Does the Skill handle unresolved open questions in a feature doc?▼

Yes. It scans the feature doc's Open Questions section and surfaces any items that are not crossed out, resolved with an answer, or marked with strikethrough, warning you to resolve them before implementing the story.

What information does the feature summary include?▼

The summary includes the problem context, goals, architecture and approach, affected areas, gating flag or entitlement, and constraints or out-of-scope items. Missing sections are reported as not documented.