neo-agent-skills 0.1.46 → 0.1.48

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -49,6 +49,7 @@ Each sub the decomposition creates MUST be a **leaf that a single PR can FULLY d
49
49
  ## Procedure
50
50
 
51
51
  1. **Confirm Epic-shape, then run §1a arm `(v)`.** The work needs ≥2 coordinated subs; a single bounded artifact (≈1 PR's worth) is a standalone ticket (`ticket-create`), not an Epic. Arm `(v)` — the epic-layer sweep, mandatory before authoring — compares **terminal predicates**, not titles, reading every open `label:epic` issue's `Terminal predicate:` line and only the bodies an outcome-overlap query ranks.
52
+ - **Size:** Around 25 subs is the working size; an epic is a checkable outcome, and past that count the leaves no longer share one (GitHub's native sub-issue cap of 100 per parent on `POST /issues/{n}/sub_issues` is the hard wall, not the target). Count the parent's subs before filing under it (`gh api repos/<r>/issues/N/sub_issues --paginate --jq length`); past ~25, file a successor epic with its own `Terminal predicate:` and link the new leaf there. A saturated epic gets the closeout treatment: cluster its open subs into outcomes, file the successors, re-parent, and resolve the old one via `epic-resolution`.
52
53
  2. **Run the Agent OS structure map.** Before authoring the body, run `npm run ai:structure-map -- --files --loc`; use it for Agent OS / architecture placement claims or record N/A. Brain-hosted, so absent elsewhere — never add `--silent`, which hides npm's `Missing script` and leaves an empty exit-1 that reads as a pass.
53
54
  3. **Graduation gate (if from a Discussion).** High-blast Epics require the §6.2 family-keyed quorum + the §5.1 divergence matrix in the source Discussion before filing (per `ideation-sandbox-workflow.md` + `ideation-sandbox/audits/double-diamond-divergence-guard.md`). Carry the `Signal Ledger` / dissent / liveness / criteria-mapping sections into the body.
54
55
  4. **Author the body** = the `Terminal predicate:` line, then problem-scope + intended-solution (+ ledger if graduated). NO ACs, NO sub-list.
@@ -187,7 +187,7 @@ The `create_issue` tool returns the new issue number. The ownership disposition
187
187
 
188
188
  - **Ownership disposition — exactly one arm, every ticket:** a non-empty `assignees` (you are taking it), an explicit named addressee (you are handing it over — their handle in `assignees`, or a one-line `handoff: @handle` in the body), or a one-line `unowned-rationale:` in the body (you are parking it, and you say why). Unowned is allowed; *silently* unowned is not — the rationale is what lets the next reader tell parked from dropped. Taking it is **`manage_issue_assignees(action: 'add', issue_number: N, assignees: ['@me'])`**, **MANDATORY before editing any tracked file** (AGENTS.md §0 Invariant 7). No intent-to-start condition: a **finding** never satisfies one, and findings are what orphans (`#34`). (Once `#11308` lands atomic assignee injection, the arms attach to the tool contract and this collapses to a pointer.)
189
189
  - **`manage_issue_labels(action: 'add', ...)`** — only if the label set needs adjustment post-creation (e.g., label list was incomplete at `create_issue` time). Prefer getting labels right in the initial call.
190
- - **`update_issue_relationship(parent_id: N, child_id: M, type: 'SUB_ISSUE')`** — required when filing sub-issues under an Epic. Native graph linkage only; do NOT rely on inline `- [ ] #N` markdown checkboxes (see §6).
190
+ - **`update_issue_relationship(parent_id: N, child_id: M, type: 'SUB_ISSUE')`** — required when filing sub-issues under an Epic. Native graph linkage only; do NOT rely on inline `- [ ] #N` markdown checkboxes (see §6). Count the parent's subs first (`gh api repos/<r>/issues/N/sub_issues --paginate --jq length`); past ~25, file or link to a successor epic (`epic-create` Procedure 1).
191
191
  - **Ticket body edits:** Update GitHub directly with `gh issue edit N --body-file <path>` (or the equivalent live GitHub write surface). GitHub remains canonical; scheduled mirroring may lag.
192
192
  - **Picking up the ticket:** If you intend to start working on this newly created ticket immediately, you MUST run the `ticket-intake` skill next (your assignee claim fulfills the primary gate).
193
193
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "neo-agent-skills",
3
- "version": "0.1.46",
3
+ "version": "0.1.48",
4
4
  "description": "Install the workflow substrate a cross-model AI team actually runs on: ticket intake, PR review gates, lane coordination and guards, versioned as a package. The skills Neo.mjs maintainers load every session — materialized into your repo, not copied.",
5
5
  "type": "module",
6
6
  "license": "MIT",