TÍTULO

[Objective title describing the problem or improvement]

RESUMO

[Concise description of what must be done and the main objective]

CONTEXTO

[Describe current scenario, identified problem, and why the change is necessary]

Include:
• Problem history
• Impact on users or current flow
• Evidence (when available)
• References (prototypes, screenshots, related tickets)

USER STORY

Como [user type],
Eu quero [desired action],
Para que [benefit or expected result].

REQUISITOS FUNCIONAIS

[Describe everything the system must do]

Organize in clear sections:
• Comportamento padrão
• Regras específicas
• Fluxos condicionais
• Tratamento de versões ou estados anteriores
• Novos campos ou novos componentes de interface
• Outras regras relevantes

REQUISITOS NÃO FUNCIONAIS

[Performance, usability, compatibility, security, design system consistency, etc.]

CRITÉRIOS DE ACEITAÇÃO

[ ] Criterion 1: objective description
[ ] Criterion 2: objective description
[ ] Criterion 3: objective description
[ ] Specific scenarios (Gherkin when necessary)

PONTOS DE ATENÇÃO TÉCNICOS

[Describe critical details that impact implementation]

Include:
• Versioning rules
• Technical dependencies
• Services or endpoints impacted
• Domain or entity changes
• Backward compatibility

DEPENDÊNCIAS

[List external or internal system dependencies]

• Prototyping
• Integrations
• Teams involved
• Other tickets that must be completed first

IMPACTO NA BASE ATUAL

[Describe how the change should affect existing data and behavior needed to avoid regressions]

CHECKLIST TÉCNICO (optional)

[ ] Create database migration
[ ] Update models/entities
[ ] Update services
[ ] Update screen and components
[ ] Create unit tests
[ ] Create integration tests
[ ] Ensure backward compatibility
[ ] Update documentation
