context-injection

Generates context blocks from hero relevant output for engineer agent handoffs.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill context-injection-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-injection
Source: https://github.com/hero-engine/hero/tree/main/core/skills/context-injection
Command: npx skills add https://github.com/hero-engine/hero --skill context-injection-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Specialist agents often write code in isolation, unaware of project conventions, past decisions, and known failure modes, which leads to repeated mistakes and convention violations. This Skill teaches delivery leads how to inject relevant project context into engineer instructions before delegating work. ## Core Features & Use Cases - Context Generation: Run hero relevant against a spec path or explicit file paths to produce a structured markdown block of conventions, past work, decisions, and known risks. - Context Interpretation: Guidance on reading each section, handling superseded specs, and resolving conflicts between conventions, decisions, and spec requirements. - Handoff Structuring: Rules for combining the spec, context block, and delivery lead commentary into engineer instructions, including when and how to override context explicitly. - Use Case: Before delegating a CSV export feature to an engineer agent, run hero relevant .hero/planning/features/add-csv-export/spec.md and paste the resulting context block between the spec and your instructions so the engineer follows existing API conventions and avoids a known session-handling race condition. ## Quick Start Ask the AI to run hero relevant on your spec file and incorporate the resulting context block into the engineer agent's delegation instructions.

Frequently Asked Questions about context-injection

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

FAQPage Schema
How do I generate context for engineer agents with hero relevant?▼

Run hero relevant with a spec path, such as hero relevant .hero/planning/features/add-csv-export/spec.md, or pass explicit files with the --files flag. The command returns a markdown block of conventions, past work, decisions, and known risks to paste into the engineer's instructions.

What does the hero relevant output contain?▼

The output is a markdown block with up to four sections: conventions to follow, past work in the area, decisions that apply, and known risks. Each entry is a summary scoped to the files being touched, with pointers to full specs for more detail.

When should I override context from hero relevant?▼

Override context when the spec intentionally changes a convention, a past decision is being revisited, or past work context is stale. Always state the override explicitly with rationale rather than silently ignoring the context.

How do I handle superseded specs in context output?▼

Entries marked [SUPERSEDED by <slug>] are surfaced for genealogy only. Do not read or follow the superseded spec; open the replacement named after the marker. Use hero supersede <old> --by <new> to mark specs yourself.

What should I do when context conflicts with the spec?▼

The spec wins over conventions, with a note that the convention needs updating. If a past decision conflicts with a new requirement the spec did not address, pause delivery and escalate to the spec author rather than resolving it yourself.