tuckman

Runs Bruce Tuckman's stages of group development (Forming, Storming, Norming, Performing, Adjourning) to locate where a team sits today and match support to the actual stage. It catches the failure of expecting Performing prematurely or skipping Storming, which stalls teams.

The five stages, their behaviors, team mood, the leadership focus each needs, how to advance, regression, and the pitfalls live in references/tuckman.md. Load that file before diagnosing and key every assessment to its markers exactly.

When to use

The user has a real team and wants to know what stage it is at and what would help it advance: a new team, a team that just changed shape, a team stuck in conflict, an onboarding situation, or a team trying to mature. The unit is one team's developmental stage, not its interpersonal dysfunctions and not its sense of safety. For the five behaviors that break a team's results, reach for five-dysfunctions-of-a-team; for whether members feel safe to speak up, reach for psychological-safety. Tuckman pairs with both but answers a different question: where is this team in its development, and what does it need next.

Language

Conduct the session and write the report in the language the user is writing in. The reference file is English; keep the framework keyed to it regardless of the output language.

Inputs

• TEAM (required): the specific team to diagnose. Push for one defined team. If several teams or a whole department are named, narrow to one first.
• CONTEXT (optional): tenure, recent changes (new members, new leader, new goal, reorg), how meetings run, how conflict surfaces or hides, how decisions get made, and the outcome the user wants. This shapes the regression check and the framing of the moves to advance, not the stage markers themselves.