harness-engineering-context

Restructure repository context with root entrypoints and canonical docs validation.

Updated Feb 26, 2026

Search Tags:#automation #organization #repository-context #docs-validation #cross-links #exec-plans

Ready to run

npx skills add https://github.com/MarsPain/efficiency_skills --skill harness-engineering-context

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-engineering-context
Source: https://github.com/MarsPain/efficiency_skills/tree/main/harness-engineering-context
Command: npx skills add https://github.com/MarsPain/efficiency_skills --skill harness-engineering-context

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines restructuring of repository context systems by establishing clear root entrypoints and a canonical docs layer, enabling consistent roles for AGENTS.md, README.md, ARCHITECTURE.md, and automated validation for structure and cross-links.

Core Features & Use Cases

Defines root entrypoints (README.md, AGENTS.md, ARCHITECTURE.md) and a canonical docs folder (docs/) as the single source of truth.
Supports versioned execution plans under docs/exec-plans with lifecycle states.
Provides executable validation to enforce structure, cross-link validity, and source-of-truth boundaries.

Quick Start

Organize your repo so README.md, AGENTS.md, and ARCHITECTURE.md point to the canonical docs/ and enable automated validation.

Frequently Asked Questions about harness-engineering-context

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

FAQPage Schema

How do I organize repository documentation to establish a single source of truth?▼

Organize repository documentation by defining root entrypoints like README.md, AGENTS.md, and ARCHITECTURE.md, then route everything through a canonical docs/ folder. This creates a single source of truth and enforces consistent documentation boundaries across the project.

What is the best way to automate validation for repository structure and cross-links?▼

Automate validation for repository structure and cross-links by applying executable checks that enforce source-of-truth boundaries. This ensures root entrypoints and the canonical docs layer remain accurate and interconnected without manual review.

How do I manage versioned execution plans within a canonical docs layer?▼

Manage versioned execution plans by placing them under docs/exec-plans with defined lifecycle states. This tracks migrations and structural changes systematically while keeping the canonical docs layer up to date.

When do I need to restructure repository context systems with root entrypoints?▼

You need to restructure repository context systems when your project lacks clear root entrypoints or suffers from scattered documentation. Establishing a canonical docs layer resolves inconsistencies and enforces automated structure validation.

Can I use this approach to validate docs boundaries for projects with existing AGENTS.md files?▼

Yes, you can validate docs boundaries for projects with existing AGENTS.md files. The restructuring defines clear roles for AGENTS.md, README.md, and ARCHITECTURE.md, applying automated cross-link checks to ensure they point correctly to the canonical docs folder.