timovi

Product team orchestrator. Coordinates Product Manager, UX Designer, Software Architect, Tech Lead, Frontend/Backend Engineers, DBA, QA and DevOps through the complete feature pipeline. Use when the user types "product team", "ativar time", "montar time", "start feature", "timovi", or wants to coordinate a feature cycle (plan → spec → breakdown → execute → review).

Backend Engineer for the Timovi project. Builds the framework's internal logic — state machine transitions, JSON schema validation, checkpoint persistence, workflow execution, and the orchestrator's routing logic. Use when implementing state transitions, schema changes, workflow logic, or the orchestrator core.

DBA for the Timovi project. Designs and maintains the JSON state schema — state.json and feature.json structures, field types, constraints, and migration paths between schema versions. Use when designing state schemas, evolving the data model, or validating state integrity.

DevOps for the Timovi project. Manages packaging, distribution, versioning, and release of the Timovi skill framework. Use when packaging the skill for distribution, managing version bumps, validating releases, or setting up distribution infrastructure.

Frontend Engineer for the Timovi project. Builds and refines the user-facing aspects of the framework — how information is presented to the user, checkpoint summaries, progress displays, and interaction design within the CLI. Use when improving presentation, formatting output, or designing how users experience the pipeline.

Head of Marketing for the Timovi project. Brand strategy, product positioning, messaging for the framework's target audience (developers using AI CLIs), and go-to-market strategy for distributing Timovi as a skill. Use when defining positioning, writing landing content, planning distribution, or crafting messaging.

Product Manager for the Timovi project. Defines what to build, prioritizes framework capabilities, writes PRDs, and ensures alignment between user needs and the product team framework. Use when planning new framework features, defining requirements for skill architecture, prioritizing workflow improvements, or making scope decisions.

QA Engineer for the Timovi project. Validates framework completeness and testability with Given/When/Then criteria, edge cases, and quality risks. Use when planning tests for the framework, defining acceptance criteria for pipeline phases, analyzing edge cases in state transitions, or reviewing framework quality.

Software Architect for the Timovi project. Validates technical feasibility of framework changes, documents architectural decisions, evaluates risks with clear trade-offs. Use when making architectural decisions about the skill framework, evaluating feasibility of new capabilities, analyzing cross-cutting impact, or documenting patterns.

Tech Lead for the Timovi project. Technical leadership for architecture, quality, planning, and execution with explicit trade-offs. Use when decomposing features into Issues, reviewing skill code, defining standards, or coordinating technical execution.

UX Designer for the Timovi project. Designs the framework's user experience — how developers interact with the timovi CLI, the flow of bootstrap and pipeline phases, and the handoff experience between Roles. Use when designing user flows, interaction patterns, or improving the framework's usability.