Execution Workflow

---

name: Execution Workflow description: This skill should be used when the user asks to "execute task", "implement feature", "delegate work", "run workflow", "review code", "code quality check", or needs task orchestration and code review guidance. Provides execution, delegation, and code review patterns.

Phase 2 - Deep Analysis:

• Algorithm correctness
• Edge case handling
• Error handling completeness
• Resource management

Phase 3 - Context Evaluation:

• Breaking changes to public APIs
• Side effects on existing functionality
• Dependency compatibility

Phase 4 - Standards Compliance:

• Naming conventions
• Documentation requirements
• Test coverage

Security:

• Input validation
• Authentication/authorization
• Data sanitization
• Secrets handling

Performance:

• Algorithm efficiency
• Resource usage
• Memory leaks
• N+1 queries

Maintainability:

• Clear naming
• Appropriate comments
• Single responsibility
• DRY principle

Testability:

• Test coverage adequate
• Tests meaningful
• Edge cases tested

Important: Should fix before merge

• Logic errors
• Missing error handling
• Performance issues

Suggestion: Nice to have improvements

• Code style
• Refactoring opportunities
• Documentation

Positive: What was done well

• Good patterns
• Clever solutions
• Thorough testing

<anti_patterns> Focusing on code style issues when functionality is broken Address critical and important issues first, style suggestions last Approving changes without thorough review Systematically review all phases: scan, deep analysis, context, standards Providing only critical feedback without acknowledging good work Balance feedback with positive observations of good practices Giving feedback without specific, actionable suggestions Provide file:line references and concrete improvement suggestions Executing independent tasks sequentially Identify and execute independent tasks in parallel for efficiency Attempting to parallelize tasks with data dependencies Analyze dependencies and execute dependent tasks sequentially </anti_patterns>

<best_practices> Analyze task dependencies before execution to determine parallel vs sequential execution model Provide comprehensive context to sub-agents including file paths, tool usage, and reference implementations Systematically review all phases: initial scan, deep analysis, context evaluation, standards compliance Balance critical feedback with positive observations of good practices Provide file:line references and concrete improvement suggestions Check Serena memories for existing patterns before delegating implementation tasks </best_practices>

<error_escalation> Sub-agent returns partial results Note in report, proceed Sub-agent task fails Document issue, use AskUserQuestion for clarification Critical task cannot be completed STOP, present options to user Sub-agent introduces breaking change BLOCK operation, require explicit user acknowledgment </error_escalation>

<related_agents> Primary agent for implementing features with sub-agent delegation Use for post-implementation code review and quality assessment Delegate debugging tasks when critical issues are identified during review </related_agents>

<related_skills> Use for memory checks and symbol operations during delegation Use when code review reveals unclear implementation details Use to verify test coverage and quality during review </related_skills>