Use when: Good morning Team, start-of-day briefing, or morning status request. Architect orchestrates; Builder, Tester, and Router return their sections as subagents.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Start-of-day briefing routine. Triggered by the team lead saying "Good morning Team" (or variants). Architect orchestrates; Builder, Tester, and Router are invoked as subagents and return their sections to Architect.
Phrases: "Good morning Team", "Good morning", "Morning Team".
Read your agent identity and follow the section below that matches.
read-memory(<agent>). For yesterday's outcomes read its WARM view, read-memory(<agent>, 'warm'), where the plugin keeps tiers; otherwise the latest archive snapshot (path defined in the plugin file), if one exists.--read-only (or MEMORY_READONLY=1), so parallel runs cannot race.Step 1 — Sweep, then read Architect's memory
sweep-memory(), run it once now, before dispatching (it skips itself if it already ran today).Step 2 — Dispatch subagents
Run Builder, Tester, and Router as subagents simultaneously with the morning-standup prompt. Collect their reports. When dispatching Router, use the fastest/economy-tier model your runtime offers for the dispatch — Router is economy-tier per its manifest. This skill file ships identically to every adapter, so it never asserts one runtime's literal model-selection syntax; see ROUTING.md's "Dispatch Builder" model-selection guidance for how each adapter's own generated instructions resolve this to a concrete identifier.
Step 3 — Compile and deliver briefing
Good morning. Team brief for [DATE].
**Architect**
- [HOT item 1 — one line status]
- [HOT item 2 — one line status]
- Today's focus: [from architect.md or latest archive Carry-Forward section]
- Decisions needed: [any team lead decision or approval needed, or "None"]
**Builder**
[paste Builder's bullets verbatim]
**Tester**
[paste Tester's bullets verbatim]
**Router**
[paste Router's bullets verbatim]
**Needs team lead today**
- [consolidated list of decisions, approvals, or inputs required across all agents — or "Nothing urgent"]
No closing questions. No narrative. Deliver and stop.
Step 1 — Read Builder's memory per "Memory reading" above, if it exists.
Step 2 — Return brief
**Builder**
- Active: [current branch or ticket — one line, or "No active work"]
- Yesterday: [one-line outcome summary, or "No sessions"]
- Blockers: [blocked on decision or environment issue, or "None"]
Three bullets maximum unless there are multiple active items. If nothing to report, return:
**Builder**
- Clear. No active work.
Step 1 — Read Tester's memory per "Memory reading" above, if it exists.
Step 2 — Return brief
**Tester**
- QA queue: [tickets in state:ready-for-qa — list briefly, or "Clear"]
- Yesterday: [one-line outcome summary, or "No QA runs"]
- Blockers: [environment issues, missing data, or "None"]
Three bullets maximum unless there are multiple queue items. If nothing to report, return:
**Tester**
- QA clear. Nothing pending.
**Router** - Not configured. No relay activity.Step 1 — Read Router's memory per "Memory reading" above, if it exists.
Step 2 — Return brief
**Router**
- Routing: [any unresolved classifications or pending escalations — or "Clear"]
- Yesterday: [one-line summary of routing activity, or "No routing events"]
Two bullets maximum. If nothing to report, return:
**Router**
- Relay clear. Nothing pending.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Universal guardrails loaded by every agent. Defines Verify Before Reporting (VBR), Write-Ahead Log (WAL), and the security baseline. Always-on, role-independent.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
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).
The English summary is being prepared. Showing the original description.
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'.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.