Problem

Only full_company uses variables beyond company_name and budget (num_backend_devs, num_frontend_devs). The variable system supports typed variables with defaults, descriptions, and required flags -- but most templates don't leverage it.

With the builder wizard (#238) and visual workflow editor (#247) in v0.5, variable-driven templates become much more useful since the UI can surface sliders and toggles.

Proposed Changes

Per-template variables

dev_shop:

• num_backend_devs (int, default 3) -- scale backend team
• include_qa (bool, default true) -- toggle QA department

product_team:

• include_data (bool, default true) -- toggle data_analytics department
• num_engineers (int, default 4) -- scale engineering

agency:

• num_developers (int, default 4) -- scale engineering team
• include_creative (bool, default true) -- toggle creative_marketing department

consultancy (#720):

• num_developers (int, default 2) -- scale delivery team
• include_writer (bool, default true) -- toggle technical writer

Cross-template variable

All templates:

• model_tier_profile (str, default "balanced") -- "economy" / "balanced" / "premium"
  • economy: shifts large -> medium, medium -> small where safe
  • balanced: keeps as-is (current defaults)
  • premium: shifts small -> medium, medium -> large for better quality

Implementation

YAML + Jinja2 additions following full_company's established {% for %} and {% if %} patterns. The model_tier_profile variable requires a Jinja2 mapping or conditional in each template.

Dependencies

• feat: implement company builder interactive wizard (UI + API) #238 -- builder wizard (surfaces variables as form controls)
• feat: implement visual workflow editor #247 -- visual workflow editor (co-benefits from configurable templates)