@nanocollective/roster 0.1.0-alpha.22 → 0.1.0-alpha.23

package/dist/cli.js

@@ -1029,6 +1029,7 @@ roster brief <kind> [handle]
     discover        write org/business.md, which every prompt is composed on top of
     charter <who>   write a staff member's CHARTER.md
     voice           revise org/voice.md, the house style every surface inherits
+    priorities      write org/priorities.md, this month's priorities
     amend <who>     change what a staff member is told, with the whole prompt attached
 
   \`charter\` carries one of the worked examples in docs/charters as a model for the shape,
@@ -4890,7 +4891,7 @@ async function initFiles(o) {
   }
   files.set("org/business.md", businessStub(o.name, o.org));
   files.set("org/priorities.md", prioritiesStub());
-  for (const [rel, text] of briefCommands(["discover", "voice"], {
+  for (const [rel, text] of briefCommands(["discover", "priorities", "voice"], {
     ORG: o.org,
     ORG_NAME: o.name,
     OPS_REPO: `${o.org}/${o.opsName}`,
@@ -5861,6 +5862,7 @@ import { join as join24 } from "path";
 var WRITES = {
   discover: (c) => [`${c.opsName}/org/business.md`],
   voice: (c) => [`${c.opsName}/org/voice.md`],
+  priorities: (c) => [`${c.opsName}/org/priorities.md`],
   charter: (c) => [`${c.dir}/CHARTER.md`]
 };
 var READS = {
@@ -5870,6 +5872,7 @@ var READS = {
     `${c.opsName}/org/guardrails.md`
   ],
   voice: (c) => [`${c.opsName}/org/business.md`, `${c.opsName}/org/guardrails.md`],
+  priorities: (c) => [`${c.opsName}/org/business.md`],
   /* A charter is the difference between this staff member and everyone else, so the peers'
      charters are the most useful thing in the room: without them the model writes a second
      copy of whoever it was shown. */

package/docs/getting-started.md

@@ -149,7 +149,8 @@ The same road, command by command. Each prints its plan and changes nothing with
 
 ```bash
 roster init --org acme --apply        # the ops repo, and its Actions access
-roster brief discover                 # a brief for org/business.md; write priorities.md too
+roster brief discover                 # a brief for org/business.md
+roster brief priorities               # a brief for org/priorities.md
 roster hire cto --apply               # the brain, the wiring, the commits as you
 roster app cto --apply                # the App, its secrets, and a pre-ticked install link
 roster credential --apply             # the agent credential, once for the org

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nanocollective/roster",
-  "version": "0.1.0-alpha.22",
+  "version": "0.1.0-alpha.23",
   "description": "An agent-run org, powered by GitHub. Scaffold AI staff members whose brain is a repo.",
   "type": "module",
   "bin": {

package/templates/briefs/priorities.md

@@ -0,0 +1,46 @@
+Write `org/priorities.md` for %%ORG_NAME%%.
+
+You are helping %%HUMAN%% decide what their AI staff should work on this month. Every staff
+member reads this file at the start of every run and picks work that serves it, so a vague
+priority produces scattered work.
+
+## Where you are
+
+- `%%OPS_REPO_DIR%%/org/business.md`: what the business is. **Read it first**, and don't ask
+  anything it already answers.
+- `%%OPS_REPO_DIR%%/org/priorities.md`: the current file, which you are replacing.
+
+If you cannot read files where you are running, ask %%HUMAN%% to paste `org/business.md`.
+
+## Interview
+
+Ask one question at a time. You are after:
+
+- **The one outcome that matters most this month**, and how they will know it happened.
+- **At most two more**, in order. Push back on a fourth: past three it is a wish list.
+- **What is out of scope this month**: work that is tempting but not now. Naming it is what
+  stops the staff doing it.
+
+Prefer outcomes ("a stranger pays for it") to activities ("improve the landing page"). If an
+answer is an activity, ask what it is for.
+
+## Write it
+
+Use exactly this shape:
+
+```
+## What matters this month
+
+### Priorities, in order
+
+1. The first outcome, and how you will know it happened.
+2. The second.
+3. The third.
+
+### Out of scope this month
+
+- One thing per line.
+```
+
+Keep each priority to a sentence or two. Don't add anything %%HUMAN%% didn't say without
+listing it after the file so they can check it.

package/templates/portal/js/views/orgedit.js

@@ -99,7 +99,12 @@ export function prioritiesForm(o) {
       (scoped.length ? "\n### Out of scope this month\n\n" + scoped.map((t) => `- ${t}`).join("\n") + "\n" : "");
     await saveAndSay(save, out, o.path, text, "portal: write org/priorities.md", o.onSaved);
   };
-  return modes([...(o.before ?? []), { label: "Fill in", node: form }, rawMode(o.path, o.onSaved)]);
+  return modes([
+    ...(o.before ?? []),
+    { label: "Fill in", node: form },
+    { label: "Let an AI interview you", node: paste({ kind: "priorities", title: "", onSaved: o.onSaved }) },
+    rawMode(o.path, o.onSaved),
+  ]);
 }
 
 /** Any org file as highlighted text, with Read ahead of it on the Org screen. */