-
Notifications
You must be signed in to change notification settings - Fork 0
Harness Engineering
Harness engineering is the discipline of keeping the runtime harness thin while putting durable reasoning into portable skills, guides, and review artifacts.
Note
This is the wiki's intentional Thai/English concept page. The rest of the wiki is English-first for public documentation consistency.
Harness ที่ดีไม่ควรพยายามควบคุมทุกอย่างใน runtime. หน้าที่หลักคือเปิดทางให้ agent โหลดคำแนะนำที่ถูกต้องในเวลาที่เหมาะสม แล้วให้มนุษย์ยังเป็นเจ้าของการตัดสินใจสำคัญ.
In English: the harness routes and loads context; the skills carry the process discipline.
| Layer | Responsibility |
|---|---|
| Thin harness | Entry points, routing, short reminders, validation hooks |
| Fat skills | Requirements, design, review, deployment, operations, reflection |
| Human judgment | Architecture, irreversible actions, production acceptance, compliance posture |
This design keeps the plugin portable across Claude Code, Codex, and other agents that can consume markdown.
The harness stays thin because the durable discipline lives in the skills. That mirrors the plugin's Covey adaptation: habits are not runtime gates; they are repeatable practices for defining intent, making decisions, reviewing work, deploying carefully, and improving the system after each cycle.
- Skill selection and reading.
- Concise workflow reminders.
- Markdown guidance that works across runtimes.
- Validators that catch documentation and skill drift.
- Runtime policy enforcement.
- Secret scanning gates.
- Automatic production mutation.
- Compliance certification.
- Dynamic orchestration engines.
Those responsibilities belong in separate governance or automation layers.
ถ้าสิ่งนั้นเป็น "วินัยในการคิดและตรวจสอบ" ให้ใส่ใน skill. ถ้าสิ่งนั้นเป็น "การบังคับ runtime หรือการอนุมัติ irreversible action" ให้แยกออกจาก plugin core.
If it is thinking discipline, it can live in a skill. If it is runtime authority, keep it outside the core.
Source of truth: this wiki is generated from docs/wiki/. Edits made through the GitHub Wiki web UI may be overwritten by the next sync. To change a page, open a PR against the repository source file.
Repository · Issues · README · License
Workflow discipline for AI-assisted development
Start
Workflow
- Overview
- 0 · Research
- 1 · Requirements
- 2 · Design
- 3 · Breakdown
- 4 · Build Brief
- 5 · Review AI
- 6 · Deploy Guide
- 7 · Monitor Setup
Operations
Reference
- Habits Reference
- Maturity Model
- Architecture
- Limitations
- Vibe Coding vs Structured
- Harness Engineering
Project