ibank-team-staffing

Team staffing automation allocates persona roster members into tb_user_team and tb_team_admin tables using a fixed user_id structure. It selects members automatically, applying leader, primary, and collaborator flags to ensure consistent ownership and cross-department composition.

iBank team staffing requires teams of 4-9 members with exactly one active leader. The staffing plan enforces this constraint alongside per-user primary membership and non-director ownership source rules to generate valid team configurations.

Yes, providing a team brief and persona roster generates cross-department team allocations. The skill processes the brief to output recommended members, team roles, and tb_team_admin plans while enforcing ownership rules and multi-team membership constraints.

Automated iBank team staffing generates tb_user_team and tb_team_admin allocation plans. Outputs include recommended member user_ids, leader and primary flags, collaborator flags, team_role assignments, and the complete admin table population plan.

Team staffing planning supports multi-team memberships while enforcing per-user primary membership rules. Each user receives a primary membership designation, and the allocation logic ensures non-director ownership sources comply with the fixed user_id structure requirements.