os-architect

Orchestrate OS evolution by interviewing intent, auditing existing capabilities, and dispatching work via CLI tooling to coordinate multiple loops. The process classifies requests, identifies capability gaps, and routes concrete changes to plugins, skills, or agents.

An ecosystem capability audit verifies existing plugin and agent functionalities, identifies capability gaps, and assesses risk. It operates as the second phase after intent classification to determine what evolution paths are needed to fill missing functionality.

The best way to dispatch evolution paths is generating Path A/B/C proposals and routing them via CLI tooling. This phase follows intent interviewing and ecosystem auditing, ensuring concrete changes are delegated correctly to plugins, skills, or agents.

Yes, you can fill capability gaps and set up improvement labs without hard dependencies on a single framework. The system coordinates multiple loops and dispatches work independently, applying intent classification and path planning to route changes.

You need intent classification when evolving patterns, setting up improvement labs, or filling capability gaps. It serves as the initial phase to categorize requests into specific evolution types, guiding the subsequent ecosystem audit and work delegation.

CLI tooling delegates work to evolve plugins, skills, or agents without hard dependencies on a single framework. This approach ensures the orchestration of multiple loops remains flexible, allowing path planning and dispatching to drive concrete changes independently.