[PR #3] refactor: implement prompt-first orchestrator approach #4

New issue

Open

opened 2026-03-01 14:33:51 +03:00 by kerem · 0 comments

kerem commented

2026-03-01 14:33:51 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/aeitroc/Droid-CLI-Orchestrator/pull/3
Author: @vforvaick
Created: 11/22/2025
Status: 🔄 Open

Base: main ← Head: claude/brainstorm-droid-cli-014VvoKohRnyHuefJpQoNER4

📝 Commits (7)

bfc2848 refactor: implement prompt-first orchestrator approach
25338bf fix: address CodeRabbit review feedback
8d7b056 docs: add comprehensive documentation to init-orchestrator
ad86480 feat: add interactive installer and health check tools
0a027ad refactor: rename tools to droidos-* prefix for clarity
baed9ed fix: address CodeRabbit review feedback
e663814 docs: add comprehensive changelog and clarify orchestrator modes

📊 Changes

6 files changed (+1774 additions, -618 deletions)

View changed files

📝 README.md (+211 -129)
➕ bin/droidos-doctor (+393 -0)
➕ bin/droidos-init (+491 -0)
➕ commands/init-orchestrator.md (+370 -0)
📝 commands/orchestrator.md (+28 -205)
📝 droids/orchestrator.md (+281 -284)

📄 Description

BREAKING CHANGE: Orchestrator behavior significantly changed

Changes:

Renamed commands/orchestrator.md → commands/init-orchestrator.md (comprehensive greenfield project initialization)
Created new lightweight commands/orchestrator.md (focused task execution with minimal scanning)
Completely refactored droids/orchestrator.md with "Prompt-First" philosophy

New Orchestrator Philosophy:
✅ PROMPT IS THE TRUTH - execute exactly what user asks ✅ Minimal scanning - only read files mentioned in prompt + dependencies ✅ No overengineering - don't add unrequested features ✅ Clarify ambiguity - suggest assumptions and ask for confirmation ✅ Smart delegation - use appropriate specialists for the task only

Forbidden Behaviors:
❌ Full codebase scanning unless explicitly needed
❌ Building features not mentioned in prompt
❌ Overengineering with unnecessary abstractions
❌ Comprehensive project analysis for simple tasks

Use Cases:

/init-orchestrator: For greenfield projects (comprehensive analysis)
/orchestrator: For focused tasks in existing projects (minimal scanning)

Why this change?
Previous orchestrator would scan entire codebase and build comprehensive solutions even for simple requests like "add X to module Y". New approach focuses on executing the specific prompt without scope creep.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/aeitroc/Droid-CLI-Orchestrator/pull/3 **Author:** [@vforvaick](https://github.com/vforvaick) **Created:** 11/22/2025 **Status:** 🔄 Open **Base:** `main` ← **Head:** `claude/brainstorm-droid-cli-014VvoKohRnyHuefJpQoNER4` --- ### 📝 Commits (7) - [`bfc2848`](https://github.com/aeitroc/Droid-CLI-Orchestrator/commit/bfc28485316be98eebf98fc2b82d358a0d1f0cfe) refactor: implement prompt-first orchestrator approach - [`25338bf`](https://github.com/aeitroc/Droid-CLI-Orchestrator/commit/25338bf1e7aee60fea85c2693c1a08af06cf9b26) fix: address CodeRabbit review feedback - [`8d7b056`](https://github.com/aeitroc/Droid-CLI-Orchestrator/commit/8d7b0569ac43d588301ae1bb3b7227b91c41ad8c) docs: add comprehensive documentation to init-orchestrator - [`ad86480`](https://github.com/aeitroc/Droid-CLI-Orchestrator/commit/ad86480dd2e6a1c171db5f81d972c6280afd106c) feat: add interactive installer and health check tools - [`0a027ad`](https://github.com/aeitroc/Droid-CLI-Orchestrator/commit/0a027ad596e1e687a310e4bfda87d003ea8a9a0e) refactor: rename tools to droidos-* prefix for clarity - [`baed9ed`](https://github.com/aeitroc/Droid-CLI-Orchestrator/commit/baed9edb93120eb691b7c79572b0d14f9b8501f0) fix: address CodeRabbit review feedback - [`e663814`](https://github.com/aeitroc/Droid-CLI-Orchestrator/commit/e6638148083c9e8d33f3639ed6289bced9496cdd) docs: add comprehensive changelog and clarify orchestrator modes ### 📊 Changes **6 files changed** (+1774 additions, -618 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+211 -129) ➕ `bin/droidos-doctor` (+393 -0) ➕ `bin/droidos-init` (+491 -0) ➕ `commands/init-orchestrator.md` (+370 -0) 📝 `commands/orchestrator.md` (+28 -205) 📝 `droids/orchestrator.md` (+281 -284) </details> ### 📄 Description BREAKING CHANGE: Orchestrator behavior significantly changed Changes: - Renamed commands/orchestrator.md → commands/init-orchestrator.md (comprehensive greenfield project initialization) - Created new lightweight commands/orchestrator.md (focused task execution with minimal scanning) - Completely refactored droids/orchestrator.md with "Prompt-First" philosophy New Orchestrator Philosophy: ✅ PROMPT IS THE TRUTH - execute exactly what user asks ✅ Minimal scanning - only read files mentioned in prompt + dependencies ✅ No overengineering - don't add unrequested features ✅ Clarify ambiguity - suggest assumptions and ask for confirmation ✅ Smart delegation - use appropriate specialists for the task only Forbidden Behaviors: ❌ Full codebase scanning unless explicitly needed ❌ Building features not mentioned in prompt ❌ Overengineering with unnecessary abstractions ❌ Comprehensive project analysis for simple tasks Use Cases: - /init-orchestrator: For greenfield projects (comprehensive analysis) - /orchestrator: For focused tasks in existing projects (minimal scanning) Why this change? Previous orchestrator would scan entire codebase and build comprehensive solutions even for simple requests like "add X to module Y". New approach focuses on executing the specific prompt without scope creep. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>