bearings 0.5.0 → 0.5.2

package/dist/{chunk-5D5YO3E3.js → chunk-WYXKSCUW.js}

@@ -16,6 +16,9 @@ var SKILLS = STARTER_SKILL_NAMES;
 var MANUAL_TESTPLAN_FILES = [
   "SKILL.md"
 ];
+var ORCHESTRATE_FILES = [
+  "SKILL.md"
+];
 var FORGE_A_SKILL_FILES = [
   "SKILL.md",
   "templates/guardrail.md",
@@ -63,6 +66,11 @@ var SCAFFOLD = [
     target: `.agents/skills/manual-testplan/${file}`,
     owner: "bearings"
   })),
+  ...ORCHESTRATE_FILES.map((file) => ({
+    template: `agents/skills/orchestrate/${file}`,
+    target: `.agents/skills/orchestrate/${file}`,
+    owner: "bearings"
+  })),
   ...FORGE_A_SKILL_FILES.map((file) => ({
     template: `agents/skills/forge-a-skill/${file}`,
     target: `.agents/skills/forge-a-skill/${file}`,
@@ -783,7 +791,7 @@ async function runFreshInit(repoDir, flags, version) {
 async function runInit(repoDir, flags, version) {
   const state = await inspectManifest(repoDir);
   if (state.kind === "absent") return runFreshInit(repoDir, flags, version);
-  const { runUpdate } = await import("./update-QTWNGAGX.js");
+  const { runUpdate } = await import("./update-4DZKUPFP.js");
   return runUpdate(repoDir, flags, version, state);
 }
 

package/dist/cli.js

@@ -8,7 +8,7 @@ import {
   skillBaselinePath,
   starterSkillNameFromTarget,
   validateHarnesses
-} from "./chunk-5D5YO3E3.js";
+} from "./chunk-WYXKSCUW.js";
 
 // src/cli.ts
 import { Command } from "commander";

package/dist/{update-QTWNGAGX.js → update-4DZKUPFP.js}

@@ -16,7 +16,7 @@ import {
   templatesDir,
   validateHarnesses,
   writeBackup
-} from "./chunk-5D5YO3E3.js";
+} from "./chunk-WYXKSCUW.js";
 
 // src/semver.ts
 function parseSemver(value) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bearings",
-  "version": "0.5.0",
+  "version": "0.5.2",
   "description": "Give your AI agents their bearings — scaffold an agent-friendly setup in any repository.",
   "type": "module",
   "engines": {

package/templates/AGENTS.md

@@ -22,9 +22,4 @@ Primary stack: <agent: fill during handoff — language/runtime/framework/platfo
 
 ## User-Facing Output
 
-Write all user-facing output for a reader with ADHD. Keep it concise, concrete, easy to scan, and in ASD-STE100 Simplified Technical English.
-
-- Lead with the answer; omit preamble and restatement.
-- Use the shortest clear structure: line, bullets, table, tree, or flow.
-- Preserve exact identifiers, paths, commands, errors, and code.
-- Report progress only for discoveries, decisions, or blockers; finish with changes and verification.
+Assume the user has ADHD and cannot comprehend long descriptions. Tailor all your responses to the user's reading ability.

package/templates/agents/skills/orchestrate/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: orchestrate
+description: Run a large task as an orchestrator that plans and decides in the main context and delegates context-heavy work to sub-agents. Use only when the developer invokes /orchestrate by name.
+disable-model-invocation: true
+---
+
+# Orchestrate
+
+Act as the orchestrator. The main context holds the plan, the decisions, and
+the synthesis; sub-agents absorb the raw material — file dumps, logs, command
+output — and return conclusions, not transcripts. If this harness cannot start
+sub-agents, tell the developer, then run the same plan inline.
+
+## Workflow
+
+1. Plan in the main context. Break the task into work items and mark each
+   `delegate` or `keep` using the Delegation table. The plan is done when every
+   item has a mark and the delegated items name their dependencies.
+2. Dispatch a sub-agent for every `delegate` item, following Sub-agent briefs.
+   Run independent items concurrently; run items that touch the same files in
+   sequence or merge them into one brief.
+3. Integrate. Read only the sub-agents' conclusions, make the decisions in the
+   main context, and dispatch follow-up sub-agents for gaps the conclusions
+   expose.
+4. Report: the decisions made, what each sub-agent concluded, and the final
+   result with its verification.
+
+## Delegation table
+
+| Work | Sub-agent returns |
+|---|---|
+| Search and exploration across many files | `path#symbol` locations plus a one-paragraph answer |
+| Bulk reading: large files, logs, external docs | Only the facts that bear on the task, with citations |
+| Verbose commands: tests, builds, lints | Pass or fail, plus only the failing output |
+| Implementation of an independent plan slice | Changed file list plus its self-check result |
+
+Keep in the main context: the plan, choices between approaches, targeted reads
+of already-located sections, and every question for the developer.
+
+## Sub-agent briefs
+
+A sub-agent starts with an empty context. Every brief carries:
+
+- The goal and its completion criterion — how the sub-agent knows it is done.
+- Every input it cannot discover cheaply: paths, commands, constraints, and
+  the repository conventions that apply.
+- The return contract: the shortest artifact the orchestrator can act on,
+  in the shape the Delegation table names.
+- For implementation work: the exact plan slice it owns and the boundary of
+  that slice.