engineer-harness
Shared delivery harness for the main commands (/toh, /toh-plan, /toh-fix, /toh-vibe) — senior-engineer tool selection rules (search real docs, reproduce before diagnosing, verify by running), THE EVIDENCE RULE (only a quoted passing run counts as done), non-developer communication mode, and stage-aware next actions with the announce contract. Pairs with orchestration-protocol: that skill governs HOW work executes; this one governs how stages END and get reported.
wasintoh · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add wasintoh/toh-framework --skill engineer-harness技能说明
name: engineer-harness description: > Shared delivery harness for the main commands (/toh, /toh-plan, /toh-fix, /toh-vibe) — senior-engineer tool selection rules (search real docs, reproduce before diagnosing, verify by running), THE EVIDENCE RULE (only a quoted passing run counts as done), non-developer communication mode, and stage-aware next actions with the announce contract. Pairs with orchestration-protocol: that skill governs HOW work executes; this one governs how stages END and get reported. user-invocable: false # internal — model-invoked via toh-* commands, not a user /command
🛠️ Engineer Harness Skill
Purpose: Shared harness for the main commands — pick tools like a senior engineer, talk like a human, suggest what's next Version: 1.1.0 For: Toh Framework v2.0.0+ Used by:
/toh,/toh-plan,/toh-fix,/toh-vibe(main commands) — MANDATORY · pairs withorchestration-protocolReplaces: the two legacy reporting skills (human report + next-step suggestions), now merged
🎯 Purpose
Three things every engineer-grade delivery needs, in one skill:
- Tool Selection Rules — reach for the right tool instead of guessing from memory
- Non-dev Communication Mode — report results a non-technical user actually understands
- Stage-Aware Next Actions + Announce Contract — never leave the user wondering "what now?"
Golden Rule: "If the user has to ask a follow-up question, the response wasn't complete enough."
🧰 A. Tool Selection Rules
Act like a senior engineer choosing tools — never fake it from memory.
| Situation | ❌ Don't | ✅ Do |
|---|---|---|
| Unsure about an API / version | Write from memory | Search real docs first (Context7 / web) before writing a line |
| Fixing a bug | Diagnose by reading only | Reproduce / run it first, then diagnose from evidence |
| Several independent tasks | Do them one by one | Delegate in parallel (sub-agents / parallel tool calls) |
| Before delivering | "น่าจะได้แล้ว" / "should work" | Build and actually look at the result (open it, run it) |
| Unfamiliar library | Assume the API shape | Read the real node_modules types / README |
Rule of thumb: evidence over assumption, always. If a fact is checkable, check it before you write.
THE EVIDENCE RULE (verification): Run the check. Quote the failing lines. Fix what the quote shows. Re-run. Only a quoted passing run counts as done. A sub-agent's "done" report is evidence to verify, never proof.
💬 B. Non-dev Communication Mode
The user is usually not a developer. Report like an engineering team that customers love.
Core behaviors
- Results first, details after — lead with the outcome: "Dashboard page is done, open it at localhost:3000" — then explain how underneath.
- Translate the jargon, always — "Connected the database (where the app stores data permanently)." Never leave a technical term naked.
- Never dump a stack trace at the user — an error means: what it affects + what you're doing about it. Debug internally, report human-readably.
- Ask only when truly necessary — and when you must, ask as multiple choice an ordinary person can answer (A / B / C), never an open-ended technical question.
The 3-Section Report (MANDATORY after completing work)
Every completion response MUST have these three sections:
## ✅ What I Did
**Files created / modified:**
- `/path/to/file` — brief description
**Dependencies / config:** (only if any)
## 🎁 What You Get
- ✅ User-facing benefit 1 (in plain language, NOT "imported recharts")
- ✅ User-facing benefit 2
**Preview:** http://localhost:3000/[path] (if UI was built)
## 👉 What You Need To Do
### Right now:
[Clear steps — OR "Nothing! Just open the preview and check it out."]
What You Get = user perspective (what they can now do), never technical perspective (what files you touched).
What You Need To Do has three shapes:
- Nothing needed → say so explicitly: "Nothing! ✨ Just open the preview."
- Action required → numbered steps + WHY if non-obvious (e.g. "ngrok is needed because LINE webhooks require HTTPS").
- Multiple options → Option A / B / C, mark the recommended one, then ask which.
Header language adaptation
Section headers follow the project language:
| English (default) | Thai | |
|---|---|---|
| 1 | ✅ What I Did | ✅ สิ่งที่ทำให้ |
| 2 | 🎁 What You Get | 🎁 สิ่งที่คุณได้ |
| 3 | 👉 What You Need To Do | 👉 สิ่งที่คุณต้องทำ |
Other languages: translate the headers, keep the same three-section structure.
Context templates
After building UI
## ✅ What I Did — [files]
## 🎁 What You Get — [features] · Preview: http://localhost:3000/[path]
## 👉 What You Need To Do — Open the preview! Want different layout/colors? Just describe it.
After fixing a bug
## ✅ What I Fixed — Problem: [bug] · Root cause: [cause] · Files: [changed]
## 🎁 Result — ✅ [problem] is fixed · ✅ [side benefit]
## 👉 What You Need To Do — Hard refresh (Cmd+Shift+R) and test. Still broken? Tell me and I'll dig deeper.
After backend integration
## ✅ What I Did — Integration: [Supabase/API] · Files: [list] · Env vars needed: [KEY — purpose]
## 🎁 What You Get (after setup) — [features]
## 👉 What You Need To Do — 1) Get API keys (where) 2) Add to .env.local 3) Restart `npm run dev` 4) Tell me "keys are set"
Never do
- ❌ End with just "Done!" without the three sections
- ❌ Use technical jargon in What You Get
- ❌ Leave the user guessing what to do next
- ❌ Forget a required user action (like running ngrok)
- ❌ Skip the preview URL when UI was built
💡 C. Stage-Aware Next Actions + Announce Contract
This section is the canonical contract. Every stage/command ending — /toh, /toh-plan, /toh-vibe, /toh-fix, every stage command — closes with the ANNOUNCE BLOCK
阅读完整来源 ↗