syntaur 0.4.4 → 0.5.0

package/examples/playbooks/assignment-creation.md

@@ -0,0 +1,19 @@
+---
+name: "Assignment Creation"
+slug: assignment-creation
+description: "Rules for how agents should create new assignments"
+when_to_use: "Before creating a new assignment (project-nested or standalone)"
+created: "2026-04-23T00:00:00Z"
+updated: "2026-04-23T00:00:00Z"
+tags:
+  - protocol
+  - assignments
+---
+
+# Assignment Creation
+
+Rules for creating new assignments.
+
+1. Do not pre-populate assignments with specific todos unless the user explicitly asks for them. Todos belong to the planning phase, and baking them into the assignment at creation time locks in an approach before the agent has read the project context, decision records, or dependencies. Let the assignment describe the goal and acceptance criteria; let the plan describe the steps.
+
+2. The initial status of a newly created assignment should usually be `brainstorming`. Assignments typically need to be shaped — goal clarified, acceptance criteria refined, scope discussed — before they're ready to be planned or worked on. Only skip `brainstorming` when the user has already fully specified the assignment and explicitly wants it to start in a later state.

package/examples/playbooks/assignment-planning.md

@@ -0,0 +1,28 @@
+---
+name: "Assignment Planning"
+slug: assignment-planning
+description: "Rules for how agents should update an assignment's todos when planning"
+when_to_use: "When creating a plan for an assignment, or creating a new plan after a prior one has been executed"
+created: "2026-04-23T00:00:00Z"
+updated: "2026-04-23T00:00:00Z"
+tags:
+  - protocol
+  - planning
+  - assignments
+---
+
+# Assignment Planning
+
+Rules for updating an assignment's todos during planning.
+
+1. When planning an assignment, add these three todos to the assignment:
+   - [ ] Create plan
+   - [ ] Review plan (include link to the plan .md)
+   - [ ] Execute plan (include link to the plan .md)
+
+2. If asked to create a new plan after a prior plan has been implemented (i.e. its "Execute plan" todo is checked off), add three new todos for the new cycle:
+   - [ ] Create new plan
+   - [ ] Review new plan (include link to the new plan .md)
+   - [ ] Execute new plan (include link to the new plan .md)
+
+   Leave the old todos intact. Mark them as done and/or outdated if appropriate, but do not delete them — the history of plan cycles is part of the assignment record.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "syntaur",
-  "version": "0.4.4",
+  "version": "0.5.0",
   "description": "Project workflow CLI with dashboard, Claude Code plugin, and Codex plugin",
   "homepage": "https://github.com/prong-horn/syntaur#readme",
   "repository": {

package/platforms/claude-code/.orphaned_at

@@ -0,0 +1 @@
+1776860006263

package/platforms/claude-code/agents/syntaur-expert.md

@@ -169,8 +169,8 @@ Only the assigned agent may write to its own assignment folder.
 | Command | Description |
 |---------|-------------|
 | `syntaur create-project <title> [--slug S] [--dir D]` | Create new project with full scaffolding |
-| `syntaur create-assignment <title> --project M [--priority P] [--depends-on D] [--slug S] [--type T]` | Create assignment in a project |
-| `syntaur create-assignment <title> --one-off [--type T]` | Create standalone assignment at `~/.syntaur/assignments/<uuid>/` (project: null, slug display-only) |
+| `syntaur create-assignment <title> --project M [--priority P] [--depends-on D] [--slug S] [--type T] [--with-todos]` | Create assignment in a project. `--with-todos` pre-scaffolds a `## Todos` section (omitted by default — usually added later by `plan-assignment`). |
+| `syntaur create-assignment <title> --one-off [--type T] [--with-todos]` | Create standalone assignment at `~/.syntaur/assignments/<uuid>/` (project: null, slug display-only) |
 
 ### Coordination (CLI-mediated writes)
 | Command | Description |

package/platforms/claude-code/commands/create-assignment/create-assignment.md

@@ -3,7 +3,7 @@ name: create-assignment
 description: Create a new Syntaur assignment (project-nested or standalone one-off)
 arguments:
   - name: args
-    description: "Title and flags. See the create-assignment skill for supported forms (e.g. --project <slug>, --one-off, --type <type>)."
+    description: "Title and flags. See the create-assignment skill for supported forms (e.g. --project <slug>, --one-off, --type <type>, --with-todos)."
     required: false
 ---
 

package/platforms/codex/agents/syntaur-operator.md

@@ -80,8 +80,8 @@ Project-nested assignments live at `~/.syntaur/projects/<slug>/assignments/<aslu
 Use these commands directly when needed:
 
 - `syntaur create-project "<title>" [--slug <slug>] [--dir <path>]`
-- `syntaur create-assignment "<title>" --project <slug> [--slug <slug>] [--priority <level>] [--depends-on <slugs>] [--type <type>] [--dir <path>]`
-- `syntaur create-assignment "<title>" --one-off [--slug <slug>] [--priority <level>] [--type <type>] [--dir <path>]` — creates standalone at `~/.syntaur/assignments/<uuid>/`
+- `syntaur create-assignment "<title>" --project <slug> [--slug <slug>] [--priority <level>] [--depends-on <slugs>] [--type <type>] [--dir <path>] [--with-todos]` — `--with-todos` pre-scaffolds a `## Todos` section (omitted by default; usually added later by `plan-assignment`)
+- `syntaur create-assignment "<title>" --one-off [--slug <slug>] [--priority <level>] [--type <type>] [--dir <path>] [--with-todos]` — creates standalone at `~/.syntaur/assignments/<uuid>/`
 - `syntaur setup [--yes] [--claude] [--codex] [--claude-dir <path>] [--codex-dir <path>] [--codex-marketplace-path <path>] [--dashboard]`
 - `syntaur assign <assignment-slug> --agent codex --project <project-slug>`
 - `syntaur start <assignment-slug> --project <project-slug>`

package/vendor/syntaur-skills/README.md

@@ -13,6 +13,16 @@ syntaur setup
 
 ## Install
 
+If you use Claude Code or Codex, install the `syntaur` package — these skills ship automatically with its plugin install flow:
+
+```bash
+npm install -g syntaur
+syntaur install-plugin        # Claude Code → ~/.claude/skills/
+syntaur install-codex-plugin  # Codex → ~/.codex/skills/
+```
+
+For any other AI coding agent (Cursor, OpenCode, custom runtimes), install the skills directly:
+
 ```bash
 npx skills add prong-horn/syntaur-skills
 ```
@@ -23,6 +33,8 @@ Or install a specific skill:
 npx skills add prong-horn/syntaur-skills --skill syntaur-protocol
 ```
 
+> **Note:** If you install `syntaur` AND also run `npx skills add prong-horn/syntaur-skills` on the same machine, you'll get the same skills installed once — they use the same names. The `syntaur` CLI detects existing copies and skips already-current ones.
+
 ## Skills
 
 | Skill | Description |

package/vendor/syntaur-skills/skills/create-assignment/SKILL.md

@@ -7,7 +7,7 @@ description: >-
 license: MIT
 metadata:
   author: prong-horn
-  version: "1.1.0"
+  version: "1.2.0"
 ---
 
 # Create Assignment
@@ -26,6 +26,7 @@ Expects arguments from the user:
 - `--type <type>` (optional): classification such as `feature`, `bug`, `refactor`, `research`, `chore`. Defaults to `feature`. When `~/.syntaur/config.md` defines `types.definitions`, the CLI validates against that list.
 - `--depends-on <slug[,slug...]>` (optional, project-nested only): comma-separated list of assignment slugs this depends on
 - `--dir <path>` (optional): override the default project directory
+- `--with-todos` (optional): scaffold a `## Todos` section in `assignment.md`. **Omit unless the user explicitly asks for it.** Todos are normally a plan (added by `plan-assignment`) or populated during planning — not something to pre-create at assignment time. Pass this flag only if the user explicitly says something like "include todos", "with a todo list", "scaffold todos", etc.
 
 If no title was provided, ask the user what the assignment should be called.
 
@@ -38,13 +39,13 @@ If no active context and no project flag, ask the user which project to add it t
 Build the command from the parsed arguments:
 
 ```bash
-syntaur create-assignment "<title>" --project <slug> [--slug <slug>] [--priority <level>] [--type <type>] [--depends-on <slugs>] [--dir <path>]
+syntaur create-assignment "<title>" --project <slug> [--slug <slug>] [--priority <level>] [--type <type>] [--depends-on <slugs>] [--dir <path>] [--with-todos]
 ```
 
 Or for a one-off (standalone at `~/.syntaur/assignments/<uuid>/`):
 
 ```bash
-syntaur create-assignment "<title>" --one-off [--slug <slug>] [--priority <level>] [--type <type>] [--dir <path>]
+syntaur create-assignment "<title>" --one-off [--slug <slug>] [--priority <level>] [--type <type>] [--dir <path>] [--with-todos]
 ```
 
 If the command fails (e.g., project not found, slug collision, invalid type), report the error and suggest fixes.
@@ -67,6 +68,6 @@ Tell the user:
 - The assignment was created with its slug, priority, type, and location. For standalone assignments, note that the folder is named by UUID (not slug) — `slug` is display-only.
 - Files created: `assignment.md`, `progress.md`, `comments.md`, `scratchpad.md`, `handoff.md`, `decision-record.md`. **`plan.md` is NOT scaffolded** — plan files are optional and created on demand by the `plan-assignment` skill.
 - Remind the user: `progress.md` is where timestamped progress entries go (NOT `assignment.md`), and `comments.md` is CLI-mediated — write only via `syntaur comment <slug-or-uuid> "body" --type question|note|feedback [--reply-to <id>]`.
-- Suggest editing `assignment.md` to fill in the objective, acceptance criteria, context, and any initial todos. The `## Todos` section accepts simple tasks or markdown links to plan files.
+- Suggest editing `assignment.md` to fill in the objective, acceptance criteria, and context. A `## Todos` section is **not** scaffolded by default — it is added automatically by `plan-assignment` (linking the new plan file) or by `syntaur request` (cross-assignment requests). Only the `--with-todos` flag pre-scaffolds an empty `## Todos` section.
 - If dependencies were set, note them. Standalone assignments cannot declare `dependsOn`.
 - Suggest `grab-assignment <project-slug> <assignment-slug>` (or `grab-assignment --id <uuid>` for standalone) to claim and start working on it.

package/dashboard/dist/assets/channel-DqU_8tiy.js

@@ -1 +0,0 @@
-import{aq as o,ar as n}from"./mermaid.core-BpP2keU-.js";const t=(r,a)=>o.lang.round(n.parse(r)[a]);export{t as c};

package/dashboard/dist/assets/classDiagram-VBA2DB6C-D29Eeoe8.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-WL4C6EOR-VVhAMMYU.js";import{_ as i}from"./mermaid.core-BpP2keU-.js";import"./chunk-FMBD7UC4-B-GjCpdr.js";import"./chunk-JSJVCQXG-BLVVcezm.js";import"./chunk-55IACEB6-CaEBUJYu.js";import"./chunk-KX2RTZJC-DqCNEw4h.js";import"./index-D-fepllQ.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dashboard/dist/assets/classDiagram-v2-RAHNMMFH-D29Eeoe8.js

@@ -1 +0,0 @@
-import{s as a,c as s,a as e,C as t}from"./chunk-WL4C6EOR-VVhAMMYU.js";import{_ as i}from"./mermaid.core-BpP2keU-.js";import"./chunk-FMBD7UC4-B-GjCpdr.js";import"./chunk-JSJVCQXG-BLVVcezm.js";import"./chunk-55IACEB6-CaEBUJYu.js";import"./chunk-KX2RTZJC-DqCNEw4h.js";import"./index-D-fepllQ.js";var n={parser:e,get db(){return new t},renderer:s,styles:a,init:i(r=>{r.class||(r.class={}),r.class.arrowMarkerAbsolute=r.arrowMarkerAbsolute},"init")};export{n as diagram};

package/dashboard/dist/assets/clone-Bok8Q3Jj.js

@@ -1 +0,0 @@
-import{b as r}from"./_baseUniq-C-qj6E4l.js";var e=4;function a(o){return r(o,e)}export{a as c};