Problem

Templates reference workflow types as bare strings ("kanban", "agile_kanban") with no configuration. Once #239 (Kanban board) and #240 (Agile sprints) ship, templates can specify real workflow configurations -- sprint lengths, WIP limits, ceremony schedules, backlog policies.

Proposed Changes

After #239 and #240 land, update templates to use proper workflow configs:

• product_team: 2-week sprints, sprint planning + retrospective ceremonies, WIP limit 3
• dev_shop: kanban with WIP limit 2 per agent, explicit done criteria
• agency: kanban with client-visible board, delivery milestones
• full_company: 2-week sprints with all ceremonies, WIP limit per department
• startup: 1-week sprints (move fast), minimal ceremonies
• solo_founder / research_lab: simple kanban, no ceremonies

Add template variables where useful (e.g. sprint_length, wip_limit).

Scope

YAML changes + potentially new template variables. Depends entirely on what workflow schema #239/#240 expose.

Dependencies

• feat: implement Kanban board workflow type #239 -- Kanban board workflow type
• feat: implement Agile sprints workflow type #240 -- Agile sprints workflow type