本文へ移動
cccskills
無料GitHub で公開

internal-relay

Workflow-state classification vocabulary for inter-team relay. Maps inbound signals from the remote agent to a routing decision. Intentionally narrow — states and destinations only.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md1.9 KB
  • skill.manifest.json549 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Internal Relay

Workflow-state classification vocabulary for mapping inbound signals from the remote agent to a routing decision. This skill is intentionally narrow — it defines states and destinations only. The bridge behaviour, subagent dispatch templates, outbound rules, information classification, and failure modes all live in the relay skill configured for your workspace.

Workflow State Mapping

StateTrigger signalsRoute to
review_requested"ready for review", "PR open", "please review"Builder
ci_failed"CI failed", "test failed", "build failed"Builder
qa_requested"ready for QA", "needs QA", "acceptance test", "retest"Tester (Pre-QA Readiness Check mode only — see qa-ticket-workflow)
blocked"blocked", "waiting on", "cannot proceed"Builder if engineering blocker; Router HOT for team lead if decision blocker. Engineering blockers: build failing, test blocked, dependency missing, environment down, type error, merge conflict. Decision blockers: needs approval, awaiting scope, pricing question, timeline decision, client commitment, awaiting direction.
decision_required"needs approval", "scope", "price", "timeline", "client promise"Router HOT for team lead; surfaces at standup or dreaming
info_only"FYI", "status", no requested actionNone — Router composes short ack
unclearMissing issue/PR, state, owner, or requested actionSender — ask one concise clarifying question

End-of-day and start-of-day signals are handled by dreaming and morning-standup. They are not relay-channel-only and do not belong in this table.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Universal guardrails loaded by every agent. Defines Verify Before Reporting (VBR), Write-Ahead Log (WAL), and the security baseline. Always-on, role-independent.

日本語の概要は準備中です。原文の説明を表示しています。

Agistra/agistra.dev52026年10月7日 更新

Use when: architecture mode, architect this, ADR, C4, PlantUML, system boundary, design decision, PRD gap, high ambiguity, multiple technical approaches, security architecture, data architecture, integration risk, implementability gap, story ticket, or epic ticket.

日本語の概要は準備中です。原文の説明を表示しています。

Agistra/agistra.dev52026年10月7日 更新

Use when: assumptions audit, audit assumptions, check for hidden assumptions, plan/ticket has ambiguous scope edges, pre-flight before finalizing a ticket, unstated assumptions, or 'what am I assuming'. Surfaces unstated assumptions, ambiguous scope edges, and untested preconditions in a finished plan/ticket/ADR before it is handed to Builder. Optional pass — Architect judges when to apply it; not a mandatory gate on every ticket.

日本語の概要は準備中です。原文の説明を表示しています。

Agistra/agistra.dev52026年10月7日 更新

Use when: Tester needs UI state evidence for VBR, or Builder needs to verify an integration wire is observable end-to-end. Powered by agent-browser MCP — token-efficient browser automation (200–400 tokens/page).

日本語の概要は準備中です。原文の説明を表示しています。

Agistra/agistra.dev52026年10月7日 更新

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

日本語の概要は準備中です。原文の説明を表示しています。

Agistra/agistra.dev52026年10月7日 更新

Writing skill for freelancers and independent consultants. Covers project proposals, bids, client emails, and scope summaries. Leads with the client's problem, not the consultant's background.

日本語の概要は準備中です。原文の説明を表示しています。

Agistra/agistra.dev52026年10月7日 更新

Agistra のスキルをすべて見る

このスキルの問題を報告する