subagent-briefing

Write and lint sub-agent briefs against a register of documented prompt defects before spawning build agents.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/timikalo7/Execute --skill subagent-briefing-timikalo7
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-briefing
Source: https://github.com/timikalo7/Execute/tree/main/.claude/skills/subagent-briefing
Command: npx skills add https://github.com/timikalo7/Execute --skill subagent-briefing-timikalo7

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Sub-agent briefs written from instinct repeat the same defects: agents hang in wait loops, lose uncommitted work, game metrics, or report success without evidence. This Skill turns each paid-for failure into a required clause and a linter rule, so every new brief starts from the last one's lessons instead of from memory. ## Core Features & Use Cases - Defect register: A table of real prompt defects (hung agents, lost trees, gamed metrics, unverified evaluator findings) with the exact clause that prevents each one. - Brief structure checklist: Eight required parts covering scope, ground truth, operational metric definitions, definition of done, anti-gaming, commit discipline, and the evidence contract. - lint-brief.mjs: A Node.js linter that fails a brief missing any load-bearing clause, flags metric words used without numbers, and ships with a --selftest suite. - Use Case: Before delegating a UI rebuild ticket to a build agent, write the brief, run the linter, fix the flagged clauses, then spawn the agent with a brief that cannot be misread. ## Quick Start Write your sub-agent brief to a text file and run node .claude/skills/subagent-briefing/lint-brief.mjs on it, then fix every flagged clause before spawning the agent.

Frequently Asked Questions about subagent-briefing

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

FAQPage Schema
How do I write a good prompt for a coding sub-agent?

Structure the brief with eight parts: working directory and reading list, one sharp job with scope fences, ground truth by path, operational metric definitions with numbers, exact done commands, an anti-gaming clause, commit discipline, and an evidence contract requiring real command output.

How do I lint a sub-agent brief before delegating work?

Run node lint-brief.mjs <brief.txt> from the skill directory. It exits 1 and lists each missing clause with the cost that clause's absence previously caused. Run with --selftest to verify the linter's own rules.

Why do AI agents hang in wait loops during long checks?

Agents hang when told to run checks in the foreground without a timeout budget, because the Bash tool defaults to 120 seconds and silently backgrounds slower commands. Briefs must name an explicit timeout parameter up to 600000ms.

Can I use metric words like density or contrast in an agent brief?

Only with numbers or a named standard. The linter flags metric words like density, fidelity, or contrast unless the brief carries percentages, ratios, or a named threshold such as WCAG AA, because undefined metrics get misread.

What are the limitations of a brief linter versus a judge?

The linter only checks that load-bearing clauses are present; it cannot judge whether a brief is well written or correct. Evaluator findings must still be verified against ground truth by the human before being relayed into a brief.