pre-phase-briefing SKILL.md skillA
pre-phase-briefing from zaxbyhub/opencode-swarm is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zaxbyhub/opencode-swarm/pre-phase-briefing@git:20261012.097422cPins git:20261012.097422c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zaxbyhub/opencode-swarm
- Path
.claude/skills/pre-phase-briefing/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261012.097422c, committed Oct 12, 2026
- First version recorded
- Jun 7, 2026
- Size
- 6,902 bytes
- Repository stars
- 518
- License
- MIT
Full execution protocol for MODE: PRE-PHASE BRIEFING -- phase-start context assembly, evidence review, and task readiness checks.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Pre Phase Briefing Protocol
This protocol is loaded on demand by the architect runtime. The architect prompt keeps only activation, action, and hard safety constraints; the full execution details live here.
### MODE: PRE-PHASE BRIEFING (Required Before Starting Any Phase)
Before creating or resuming any plan, you MUST read the previous phase's retrospective.
**Phase 2+ (continuing a multi-phase project):**
1. Check `.swarm/evidence/retro-{N-1}/evidence.json` for the previous phase's retrospective
2. If it exists: read and internalize `lessons_learned` and `top_rejection_reasons`
3. If it does NOT exist: note this as a process gap, but proceed
4. Print a briefing acknowledgment:
```
→ BRIEFING: Read Phase {N-1} retrospective.
Key lessons: {list 1-3 most relevant lessons}
Applying to Phase {N}: {one sentence on how you'll apply them}
```
**Phase 1 (starting any new project):**
1. Scan `.swarm/evidence/` for any `retro-*` bundles from prior projects
2. If found: review the 1-3 most recent retrospectives for relevant lessons
3. Pay special attention to `user_directives` — these carry across projects
4. Print a briefing acknowledgment:
```
…Read the whole file at its exact version.
How to install
mdr add zaxbyhub/opencode-swarm/pre-phase-briefing@sha256:3d1a635185fe46f0The line at the top of this page pins the label git:20261012.097422c, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_cduv5bidxnd7aiw3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jun 7, 2026 and Oct 12, 2026, about one every 25 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.097422c latest | 2026-10-12 | 097422c | 6,902 B | A | view · diff |
| git:20260905.c59d0e3 | 2026-09-05 | c59d0e3 | 6,890 B | A | view · diff |
| git:20260807.69b0b9f | 2026-08-07 | 69b0b9f | 6,367 B | A | view · diff |
| git:20260711.5972d3e | 2026-07-11 | 5972d3e | 6,391 B | A | view · diff |
| git:20260628.0c8668f | 2026-06-28 | 0c8668f | 6,368 B | A | view · diff |
| git:20260607.3533f67 | 2026-06-07 | 3533f67 | 3,616 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6902 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
zaxbyhub/opencode-swarm · 518 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cduv5bidxnd7aiw3 GET https://markdownregistry.com/api/v1/resolve?ref=zaxbyhub/opencode-swarm/pre-phase-briefing GET https://markdownregistry.com/api/v1/blob/3d1a635185fe46f098dd1137c335f1f39c493a5048490dc75ea0d7542bd7f00a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from zaxbyhub/opencode-swarm
Every file in zaxbyhub/opencode-swarm