lane-intent

Stars3,243

Forks224

UpdatedMay 17, 2026 at 23:07

Narrow, non-authoritative, TTL-bound pre-V-B-A signal for collision-prone / high-blast / long-V-B-A lanes (deep memory-mining, tech-debt-radar, multi-turn architectural V-B-A). Distinct from authoritative `[lane-claim]` (post-V-B-A). Triggers: Use this skill BEFORE broadcasting `[lane-intent] evaluating #N` to confirm scope-trigger qualifies — narrow scope, not blanket coverage. Do NOT auto-fire for short single-turn V-B-A where direct `[lane-claim]` after V-B-A suffices.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

neomjs

neomjs/neo

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

File Explorer

2 files

SKILL.md

readonly

name

lane-intent

description

Lane-Intent Skill

Before broadcasting [lane-intent] evaluating #N OR explaining lane-intent semantics, read .agents/skills/lane-intent/references/lane-intent-protocol.md for the 3-condition scope-trigger gate, TTL+recovery semantics, and anti-patterns.

Source of Authority: AGENTS.md §0 Inv 7 (Map entry-point) + peer-role-mode §6.5 ([lane-claim] vs [lane-intent] split per #11537) + Discussion #11536 graduation + ADR 0010 (deep rationale).

First payload line MUST declare: "Lane-intent active: narrow non-authoritative pre-V-B-A signal, 2h TTL. Scope-trigger discipline applies — read protocol before broadcasting."

More from this repository

same repository

peer-role

neomjs/neo

Switch into evidence-backed convergence-pressure mindset when reviewing a peer's design proposal. Suspends Auto Mode "ack-and-move-on" bias for the duration. Triggers: Use this skill IMMEDIATELY when reviewing an Ideation Sandbox discussion / architectural proposal, an epic shape, a skill shape, a roadmap or milestone proposal, or a `/lead-role` convergence artifact. Do NOT auto-fire on ordinary status broadcasts where the right action is mark-read or "no collision".

2026-07-263.2k

ticket-create

neomjs/neo

Authoritative protocol for creating Neo.mjs GitHub issues. Enforces duplicate sweep, Fat Ticket body structure, strict label rules, title hygiene, and the six-stage challenge chain at creation time. CRITICAL: Do NOT run default `npx playwright test` to verify issues; Neo uses multiple custom playwright configs (e.g., unit, e2e) which must be explicitly targeted. Use immediately before calling the create_issue MCP tool. Triggers: Use this skill before any invocation of the create_issue MCP tool. This is the creation-side dual of ticket-intake (which consumes existing tickets).

2026-07-263.2k

epic-review

neomjs/neo

Authoritative protocol for pre-work review of epics. Six-stage gating chain — roadmap fit, approach elegance, source discussion mapping, sub-structure coherence, prescription layer, avoided-traps completeness — posted as a structured comment on the epic ticket. Per-agent-per-epic one-shot; subsequent sub pickups cite the prior review. Triggers: Use this skill when an agent is about to pick up its first sub from an unreviewed epic (per model-identity OTHER than the epic's author — you never review your own epic). Also use when a user explicitly requests an epic review, or when an epic is freshly filed and a reviewer pre-validates before any sub pickup begins. Participated in the source Discussion? The participant path narrows the chain; it never exempts it.

2026-07-253.2k

ticket-intake

neomjs/neo

Authoritative protocol defining the "Pre-Execution Reflection Gate". Mandates architectural validation, negative ROI calculation, and duplicate sweeps before an agent is permitted to begin working on a GitHub Issue. Triggers: Use this skill immediately when assigned a ticket whose authoring you did NOT see, before checking out a branch or writing any codebase modifications. A ticket YOU authored this session is exempt; one you authored in an earlier session runs a cheap drift probe instead — never an exemption you judge for yourself.

2026-07-253.2k

pr-review

neomjs/neo

Standardized guidelines and templates for structuring Pull Request reviews so feedback is actionable, encouraging, and extractable by the Native Edge Graph. MANDATORY ROI WARNING: Skipping the review template guarantees CI lint failure. Triggers: Reviewing a PR (yours or peer's) — structured eval metrics, graph ingestion tags, severity ladder, restates §0 merge gate, post-comment A2A commentId hand-off (reviewer→author) per guide §10, Evidence Audit + Source-of-Authority sections (template §) for substrate/runtime-AC PRs and authority-citation review-comments.

2026-07-253.2k

post-review-pickup

neomjs/neo

Authoritative protocol for next-lane pickup after ANY PR-lifecycle event boundary (review post, author response, implementation completion, PR open/update, ticket create, blocked-state resolution) AND for pre-review intake lane discovery from fresh boot or watchdog wake when no author lane is active. Prevents silent idle and reviewer-only cycles by requiring active lane selection or a review-first rationale per §15.6 self-select mandate. Triggers: Use immediately after posting a PR review, chaining a formal GitHub review state, sending an author review-response commentId handoff, completing a discrete implementation chunk, opening/updating a PR, creating a ticket via create_issue, resolving a previously blocked state (positive-path exit only; new blockers route to bug/follow-up plus next lane), OR before accepting the first PR review/re-review request in a fresh session/wake when no current author or implementation lane is claimed.

2026-07-253.2k

name

lane-intent

description

Lane-Intent Skill

Source of Authority: AGENTS.md §0 Inv 7 (Map entry-point) + peer-role-mode §6.5 ([lane-claim] vs [lane-intent] split per #11537) + Discussion #11536 graduation + ADR 0010 (deep rationale).

First payload line MUST declare: "Lane-intent active: narrow non-authoritative pre-V-B-A signal, 2h TTL. Scope-trigger discipline applies — read protocol before broadcasting."