install-subagents

name	install-subagents
description	Select and verify project-managed sub-agents for PBI work. Developers invoke after receiving PBI assignments.
disable-model-invocation	false

Inputs

• PBI assignment (backlog.json → assigned PBI details)
• Sub-agent definitions in agents/ directory

Outputs

• Confirmation of available sub-agents
• sprint.json → developers[].sub_agents (the sub-agents installed for this developer's pipeline profiles this Sprint)

Required Sub-Agents

Verify these 11 sub-agents exist with valid YAML frontmatter at .claude/agents/<name>.md:

PBI Pipeline (Developer-spawned, per Round):

• pbi-designer
• pbi-implementer
• pbi-ut-author
• codex-design-reviewer
• codex-impl-reviewer
• codex-ut-reviewer

PBI Integrity stage (Developer-spawned, 5-aspect parallel at the Round tail):

• requirement-conformance-reviewer
• functional-quality-reviewer
• security-reviewer
• maintainability-reviewer
• docs-consistency-reviewer

Missing required → BLOCK (escalate to SM, do not proceed to PBI work).

Steps

1. Analyze PBI→determine specialist needs
2. Verify ALL required sub-agents exist:

   for name in pbi-designer pbi-implementer pbi-ut-author \
               codex-design-reviewer codex-impl-reviewer codex-ut-reviewer \
               requirement-conformance-reviewer functional-quality-reviewer \
               security-reviewer maintainability-reviewer docs-consistency-reviewer; do
     [ -f ".claude/agents/$name.md" ] || { echo "MISSING REQUIRED: $name"; exit 1; }
   done
   

3. Verify YAML frontmatter on each (yq eval '.name' or equivalent).
4. During pbi-pipeline execution (incl. the Integrity stage)→invoke via Agent(subagent_type="<name>"). Record the full installed set for this developer's pipeline profiles — the 6 Round agents plus the 5 Integrity-stage reviewers — in sprint.json via the wrapper (this is a deterministic record of what was installed, not an accumulated log of runtime invocations):

   .scrum/scripts/set-sprint-developer.sh "$DEV_ID" sub_agents \
     '["pbi-designer","pbi-implementer","pbi-ut-author","codex-design-reviewer","codex-impl-reviewer","codex-ut-reviewer","requirement-conformance-reviewer","functional-quality-reviewer","security-reviewer","maintainability-reviewer","docs-consistency-reviewer"]'
   

   A kind=docs PBI exercises only a subset of these at runtime (impl + codex-impl-reviewer, and Integrity aspects 1 and 5); the recorded set is still the full installed roster, not the per-PBI subset. The wrapper validates the value parses as a JSON array of strings. Raw jq -i / direct edits on .scrum/sprint.json are blocked by the PreToolUse guard.

Graceful Degradation

• Required sub-agent files missing → BLOCK (cannot proceed; SM must install them).

Ref: FR-019

Exit Criteria

• All 11 required sub-agents verified present (6 PBI Pipeline + 5 Integrity-stage, per "Required Sub-Agents" list above) with valid YAML frontmatter
• BLOCKED if any required sub-agent is missing