team-code-refactor

Architect-directed code refactoring within an existing team is handled by loading the coding skill into a single refactorer, assigning an action plan, and verifying changes with pyright. This keeps team governance intact and coordinates refactoring via message exchanges.

The best way to coordinate a team code refactor without creating new teams is to spawn a single refactorer into the existing review team, assign tasks using the team name, and apply an approved action plan to ensure alignment and governance.

You verify code quality during team refactoring by running pyright validation after each change group. This ensures type safety and code quality are maintained before performing final cleanup operations.

Yes, pyright validation is used to check changes during an in-place team refactor. The architect directs the single refactorer to implement changes, and pyright verification is performed after each change group to ensure code quality.

Yes, you need an existing review team from a previous code review phase to start an architect-led refactor. The skill shuts down non-critical reviewers and streamlines the existing team for Phase 5 refactoring using an approved action plan.

You should shut down non-critical reviewers before a team code refactor to streamline the existing team for Phase 5 refactoring. This allows the architect to focus coordination on a single refactorer executing the approved action plan with pyright validation.