Serena Workflow Profiles

This file defines Serena operating modes and when to use the Aion explainer skill.

quick-scan

• goal: rapidly identify candidate files, symbols, and likely impact areas
• allowed tools: search, read, symbol lookup
• output payload: candidate_targets, quick_risks, open_questions
• forbidden actions: editing files, claiming contract guarantees

deep-trace

• goal: map cross-package impact and dependency chains before implementation
• allowed tools: search, read, symbol usage mapping, dependency analysis
• output payload: impact_map, risk_levels, required_mcp_calls, assumptions
• forbidden actions: changing contract semantics without explicit lock updates

verify

• goal: validate that proposed or completed changes satisfy locked contracts and gates
• allowed tools: search, read, test execution, static checks
• output payload: pass_fail_matrix, failed_checks, remediation_actions
• forbidden actions: ignoring failed gate checks

Explain Aion Invocation Rules

• invoke aion-framework-explainer when user intent is communication-oriented
• audience input must be one of: engineering, product, architecture
• summaries must use AGENTS glossary and avoid unbacked claims
• if explanation depends on a gate, include the gate reference