mattvideoproductions/MVP-Prompts / skills/foreman
foreman
VerifiedBe the foreman on a big job. One lead model plans the work, hands pieces to helper agents in lanes that never share files, checks everything before accepting it and reports the cost; or runs a long solo build with an owner in the loop. Covers the North Star plan of record, briefs that carry the lead's reasoning, measured gates plus the owner's judgement, strike-based promotion between model tiers, a cost ledger and a mistake register every pass is checked against. Use it when the user types /foreman, says "be the foreman", "be the lead" or "orchestrate this", asks to delegate to subagents or run lanes or passes, or mentions a North Star, three strikes, tiers or promotion between models. Also load it when a task looks too big for one context or needs several agents or days, even if not asked by name; the skill then has you offer it and wait for a yes. Also use it to resume such a project, close a pass, report a session's cost or record a mistake. Not for a change one agent can finish in one sitting.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 32.2 KB |
| assets/NORTH_STAR.template.md | markdown | 4.3 KB |
| assets/brief.template.md | markdown | 1.8 KB |
| assets/config.default.json | config | 2.2 KB |
| assets/discovery-brief.template.md | markdown | 1.8 KB |
| assets/handoff.template.md | markdown | 611 B |
| assets/mistakes.seed.jsonl | other | 21.9 KB |
| assets/prices.json | config | 1.7 KB |
| assets/promoted-brief.addendum.md | markdown | 673 B |
| assets/report.template.md | markdown | 804 B |
| references/audit.md | markdown | 15.9 KB |
| references/briefs-and-handoffs.md | markdown | 10.9 KB |
| references/cost-and-mistakes.md | markdown | 16.5 KB |
| references/field-data.md | markdown | 9.1 KB |
| references/north-star.md | markdown | 11.0 KB |
| references/reference-build.md | markdown | 8.0 KB |
| references/skeleton.md | markdown | 4.3 KB |
| scripts/orch.py | script | 59.5 KB |
assets/discovery-brief.template.md
View on GitHubUse this in place of the build brief when the answer is not yet known: finding a cause, reverse engineering, research. The lead's thinking goes into the suspects and the tests, not into a design.
GOAL
<the question to answer, and which line of the North Star it serves>
<what counts as an answer: the evidence that would settle it, decided before looking>
SUSPECTS
> The lead's candidate explanations, most likely first.
Yours to try to disprove: <which one>
- <explanation A> -> ruled out if <test and the result that would rule it out>
- <explanation B> -> ruled out if <test and result>
> Measure before you change anything. If the evidence points somewhere not listed, follow it and say so.
EXPECTED FAILURES
- <how this kind of search usually goes wrong> -> <how to avoid it>
ALREADY RULED OUT
- <what has been tested and excluded, with the evidence>
FILES
Yours: <paths, including where findings are written>
Do not touch: <paths; always includes the gate scripts, NORTH_STAR.md, .orchestration/ and every other lane's files>
Read first: <North Star section>, <findings so far>
STANDING LIMITS
<the environment-contract rules that apply, quoted, including any exclusive resource and how to take your turn>
GATE
Run: <the command or procedure that reproduces the finding from scratch>
Pass: <yes or no: the finding reproduces, or the suspect is excluded with the stated evidence>
STOP AND REPORT IF
- two tests in a row tell you nothing new
- the next test needs a resource or file outside your lane
- your context passes <N> tokens
KILL RULE
<when to abandon this line of inquiry and record why>
REPORT
> Use the report format. Put every fact found (addresses, constants, names, versions) under FINDINGS with how it was verified, so that nobody has to find it twice.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |