trw-sprint-team

Sprint team formation is automated by reading a sprint document to derive a kebab-case team name, analyze PRDs, and generate a structured team ownership map. The automation proposes a scalable team structure with file ownership and generates per-teammate playbooks for spawning Codex subagents.

Sprint team automation requires a sprint document path and PRDs placed in a configured directory. These inputs allow the system to derive sprint goals, assign tracks, and produce the file_ownership.yaml and interface-contract.yaml configurations needed for the workflow.

Generating teammate playbooks works by creating contextual configurations for each subagent based on analyzed PRDs and track assignments. The system executes the /trw-team-playbook command to produce individual playbooks that define implementation, testing, and review task sets for each spawned teammate.

Yes, sprint planning automation supports projects with multiple tracks by reading track assignments from the sprint document and PRDs. It assigns ownership across all tracks and generates distinct task sets and playbooks for each parallel workstream within the same sprint.

File ownership is assigned by proposing a structured ownership map derived from the analyzed sprint document and PRDs. The system generates a file_ownership.yaml file that maps specific files to individual teammates, subject to your approval before finalizing the team structure.

Automating subagent spawns requires properly formatted sprint documents and PRDs in a configured path to derive a kebab-case team name successfully. The system depends on these inputs to generate valid file_ownership.yaml, interface-contract.yaml, and per-teammate playbooks without manual intervention.