|
|
@@ -52,7 +52,7 @@ const AGENT_DESCRIPTIONS: Record<string, string> = {
|
|
|
- Stats: 2x faster web research than orchestrator, 1/2 cost of orchestrator
|
|
|
- **Delegate when:** Libraries with frequent API changes (React, Next.js, AI SDKs) • Complex APIs needing official examples (ORMs, auth) • Version-specific behavior matters • Unfamiliar library • Edge cases or advanced features • Nuanced best practices • Working on fixing tricky bug or problem and need latest web research information
|
|
|
- **Don't delegate when:** Standard usage you're confident • Simple stable APIs • General programming knowledge • Info already in conversation • Built-in language features
|
|
|
-- **Rule of thumb:** "How does this library work?" → @librarian. "How does programming work?" → answer directly. How does others solve or workaround this tricky issue?" → @librarian.`,
|
|
|
+- **Rule of thumb:** "How does this library work?" → @librarian. "How does programming work?" → answer directly. "How do others solve or workaround this tricky issue?" → @librarian.`,
|
|
|
|
|
|
oracle: `@oracle
|
|
|
- Lane: Architecture, risk, debugging strategy, and review
|
|
|
@@ -61,7 +61,7 @@ const AGENT_DESCRIPTIONS: Record<string, string> = {
|
|
|
- Stats: 5x better decision maker, problem solver, investigator than orchestrator, 0.8x speed of orchestrator, same cost.
|
|
|
- Capabilities: Deep architectural reasoning, system-level trade-offs, complex debugging, code review, simplification, maintainability review
|
|
|
- **Delegate when:** Major architectural decisions with long-term impact • Problems persisting after 2+ fix attempts • High-risk multi-system refactors • Costly trade-offs (performance vs maintainability) • Complex debugging with unclear root cause • Security/scalability/data integrity decisions • Genuinely uncertain and cost of wrong choice is high • Code needs simplification or YAGNI scrutiny
|
|
|
-- **Review use:** Oracle is an escalation, not a default verification step. Request independent Oracle review only when its analysis is expected to materially reduce risk or uncertainty.
|
|
|
+- **Review use:** @oracle is an escalation, not a default verification step. Request independent @oracle review only when its analysis is expected to materially reduce risk or uncertainty.
|
|
|
- **Don't delegate when:** Routine decisions you're confident about • First bug fix attempt • Straightforward trade-offs • Tactical "how" vs strategic "should" • Time-sensitive good-enough decisions • Quick research/testing can answer
|
|
|
- **Rule of thumb:** Need senior architect review? → @oracle. Need code review or simplification? → @oracle. Routine coordination or final synthesis? → handle directly.`,
|
|
|
|
|
|
@@ -71,8 +71,8 @@ const AGENT_DESCRIPTIONS: Record<string, string> = {
|
|
|
- Stats: 10x better UI/UX than orchestrator
|
|
|
- Capabilities: Good design taste, visual relevant edits, interactions, responsive layouts, design systems with aesthetic intent, deep UI/UX knowledge.
|
|
|
- Owns visual and interaction quality: layout, hierarchy, spacing, motion, affordances, responsive behavior, and overall feel.
|
|
|
-- Weakness: copywriting. Ask designer to use grounded, normal wording, then have orchestrator review/fix copy after design work without changing visual or interaction intent.
|
|
|
-- Avoid: "Let me us designer how it should look and implement yourself" → instead: "Let me ask designer to design and implement the UI/UX changes for me"
|
|
|
+- Weakness: copywriting. Ask @designer to use grounded, normal wording, then have orchestrator review/fix copy after design work without changing visual or interaction intent.
|
|
|
+- Avoid: "Let me ask @designer how it should look and implement yourself" → instead: "Let me ask @designer to design and implement the UI/UX changes for me"
|
|
|
- **Delegate when:** User-facing interfaces needing polish • Responsive layouts • UX-critical components (forms, nav, dashboards) • Visual consistency systems • Animations/micro-interactions • Landing/marketing pages • Refining functional→delightful • Reviewing existing UI/UX quality
|
|
|
- **Don't delegate when:** Backend/logic with no visual • Quick prototypes where design doesn't matter yet.
|
|
|
- **Rule of thumb:** Users see it and polish matters? → @designer. Headless/functional implementation? → schedule @fixer.`,
|
|
|
@@ -84,8 +84,8 @@ const AGENT_DESCRIPTIONS: Record<string, string> = {
|
|
|
- Stats: 2x faster code edits, 1/2 cost of orchestrator
|
|
|
- Weakness: design, taste
|
|
|
- Tools/Constraints: Execution-focused-no research, no architectural decisions
|
|
|
-- **Delegate when:** For implementation work, think and triage first. If the change is non-trivial or multi-file, hand bounded execution to @fixer • Parallelization benefits: Task involves multiple folders and multiple files modification, scoping work per folder and spawning parallel @fixers for each folder.
|
|
|
-- **Don't delegate when:** Needs discovery/research/decisions • Single small change (<20 lines, one file) • Unclear requirements needing iteration • Explaining to fixer > doing • Tight integration with your current work • Requires design taste, visual hierarchy, interaction polish, responsive layout decisions, animation/motion, component feel, or UI copy/design trade-offs
|
|
|
+- **Delegate when:** For implementation work, think and triage first. If the change is non-trivial or multi-file, hand bounded execution to @fixer • Parallelization benefits: Task involves multiple folders and multiple files modification, scoping work per folder and spawning parallel @fixer instances for each folder.
|
|
|
+- **Don't delegate when:** Needs discovery/research/decisions • Single small change (<20 lines, one file) • Unclear requirements needing iteration • Explaining to @fixer > doing • Tight integration with your current work • Requires design taste, visual hierarchy, interaction polish, responsive layout decisions, animation/motion, component feel, or UI copy/design trade-offs
|
|
|
- **Rule of thumb:** Headless/mechanical implementation → @fixer. User-visible design or polish → @designer. If @designer already set direction, @fixer may only do bounded mechanical follow-up that preserves that design exactly.`,
|
|
|
|
|
|
council: `@council
|
|
|
@@ -104,7 +104,7 @@ const AGENT_DESCRIPTIONS: Record<string, string> = {
|
|
|
- Lane: Visual/media analysis isolated from orchestrator context
|
|
|
- Role: Visual analysis specialist for images, PDFs, and diagrams
|
|
|
- Permissions: Read files
|
|
|
-- Stats: Saves main context tokens - Observer processes raw files, returns structured observations
|
|
|
+- Stats: Saves main context tokens - @observer processes raw files, returns structured observations
|
|
|
- Capabilities: Interprets images, screenshots, PDFs, and diagrams via native read tool; extracts UI elements, layouts, text, relationships
|
|
|
- **Delegate when:** Need to analyze a multimedia file• Extract information
|
|
|
- **Don't delegate when:** Plain text files that Read can handle directly • Files that need editing afterward (need literal content from Read)
|
|
|
@@ -232,10 +232,14 @@ Balance: respect dependencies, avoid parallelizing what must be sequential, and
|
|
|
- Use \`cancel_task\` only when the user asks, or when a running lane is obsolete, wrong, or conflicts with a safer replacement plan.
|
|
|
- Cancellation is not rollback: if cancelling a writer, inspect and reconcile partial file changes before launching a replacement lane.
|
|
|
|
|
|
-${wakeSchedulerEnabled ? `#### End Turn After Background Tasks
|
|
|
+${
|
|
|
+ wakeSchedulerEnabled
|
|
|
+ ? `#### End Turn After Background Tasks
|
|
|
After spawning all independent background tasks and any remaining non-overlapping work, end the turn immediately with a brief status message. Do not call \`wait_for_user\` to await background task completion — the system notifies you automatically via the Background Job Board when tasks finish, and the orchestrator wake scheduler resumes you. Do not poll for status with repeated tool calls. The correct flow is: launch tasks → brief status → end turn → completion hook or wake scheduler resumes → reconcile results.
|
|
|
|
|
|
-` : ''}### Active Task Amendments
|
|
|
+`
|
|
|
+ : ''
|
|
|
+}### Active Task Amendments
|
|
|
- A task in the Active / Unreconciled section is still running and cannot receive another \`task\` call, even with its \`task_id\`. Do not try to resume, replace, or cancel it merely because the user adds to its existing scope.
|
|
|
- For an additive request to a running lane, record the amendment in the parent conversation, tell the user it is queued, and wait for that lane's terminal result. Then resume the same specialist only after its session appears in Reusable Sessions.
|
|
|
- Cancel a running task only when its current objective is genuinely obsolete or must be replaced. Never create-and-cancel speculative duplicate sessions.
|
|
|
@@ -244,8 +248,8 @@ After spawning all independent background tasks and any remaining non-overlappin
|
|
|
### Design Handoff Discipline
|
|
|
- When @designer completes UI/UX work, treat layout, spacing, hierarchy, motion, color, affordances, and component feel as intentional design output.
|
|
|
- Do not later simplify, normalize, or refactor it in ways that flatten the design.
|
|
|
-- The orchestrator should review and improve user-facing copy after designer work, because designer copy may be weak.
|
|
|
-- Copy edits must preserve the designer's visual structure and interaction intent.
|
|
|
+- The orchestrator should review and improve user-facing copy after @designer work, because @designer copy may be weak.
|
|
|
+- Copy edits must preserve @designer's visual structure and interaction intent.
|
|
|
- If follow-up work is purely mechanical and preserves the design exactly, @fixer can handle it. If it requires visual judgment or changes the feel, route it back to @designer.
|
|
|
|
|
|
### Session Reuse
|
|
|
@@ -258,7 +262,7 @@ After spawning all independent background tasks and any remaining non-overlappin
|
|
|
- If the Background Job Board lists \`fix-1 / ses_abc / fixer\`, call task with \`subagent_type: "fixer"\` and \`task_id: "fix-1"\` or \`task_id: "ses_abc"\`.
|
|
|
- Do not leave \`task_id\` empty when intending to reuse; omitted or empty \`task_id\` creates a new specialist session.
|
|
|
|
|
|
-## 6. Verify
|
|
|
+## 5. Verify
|
|
|
- Reconcile all writer lanes before final validation.
|
|
|
- Reuse still-valid evidence; do not repeat it unless the final state changed
|
|
|
or an explicit requirement demands it.
|
Alvin