blocked-task-state

Estrelas3.243

Forks224

Atualizado5 de junho de 2026 às 17:32

Authoritative protocol for signaling blocked or input-required task states. Mandates targeted A2A pings using the Task.state envelope rather than global capacity broadcasts. Triggers: Use this skill whenever your execution becomes blocked, requires explicit operator input, or encounters a failure that halts progress.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

neomjs

neomjs/neo

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Outras ocupações de informáticaInformática e Matemática·SOC 15-1299

Explorador de arquivos

2 arquivos

SKILL.md

readonly

name	blocked-task-state
description	Authoritative protocol for signaling blocked or input-required task states. Mandates targeted A2A pings using the Task.state envelope rather than global capacity broadcasts. Triggers: Use this skill whenever your execution becomes blocked, requires explicit operator input, or encounters a failure that halts progress.

Blocked Task-State Coordination

If you are an agent and your task transitions into a blocked, input-required, or failed state, you MUST NOT broadcast a global idle signal.

You MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/blocked-task-state/references/blocked-task-state-workflow.md before sending any A2A messages.

Mais deste repositório

mesmo repositório

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	blocked-task-state
description	Authoritative protocol for signaling blocked or input-required task states. Mandates targeted A2A pings using the Task.state envelope rather than global capacity broadcasts. Triggers: Use this skill whenever your execution becomes blocked, requires explicit operator input, or encounters a failure that halts progress.

Blocked Task-State Coordination

If you are an agent and your task transitions into a blocked, input-required, or failed state, you MUST NOT broadcast a global idle signal.

You MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/blocked-task-state/references/blocked-task-state-workflow.md before sending any A2A messages.