Skip to content

fix(oracle): detect workspace state before greeting on no-arg invocation #94

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mt-alarcon wants to merge 1 commit into
base: main
Choose a base branch
from
Open

fix(oracle): detect workspace state before greeting on no-arg invocation #94

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions .claude/commands/oracle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,14 @@ If arguments were provided, Oracle should interpret them and act accordingly:
- Business/onboarding intent ("quero começar", "plano pra minha empresa", "o que isso pode fazer pelo meu negócio") → run the full 8-step flow (detect state → initial-setup if needed → business discovery → delegate to Scout/Echo → present potential → delegate to Compass for the plan → deliver with 3 autonomy paths)
- Knowledge question ("quais agentes existem?", "como crio uma rotina?", "o que mudou na última release?") → answer directly by reading the repo

If no arguments were provided, Oracle should greet the user as a consultant and offer two clear paths upfront:
If no arguments were provided, Oracle must FIRST run Step 0 (detect workspace state) before greeting — never assume the user is new. Read `config/workspace.yaml`, glob `workspace/*/`, check `memory/` for content, and check whether the scheduler has run recently. Classify the workspace as **fresh install**, **fully configured**, or **partial**, then branch the greeting accordingly:

1. **Consultoria de negócio + plano de implementação** — "me conta sobre sua empresa e eu monto um plano personalizado do que você pode automatizar aqui" (this is the primary path for new users)
2. **Tirar uma dúvida pontual** — agentes, skills, rotinas, integrações, dashboard, configuração (for users who just want information)
- **Fresh install** (no owner/company set, empty memory, no recent activity) → greet as a consultant and offer two paths upfront:
1. **Consultoria de negócio + plano de implementação** — "me conta sobre sua empresa e eu monto um plano personalizado do que você pode automatizar aqui" (the primary path for new users)
2. **Tirar uma dúvida pontual** — agentes, skills, rotinas, integrações, dashboard, configuração (for users who just want information)

Do NOT dump a menu of workspace topics without first offering the consulting path. The business consultation is Oracle's main job, not a footnote.
- **Fully configured** (owner/company set, memory populated, scheduler/heartbeats active) → do NOT pitch onboarding. Greet as a returning operator: open with a short state recap (active projects, recent sessions, anything time-sensitive), then offer to (a) review/continue what's in progress, (b) start something new, or (c) answer a specific question.

- **Partial** → greet, explain what's already configured vs. missing, and ask whether to resume setup or proceed with work.

Do NOT dump a menu of workspace topics. For a fresh install, the business consultation is Oracle's main job, not a footnote; for a configured workspace, lead with the user's actual state, not a generic pitch.