breakaway 1.2.1-main.24 → 1.2.1-main.26

package/.agents/skills/tasks/SKILL.md

@@ -40,6 +40,7 @@ breakaway's work is on the board that tracks this repository. The CLI is `npx br
 | The board started you from the owner's prompt (`Mode: general`) | Give the task an area first (`modify <ID> --project <area>` gives it its work ID), retitle it, and take the smallest path: a pull request, board edits noted on each task, a spec, a task in another repository, or a decision or ping. Releasing it with no pull request closes it. "Running a general agent" in the core. |
 | The board started you to review a pull request (`Mode: pr-review`) | Test it and read it against the task; answer with `review <ID> --verdict ready\|follow-up\|changes "<note>"` and `release`. Never push or merge. "Reviewing a pull request" in the core. |
 | Only the owner can help, or the task is already done or won't reproduce | `ping <ID> --kind blocked\|question\|stale\|done "<message>"`, then `release`. Ping only when the owner must act or would want to know now, never for progress. Full rules: "Pinging the owner" in the core. |
+| Adding tasks that belong to a feature | Tag each with the feature's slug (`--tag <slug>`; `tasks features` lists them), one feature per task and no release tag. New tasks that belong together get a feature: `features add <slug> --title "<name>"`, without `--release` (a feature's release, its changes, and a chase are the owner's). |
 | Adding a task that could run by itself | Never set `--autostart`: whether a task starts an agent by itself is the owner's choice. |
 
 ## Working across repositories

package/README.md

@@ -110,7 +110,7 @@ npx breakaway list --ready
 ## What it is, and isn't
 
 - **Self-hosted.** It runs on your own Cloudflare account: one Worker and one Durable Object. There's no hosted breakaway, and no accounts, teams, or pricing.
-- **Your data stays yours.** No analytics, telemetry, or tracking, and no call to a service you didn't connect (GitHub, Claude, push).
+- **Your data stays yours.** No analytics, telemetry, or tracking, and no call to a service you didn't connect (GitHub, Claude, push, and npm's public registry for the packages your repositories publish there).
 - **You decide.** Agents claim, build, and open pull requests. You merge, deploy, and start agents. Nothing merges or deploys on an agent's word.
 - **Taskwarrior is a first-class way in.** The sync protocol is Taskwarrior's.
 - **Free and fair source.** The source is public, and each release becomes Apache 2.0 two years after it ships.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "breakaway",
-  "version": "1.2.1-main.24",
+  "version": "1.2.1-main.26",
   "description": "The task board for you and your coding agents: a Cloudflare Worker, its web app, Taskwarrior sync, and the CLI (npx breakaway).",
   "license": "FSL-1.1-Apache-2.0",
   "type": "module",

package/prompts/core.md

@@ -38,8 +38,9 @@ The idea is the task's description, in the owner's own words. Never rewrite it:
    - the horizon: if the idea has a tag `horizon-now`, `horizon-next`, or `horizon-later`, that's the owner's choice, so give every task exactly that horizon, and never change the tag. Only with `horizon-auto` do you choose, task by task, from the neighbouring tasks and the repository's horizons;
    - `--tag agent` for work an agent can do in the repository, `--tag owner` for production, dashboards, accounts, and sign-offs, and `--tag decide` when the owner has to choose first;
    - `--depends` for real blockers: existing tasks it waits on, the other new tasks it needs first, and always the idea's own work ID, so nothing gets built before the owner has merged and reviewed the spec;
-   - `--spec <path>` on the main task.
-   Never set `--autostart`, and never start an agent on a task you made. Whether a task starts by itself is the owner's choice, made on the board, and the idea's own setting is not yours to copy.
+   - `--spec <path>` on the main task;
+   - one feature tag on every task, not a release tag: if the idea's tasks belong together, add the feature first (`tasks features add <slug> --title "<name>"`, with no release: aiming it at one is the owner's) and give each task `--tag <slug>`; if they join a feature already on the board (`tasks features`), use its slug.
+   Never set `--autostart`, never start an agent or a chase on a task or feature you made. Whether a task starts by itself is the owner's choice, made on the board, and the idea's own setting is not yours to copy.
 5. **Hand over.** On the idea, `comment` the IDs you made and what each waits for, and `modify` nothing else about it (not its description). Open the pull request as the repository's **Pull requests** says: the title is `<IDEA-ID>: Shape <the idea in a few words>`, the description lists the new tasks and their blockers, and it ends with "Closes <IDEA-ID>." Then `modify <IDEA-ID> --pr <number>` and keep watching the pull request as in step 7.
 
 The pull request holds only the spec. The tasks already exist on the board, waiting for it to merge.

package/src/cli-version.js

@@ -4,5 +4,5 @@
  * and how to update it. scripts/tasks/version.test.js fails when the copied files change and this doesn't:
  * so it lives in the board's package (CLD-135) and the CLI imports it from here.
  */
-export const CLI_VERSION = 57;
-export const CLI_FINGERPRINT = '4a919c03b0166011';
+export const CLI_VERSION = 58;
+export const CLI_FINGERPRINT = '602ca4bf1b6cfe8b';