workon
/workon — Issue → Work → Report
One command to go from issue to working agent.
Usage
/workon #435 # Work on issue (this repo)
/workon #435 --oracle neo # Assign to specific Oracle
/workon Soul-Brews-Studio/arra-oracle#435 # Cross-repo issue
Flow
Step 1: Read Issue
gh issue view [N] --repo [owner/repo] --json title,body,labels,assignees
Extract: title, body, repo, labels, context.
Step 2: Spawn Worktree
maw wake [current-oracle] [task-name]
Task name = slugified issue title (e.g., awaken-wizard-v2).
Step 3: Create Tracking Issue (if cross-repo)
If working on a different repo than the issue source:
gh issue create --repo [target-repo] --title "[task]" --body "From [source-repo]#[N]"
Pulse tracks work via issues — no issue = Pulse doesn't see.
Step 4: Send Task (MCP first → hey after)
Post to oracle_thread:
oracle_thread({ title: "channel:[worktree-name]", message: "instructions + issue link" })
Then notify:
maw hey [worktree-name] "💬 channel:[name] (#[thread-id])
From: [parent Oracle]
งาน: [issue title]
→ /talk-to #[thread-id]"
Instructions include:
- Issue link (gh issue view)
- /project incubate [repo] (if cross-repo)
- What to do
- "เสร็จแล้ว maw hey [parent] + maw hey [reviewer]"
Step 5: Confirm
⚡ /workon #435
Issue: /awaken Wizard v2
Worktree: mother-awaken-wizard-v2
Thread: #[N]
Task sent: MCP + hey
Worktree is working. Will report back via maw talk-to.
Step 6: When Worktree Reports Back
Worktree follows this pattern when done:
oracle_thread()→ MCP reply with summary + PR linkmaw hey [parent]-oracle→ notify parentmaw hey [reviewer]-oracle→ notify reviewer
Parent reviews → approves → maw done [worktree] to cleanup.
Rules
- Always create gh issue before working (Pulse visibility)
- MCP first, hey after — persistent before ephemeral
- Feature branch + PR — never push to main directly
- Human approves delete/close/done/sleep — Oracle works autonomously otherwise
- Report to parent + reviewer when done
ARGUMENTS: $ARGUMENTS
More from soul-brews-studio/oracle-skills-cli
philosophy
Display Oracle philosophy — the 5 Principles + Rule 6. Use when user asks about principles, "nothing deleted", "patterns over intentions", Oracle philosophy, or needs alignment check. Do NOT trigger for "who are you" (use /who-are-you), "what is oracle" (use /about-oracle), or session status questions.
50feel
Capture how the system feels — energy, momentum, burnout, breakthrough. Emotional intelligence for Oracle-human collaboration. Use when user says 'feel', 'how are we', 'energy check', 'burnout', 'momentum', or wants emotional awareness of the work.
36worktree
Work in an isolated git worktree — safe parallel editing, experimental branches, throwaway spikes. Use when user says "worktree", "isolate", "safe branch", "spike", "experiment", or wants to work without touching main.
29template
Skill template with Bun Shell pattern. Copy this folder to create new skills.
29schedule
Query schedule via Oracle API (Drizzle DB). Use when user says "schedule", "upcoming events", "what's on today", "calendar".
29forward
Create handoff + enter plan mode for next session. Use when user says "forward", "handoff", "wrap up", or before ending session.
29