context-engineering

Curate task-scoped context for agent workers from repository rules and specs.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-assistant --skill context-engineering-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/jankneumann/agentic-assistant/tree/main/.agents/skills/context-engineering
Command: npx skills add https://github.com/jankneumann/agentic-assistant --skill context-engineering-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Context engineering prevents agents from producing low-quality or incorrect work caused by missing, outdated, or overly broad information.

Core Features & Use Cases

  • Curated context hierarchy: Selects the right mix of project rules, relevant specs, source files, error output, and conversation history.
  • Named context packing strategies: Uses structured “Brain Dump,” “Selective Include,” or “Hierarchical Summary” patterns to match task scope.
  • Repo-specific handoff safety: Supports coordinator-aware context discovery, enforces work-packages scope boundaries, and applies the sanitize-then-verify contract for cross-session transfers.
  • Confusion management guardrails: Prompts for explicit choices when requirements are incomplete or spec/code conflicts exist.

Quick Start

Ask your orchestrator to load context-engineering before dispatching a worker for a specific wp-* work package so the worker receives only the rules, spec excerpts, files, and errors it needs.

Frequently Asked Questions about context-engineering

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

FAQPage Schema
How do I give an AI agent the right context to prevent hallucinations during feature implementation?

Context engineering curates the exact project rules, specs, source files, and errors an agent needs at dispatch time, preventing low-quality output caused by missing or overly broad information.

What is the best way to enforce scope boundaries when orchestrating parallel agents across work packages?

Enforcing scope boundaries is handled by applying rules from a work-packages.yaml file, ensuring dispatched workers only receive and act upon the specific repo context and spec excerpts defined for their assigned wp-* work package.

How do I sanitize and verify context during cross-session agent handoffs?

Cross-session context transfers are secured using a sanitize-then-verify contract, ensuring that coordinator-aware handoffs pass clean, validated information to the next worker without carrying over irrelevant or conflicting session history.

Can I use named context packing strategies like Brain Dump or Selective Include for different task scopes?

Yes, you can apply named packing strategies such as Brain Dump, Selective Include, or Hierarchical Summary to dynamically match the curated context size and depth to the specific scope of the feature task.

What happens if an agent has incomplete requirements or spec and code conflicts during context loading?

Confusion management guardrails trigger explicit prompts for choices when incomplete requirements or spec and code conflicts are detected, ensuring the agent pauses to resolve ambiguities before proceeding.