skills.rest
zxyycom
zxyycomCOMMUNITY
Explore all skills by this author →
GitHub

context-engineering

Establish and repair project context packets from AGENTS.md and navigation docs.

Updated Jun 4, 2026
Search Tags:#context#navigation#handoff#drift#rules#docnav
One-click install
npx skills add https://github.com/zxyycom/docnav --skill context-engineering-zxyycom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: context-engineering
Source: https://github.com/zxyycom/docnav/tree/main/.codex/skills/context-engineering
Command: npx skills add https://github.com/zxyycom/docnav --skill context-engineering-zxyycom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Aligns agent behavior with repository contracts by establishing, repairing, or handing off project context. It prevents drift, aligns assumptions, and maintains authority paths across tasks and teams.

Core Features & Use Cases

  • Establish or repair a bounded context packet for a project task.
  • Track and reconcile assumptions with sources (rules, AGENTS.md, navigation docs).
  • Support drift recovery and parallel handoffs by packaging context data for next agents.

Quick Start

Provide a bounded context packet for the current task that anchors decisions and enables drift recovery.

Frequently Asked Questions about context-engineering

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

FAQPage Schema
How do I prevent agent drift when handing off tasks across multiple ownership boundaries?▼

To prevent agent drift during handoffs, establish a bounded context packet that anchors decisions to authoritative sources like AGENTS.md. This aligns agent behavior with repository contracts and maintains authority paths across teams.

What is project context repair and when do I need to reconcile assumptions with navigation sources?▼

Project context repair is binding explicit assumptions to authoritative sources like docs/navigation.md. You need this when tasks involve multiple rules or navigation sources and require drift recovery to align agent behavior with repository contracts.

How do I package a compact context packet for parallel agent handoffs?▼

Package a compact context packet by loading authoritative sources like AGENTS.md and docs/navigation.md, then binding explicit assumptions to their origins. This produces the data needed to support parallel handoffs and anchor next agents.

Does establishing project context require loading specific repository navigation files?▼

Yes, establishing project context requires loading authoritative sources such as AGENTS.md and docs/navigation.md. These files provide the repository contracts needed to anchor governance and bind explicit assumptions for the current task.

What is the best way to align agent behavior with repository contracts across multiple rules?▼

The best way to align agent behavior is to establish or repair a bounded context packet that tracks and reconciles assumptions with sources. This anchors governance, reduces drift, and maintains authority paths across tasks and teams.

Related Skills

Explore More Product & Management Skills→
mattjeffersonmattjefferson
4

he-bootstrap

Initialize a repository with Harness Engineering directory structure and baseline documentation files.

Community
Basic
jshsakurajshsakura
22

context-manager

Summarize project context into a compact packet for downstream subagents.

Community
Intermediate
QventuQventu

mintlify

Creates and maintains Mintlify documentation sites using CLI, MDX frontmatter, and docs.json.

Official
Intermediate
diegosouzapwdiegosouzapw
108

design-systems-ops

Govern token changes and component drift across Figma, code, and docs.

Community
Advanced