# Ops Templates Sample Book

## Purpose
**SAMPLE DATA** - Example filled ops/support templates for demonstration and testing purposes. These are realistic examples to work with while actual definitions are pending from ops/support team.

Use these to:
- Understand the template structure
- Test tooling and workflows
- Demo the feature-flow pipeline

Real templates will follow the same structure but with validated content.

## Structure

```
ops-templates-sample/
├── pet-owner/         # 5 flows for pet owners
│   ├── 01-registro.md
│   ├── 02-reservar-turno.md
│   ├── 03-gestion-mascotas.md
│   ├── 04-pago-turno.md
│   └── 05-historial-medico.md
├── veterinarian/      # 5 flows for vets
│   ├── 01-aceptar-solicitud.md
│   ├── 02-gestion-agenda.md
│   ├── 03-realizar-visita.md
│   ├── 04-zonas-cobertura.md
│   └── 05-historial-pacientes.md
└── backoffice/        # 5 flows for admins
    ├── 01-gestion-solicitudes.md
    ├── 02-gestion-usuarios.md
    ├── 03-gestion-servicios.md
    ├── 04-reembolsos.md
    └── 05-reportes.md
```

## Template Format

Each file follows the standard ops template:

```markdown
# [Nombre del Flujo]

## Tipo de usuario
## Donde empieza
## Que quiere hacer el usuario
## Pasos
## Que deberia pasar
## Problemas comunes
## Casos especiales
## Flujos relacionados
## Notas tecnicas
```

## Corresponding Gherkin

Each template has corresponding `.feature` files in:
- `album/book/gherkin-sample/es/` - Spanish keywords (Dado/Cuando/Entonces)
- `album/book/gherkin-sample/en/` - English keywords (Given/When/Then)

## Usage

1. **Support/Ops**: Use templates to document new flows
2. **Dev**: Convert templates to Gherkin specs
3. **QA**: Use Gherkin to derive test cases
4. **Product**: Review templates for completeness

## Source Template

The base template is at: `album/template/ops-flow/plantilla-flujo.md`

## Coverage

| Area | Flows | Status |
|------|-------|--------|
| Pet Owner | 5 | Complete |
| Veterinarian | 5 | Complete |
| Backoffice | 5 | Complete |
| **Total** | **15** | |
