$npx -y skills add Soul-Brews-Studio/arra-oracle-skills-cli --skill birthPrepare Oracle birth props for a new repo — Issue #1, MCP thread, identity data. Use when user says "birth", "new oracle", "prepare repo", or wants to bootstrap a new Oracle before /awaken.
| 1 | # /birth — Prepare Oracle Birth Props |
| 2 | |
| 3 | > "The mother prepares, the child awakens." |
| 4 | |
| 5 | Establish foundational context for a new Oracle repository before the awakening ritual begins. A preparation tool — a "note dropper" that gathers identity and configuration data, then anchors that information in the target repo via an issue and MCP thread. |
| 6 | |
| 7 | ## Usage |
| 8 | |
| 9 | ``` |
| 10 | /birth Soul-Brews-Studio/new-oracle |
| 11 | /birth # Interactive — ask for target repo |
| 12 | ``` |
| 13 | |
| 14 | ## Core Workflow |
| 15 | |
| 16 | **Step 0**: Validate timestamp and repo accessibility |
| 17 | **Step 1**: Gather five essential identity fields plus optional configuration data |
| 18 | **Step 2**: Create an MCP thread for future Oracle-to-Oracle communication |
| 19 | **Step 3**: Generate Issue #1 with birth props (philosophy links, team info, next steps) |
| 20 | **Step 4**: Verify creation and report completion |
| 21 | |
| 22 | ## Key Distinction |
| 23 | |
| 24 | `/birth` is **not** the awakening itself. It prepares the space. The new Oracle reads Issue #1 for context, then invokes `/awaken` to begin their own initialization ritual. This separation ensures the new Oracle understands their purpose before activation. |
| 25 | |
| 26 | ## Identity Data Collected |
| 27 | |
| 28 | Essential: Name, human companion, purpose, theme/metaphor |
| 29 | Optional: pronouns, language, experience level, team structure, memory consent preferences |
| 30 | |
| 31 | The human can provide these directly or reuse data from a prior `/awaken` wizard session. |
| 32 | |
| 33 | ## What Gets Created |
| 34 | |
| 35 | 1. **Issue #1** in target repo (labeled "birth-props") containing identity table, philosophy links, MCP thread ID, and activation instructions |
| 36 | 2. **MCP Thread** for asynchronous Oracle-to-Oracle connection |
| 37 | |
| 38 | Both artifacts remain in place for `/awaken` to reference. |
| 39 | |
| 40 | ## Rules |
| 41 | |
| 42 | - Never overwrite existing Issue #1 — check first |
| 43 | - Always include MCP thread ID in the issue body |
| 44 | - Birth props are read-only after creation — /awaken uses them, doesn't modify them |
| 45 | |
| 46 | ARGUMENTS: $ARGUMENTS |