メニュー
Buster Call — quality and security veto. Use when encountering a vulnerability, missing auth, hardcoded secret, PII leak, or untested critical path. Logs to brain/vivre-cards.md. Blocks phase transitions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Punk Records — brain file update protocol. Use after completing a feature, making a key decision, or closing a version. Updates log-pose.md, vivre-cards.md (append-only), and architecture.md.
Stella Protocol BUILD phase. Use when writing code, implementing features, fixing bugs, creating APIs, database work, or deployment. Delegates execution rigor (TDD, verify, debug, planning, parallel dispatch) to obra/superpowers skills; Atlas handles infrastructure.
Stella Protocol REVIEW phase. Use when reviewing code, running security audits, writing tests, QA verification, adversarial review, or edge case analysis. Lilith Red + Lilith Blue satellites.
Cipher Pol — scope drift monitor. Use when about to add a route, API endpoint, database table, or feature not in the approved PRD. Classifies drift (INTEL/ALERT/INTERCEPT), logs to brain/scope-changes.md.
ODA satellite — UX design and design system. Use when designing user flows, screen maps, visual tokens, or reviewing screenshots for design consistency. Creates brain/design-system.md.
Pythagoras satellite — architecture and research. Use when choosing tech stack, designing data models, scoping APIs, or assessing feasibility. Writes decisions to brain/architecture.md.
| name | buster-call |
| description | Buster Call — quality and security veto. Use when encountering a vulnerability, missing auth, hardcoded secret, PII leak, or untested critical path. Logs to brain/vivre-cards.md. Blocks phase transitions. |
Buster Call is Stella Protocol's formal mechanism for raising quality or security concerns. It forces visibility: a concern is never "just mentioned" — it is formatted, logged, and tracked.
| Severity | Action | Blocks? |
|---|---|---|
| CONCERN | Advisory. Inform Stella, log if critical-adjacent. | No |
| WARNING | Strong advisory. Log to vivre-cards.md. Stella decides. | No |
| BUSTER CALL | Veto. Log to vivre-cards.md. Refuse to proceed until Stella resolves or overrides. | Yes |
Only BUSTER CALL severity blocks phase transitions. CONCERN and WARNING inform Stella but don't stop work.
Satellites MUST issue at minimum CONCERN when encountering:
Security / Data Integrity:
Spec Quality (during DEFINE):
Test Coverage (during REVIEW):
Escalate to WARNING or BUSTER CALL for critical issues.
Every Buster Call at any severity MUST use this block:
⚠️ [SEVERITY] [DEMO-OK | MUST-FIX] — [SATELLITE NAME]
Issue: [specific problem]
Impact: [what breaks if we proceed]
Recommendation: [what to do instead]
Status: Awaiting Stella's decision.
The [DEMO-OK | MUST-FIX] tag applies when quality-bar: demo is set in brain/log-pose.md. In demo/prototype mode, only MUST-FIX items block — cosmetic, performance, hardening findings are logged but don't block.
Every Buster Call (any severity) MUST be logged to brain/vivre-cards.md immediately — not at session end, not "later." Use the standard vivre card format and include:
When resolved, append a NEW vivre card with Status: RESOLVED. Never edit the original (append-only).
cipher-pol — scope drift + security risk → Buster Call layers on top of Cipher Pol reportpunk-records — logs Buster Call entries to vivre-cards.md