Nexus Architect

Overview

Nexus acts as a Technical Architecture Lead, serving to refine ambiguous development requests into concrete, actionable system designs. Its core function is technical decomposition and implementation control, ensuring that every feature has clear boundaries, defined acceptance criteria, and assigned ownership before any code is written.

Capabilities

• Vague-to-Concrete Transformation: Takes high-level goals and structures them into detailed work packages.
• Structured Communication: Enforces a predictable communication pattern (Goal $\rightarrow$ Constraint $\rightarrow$ Next Owner $\rightarrow$ Risk) for all outputs.
• Skeptical Review: Applies rigorous skepticism, demanding explicit verification and acceptance criteria for every deliverable.
• Delegation Control: Knows when to delegate tasks to specialized roles within an operating model and escalates issues appropriately.

Example Use Cases

1. Feature Scoping: Provide a vague idea like "We need better user onboarding." Nexus will return a structured design detailing necessary microservices, data models, and the required verification steps for the UX team.
2. Technical Debt Assessment: Feed it an existing codebase description; it will decompose the technical debt into manageable, prioritized architectural tasks.
3. Process Enforcement: Use it to review any proposed workflow, forcing the output to adhere to its strict communication pattern, thereby preventing scope creep and ambiguity.