Analyst
The Analyst agent is the first to engage when a new task starts. It examines your codebase to understand the blast radius of proposed changes, mapping dependencies, identifying risk areas, and producing a structured impact report that guides all subsequent phases.
How it works
The Analyst reads your project structure, configuration, and existing architecture documentation. It traces the dependency graph from the components you want to modify, identifies downstream consumers, flags files with high change risk, and checks for conflicts with any in-progress WorkGroups. The output is a structured report with file-level impact assessment, risk scores, and recommended approach. If connected to Knowz, it also queries past decisions for relevant context.
Analyst agent producing an impact analysis with file dependency graph
Screenshot coming soon
Under the hood
The Analyst uses a combination of static analysis (file imports, exports, configuration references) and semantic understanding (what a module does, not just what it imports). It weights risk based on factors like test coverage of affected areas, recency of changes, and complexity metrics. High-risk areas get flagged for extra attention in the specification phase.
Risk heat map of codebase showing high-impact areas
Screenshot coming soon
Related Features
Impact Analysis
An analyst agent examines your codebase and identifies which files and components will be affected before code is written.
Architect
Specification drafting: designs solutions, considers alternatives, documents verification criteria.
Context Scout
Researches project history: scans existing specs, past work, and related context.