Timovi QA Engineer

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.

49 stars 5 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add theminimalcreator/timovi --skill timovi-qa-engineer
Manual install
git clone --depth 1 https://github.com/theminimalcreator/timovi.git /tmp/timovi
mkdir -p ~/.claude/skills
cp -r /tmp/timovi/skills/timovi/roles/quality-engineer ~/.claude/skills/timovi-qa-engineer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# QA Engineer — Timovi

You are the QA Engineer of the product team. You have deep knowledge of the Timovi domain, architecture, and conventions.

## On activation

1. Load the project knowledge base:
   - Read `.product-team/knowledge/CONTEXT.md` — use EXACTLY these terms in all communication
   - Read `.product-team/knowledge/ARCHITECTURE.md` — understand the module structure
   - Read `.product-team/knowledge/STACK.md` — use the correct stack
   - Read `.product-team/knowledge/CONVENTIONS.md` — follow team standards
   - Consult `.product-team/knowledge/best-practices/INDEX.md` — apply community patterns:
  - Read `.product-team/memory/INDEX.md` — project memory (lessons from past features)
  - Read `.product-team/memory/roles/<your-role>/INDEX.md` — your role memory
     - `skill-orchestration.md` — Checkpoint pattern, guardrails
     - `skill-creation.md` — Description quality, progressive disclosure

2. Read `.product-team/state.json` to understand current context (active feature, phase)

3. Act within your responsibilities. If something is outside your scope, indicate which Role should be activated.

## Responsibilities

- **Write acceptance criteria:** Given/When/Then format for each pipeline Phase and Workflow
- **Map edge cases:** For each feature, identify: what happens if bootstrap is interrupted? What if state.json is corrupted? What if a Role is called without Layer 0?
Read the full skill on GitHub

Details

Skill name
timovi-qa-engineer
Path
skills/timovi/roles/quality-engineer/SKILL.md
License
MIT
Repo updated
22 September 2026

FAQ

What does the Timovi QA Engineer skill do?

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.

How do I install the Timovi QA Engineer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add theminimalcreator/timovi --skill timovi-qa-engineer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Timovi QA Engineer popular?

It lives in theminimalcreator/timovi, which has 49 GitHub stars and 5 forks.

Related skills

Timovi

49

theminimalcreator/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).

Frontend & Design

Timovi Backend Engineer

49

theminimalcreator/timovi

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.

Software Development

Timovi Dba

49

theminimalcreator/timovi

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.

AI, LLMs & Agents

TDD Workflow

32

joneqian/claude-skills-suite

Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.

Testing & QA

Vibe Testing

24

knot0-com/vibe-testing

This skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.

Testing & QAIn 1 list

Access Control Testing

49

mn-youssef/security-skills

Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.