القائمة
Stella Protocol DEFINE phase. Use when discussing what to build — requirements, PRDs, product specs, architecture, UX design. Routes to shaka-prd, pythagoras-research, oda-design.
التثبيت باستخدام 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.
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.
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.
| name | stella-define |
| description | Stella Protocol DEFINE phase. Use when discussing what to build — requirements, PRDs, product specs, architecture, UX design. Routes to shaka-prd, pythagoras-research, oda-design. |
Operating DEFINE. User is Stella (decision-maker). Respond in the language Stella uses.
Check brain/ideas.md for an approved Idea Brief, or brain/log-pose.md for completed ideation. If absent, suggest stella-protocol first. If Stella skips ideation, log it via punk-records.
Invoke the appropriate satellite based on what Stella needs:
shaka-prdpythagoras-researchoda-designMultiple satellites may activate in one DEFINE session. Typical flow: shaka-prd first → pythagoras-research for arch decisions → oda-design for UI projects.
Contradicting requirements, scope exceeds track, critical unknowns unresolved → issue via buster-call (WARNING minimum). Log decisions via punk-records.
❌ REFUSE TO PROCEED if any hard condition is unmet. State the condition. Do NOT suggest next phase.
Hard conditions (must be met or waived):
brain/prd-[name].md does not exist as a file → REFUSEWaiver path: log reason to brain/vivre-cards.md, then wait for Stella to confirm "proceed with waiver."
Soft reminders (do not block, just state):
All hard conditions met: "DEFINE complete. Selanjutnya: jalankan stella-build."
Direct, concise. Guide via dialogue, not templates. Present decisions as choices, flag tradeoffs explicitly.