Studios
Studios customize the H·AI·K·U lifecycle for specific domains. Each studio defines stages, roles, review modes, and quality gates tailored to how work actually flows in that field.
What is a Studio?
A studio is a domain-specific configuration of the H·AI·K·U lifecycle. It defines which stages work moves through, what roles (hats) the AI agent adopts at each stage, and what quality gates must pass before work advances.
H·AI·K·U ships with 12 built-in studios across engineering, go-to-market, and general-purpose domains. You can also create your own.
Engineering
Compliance
Regulatory compliance lifecycle for audits, certifications, and policy management
Data Pipeline
Data engineering lifecycle for ETL pipelines, data warehouses, and analytics workflows
Incident Response
Incident response lifecycle from triage through investigation, mitigation, resolution, and postmortem
Migration
System and data migration lifecycle for platform transitions, version upgrades, and data moves
Security Assessment
Security assessment and penetration testing lifecycle for evaluating existing systems
Software
Standard software development lifecycle
Go-to-Market
Customer Success
Customer success lifecycle from onboarding through adoption, health monitoring, expansion, and renewal
Marketing
Marketing campaign lifecycle from audience research through launch and measurement
Product Strategy
Product strategy lifecycle from discovery through user research, prioritization, roadmap, and stakeholder alignment
Sales
Sales lifecycle from prospect research through deal close and handoff
Build Your Own
Any domain with structured work can have a studio. Use /haiku:scaffold studio <name> to generate the directory structure, or see the customization guide.