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월 14일 업데이트
무료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
| State | Trigger signals | Route 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 action | None — Router composes short ack |
unclear | Missing issue/PR, state, owner, or requested action | Sender — 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.
리뷰
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
댓글
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
같은 저장소의 스킬
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월 14일 업데이트
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월 14일 업데이트
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월 14일 업데이트
Use when drafting a bug or defect ticket, reviewing one someone else wrote, or deciding whether a reported problem is ready to file. Keeps what the reporter actually saw separate from what the agent later found out, so a reader can tell which lines are testimony and which are collected proof. Trigger phrases: 'file a bug', 'write up this defect', 'triage this report', 'is this ticket ready to file', 'what did the reporter actually see'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Agistra/agistra.dev52026년 10월 14일 업데이트
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월 14일 업데이트