deusyu/harness-engineering

Harness Engineering 学习指南 — 从概念理解到独立实践的深度学习档案

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 27 minutes ago
Added to GitGenius on September 11th, 2026
Created on March 23rd, 2026
Open Issues & Pull Requests: 4 (+0)
GitHub issues: Enabled
Number of forks: 520
Total Stargazers: 5,893 (+0)
Total Subscribers: 19 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.0 hours
Mean response time: 28.7 hours
90th percentile: 3.3 days
Tracked items: 6

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 11% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Harness Engineering is a learning guide that documents the engineering paradigm where developers design environments and intent specifications for AI agents rather than writing code directly.

The guide addresses how engineering practices must evolve as AI agents become primary executors of work. Rather than traditional software development, the approach centers on creating constraint systems, feedback loops, and agent-readable specifications. The core shift moves from producing code to producing what the guide calls "约束系统"—AGENTS.md files, architectural rules, custom linters, and feedback mechanisms that guide agent behavior. The repository records a complete learning journey from understanding OpenAI's Harness Engineering concept through practical implementation, including concept breakdowns, hands-on experiments, and generated artifacts.

This resource suits teams exploring AI-agent-first development patterns and engineers transitioning from traditional coding to agent orchestration. The guide emphasizes six core concepts: treating the repository as the single source of truth for agent visibility, using concise entry-point documents rather than exhaustive manuals, enforcing rules through mechanical linters instead of documentation, optimizing for agent readability over human aesthetics, and reconsidering merge practices when agent throughput far exceeds human review capacity. The approach prioritizes making systems transparent and actionable to AI agents by encoding decisions and constraints as version-controlled, machine-verifiable artifacts.

The project maintains active documentation with multiple concept files and practical examples. Development appears focused on building out the learning archive with structured content that bridges theoretical understanding and practical application, including generated supplementary materials like presentation decks.