feat: refactor 30+ skills to Anthropic progressive disclosure pattern

- All SKILL.md files now <500 lines (avg reduction 69%)
- Detailed content extracted to references/ subdirectories
- Frontmatter standardised: only name + description (Anthropic standard)
- New skills: brand-guidelines, spec-coauthor, report-templates, skill-creator
- Design skills: anti-slop guidelines, premium-proposals reference
- Removed non-standard frontmatter fields (triggers, version, author, category)

Plugins affected: infraestrutura, marketing, dev-tools, crm-ops, gestao,
core-tools, negocio, perfex-dev, wordpress, design-media

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-03-12 15:05:03 +00:00
parent 9404af7ac9
commit 6b3a6f2698
397 changed files with 67154 additions and 17257 deletions

View File

@@ -0,0 +1,83 @@
# Product - Metricas de Produto
## AARRR Pirate Metrics
| Fase | Metrica | Target |
|------|---------|--------|
| **Acquisition** | Signups/semana | +20%/mes |
| **Activation** | Setup completo | > 40% |
| **Retention** | D7 retention | > 30% |
| **Revenue** | Conversion free->paid | > 3% |
| **Referral** | NPS | > 40 |
## Product Health
### Engagement
- DAU/MAU ratio (stickiness): > 20%
- Session duration: Sector-dependent
- Features usado/session: > 3
### Adoption
- Time to first value: < 10 min
- Feature adoption (30 dias): > 30%
- Power users (5+ dias/semana): > 10%
### Quality
- Error rate: < 1%
- Support tickets/100 users: < 5
- CSAT: > 4/5
## Outcomes vs Outputs
```
ERRADO (Output-driven):
"Lancar 10 features este trimestre"
CERTO (Outcome-driven):
"Aumentar retention D30 de 20% para 35% (via engagement features)"
Medir:
- North Star Metric (ex: DAU/MAU)
- Leading indicators (ex: time-to-value)
- Lagging indicators (ex: churn)
```
## Discovery - Pain Points
```
Perguntas a fazer:
1. O que frustra o utilizador actualmente?
2. Que workarounds usa hoje?
3. Quanto tempo/dinheiro perde com o problema?
4. Qual a frequencia do problema?
5. O que tentou fazer para resolver?
Evidencia:
- [ ] 5+ entrevistas com users
- [ ] Analytics de uso (onde abandonam?)
- [ ] Tickets de suporte relacionados
- [ ] Pesquisa concorrencia (como resolvem?)
```
## Validation Framework
### Desirability (Users querem?)
- Problem interviews (10+)
- Solution interviews (5+)
- Survey (50+ respostas)
- Prototype test (usability)
- Evidence: X% users pagaria, Y% usaria diario
### Viability (Negocio faz sentido?)
- Market size (TAM/SAM/SOM)
- Revenue model claro
- Unit economics positivos
- Payback period aceitavel
- Target: ROI > 3x em 12 meses
### Feasibility (Conseguimos construir?)
- Technical spike completo
- Dependencies mapeadas
- Resources disponiveis
- Timeline realista
- Risk assessment: Alto/Medio/Baixo

View File

@@ -0,0 +1,78 @@
# Product - Frameworks de Priorizacao
## A. RICE Score (Recomendado)
```
Reach x Impact x Confidence
Score = ----------------------------
Effort
Reach: Quantos users impactados por periodo
- Ex: 1000 users/quarter, 500 users/month
Impact: Quanto impacto por user
- 3 = Massive impact
- 2 = High impact
- 1 = Medium impact
- 0.5 = Low impact
- 0.25 = Minimal impact
Confidence: Certeza das estimativas
- 100% = Dados solidos
- 80% = Boas evidencias
- 50% = Suposicoes educadas
Effort: Person-months para entregar
- Ex: 2 person-months, 0.5 person-month
```
Exemplo Pratico:
| Feature | Reach | Impact | Confidence | Effort | RICE | Prioridade |
|---------|-------|--------|------------|--------|------|------------|
| Export PDF | 800/q | 2 | 80% | 1 | 1280 | Alta |
| Dark mode | 400/q | 0.5 | 100% | 0.5 | 400 | Media |
| API v2 | 200/q | 3 | 50% | 3 | 100 | Baixa |
| Search filters | 1000/q | 1 | 80% | 0.5 | 1600 | Alta |
## B. MoSCoW Method
```
MUST have: Critico para launch (MVP)
- Sem isso, produto nao funciona
- Legal/compliance obrigatorio
- Blocker absoluto
SHOULD have: Importante mas nao critico
- Melhora significativamente a experiencia
- Workaround existe
- Pode ser adiado 1 sprint
COULD have: Nice to have
- Pequena melhoria
- Se sobrar tempo
- Low effort/low impact
WON'T have (agora): Fora de scope
- Para proxima versao
- Nao alinhado com objectivo actual
```
## C. Value vs Effort Matrix
```
| HIGH VALUE
|
II | I
Quick | Big
Wins | Bets
(DO) | (PLAN)
---------+---------
III | IV
Fill | Money
Ins | Pit
(LATER) | (AVOID)
|
| LOW VALUE
LOW EFFORT -> HIGH EFFORT
```

View File

@@ -0,0 +1,162 @@
# Product - Templates de Roadmap e Sprint
## Template Roadmap Quadrimestral
```markdown
# Product Roadmap Q1-Q3 2026
## Q1 (Jan-Abr): Foundation
**Theme:** Stabilize core + basic integrations
**Goal:** 100 active users, NPS > 40
### Epic 1: Core Functionality Polish
- [ ] Performance optimization (< 2s load)
- [ ] Mobile responsive
- [ ] Error handling robusto
### Epic 2: Basic Integrations
- [ ] Slack notifications
- [ ] Google Calendar sync
- [ ] Email templates
**Milestone:** MVP Launch (31 Mar)
**Success Metrics:**
- 50 signups/week
- 40% activation rate
- < 10% churn
---
## Q2 (Mai-Ago): Growth
**Theme:** Expand features + virality
**Goal:** 500 active users, NPS > 50
### Epic 3: Collaboration Features
- [ ] Team workspaces
- [ ] Comments & mentions
- [ ] Activity feed
### Epic 4: Growth Loops
- [ ] Invite system (referral)
- [ ] Public templates gallery
- [ ] Embeddable widgets
**Milestone:** Product-Market Fit (31 Ago)
**Success Metrics:**
- 1000 signups total
- 50% M1 retention
- NRR > 100%
---
## Q3 (Set-Dez): Scale
**Theme:** Enterprise readiness
**Goal:** 2000 active users, ARR > 100kEUR
### Epic 5: Enterprise Features
- [ ] SSO/SAML
- [ ] Advanced permissions
- [ ] Audit logs
- [ ] Custom branding
### Epic 6: API & Integrations
- [ ] Public API v1
- [ ] Zapier integration
- [ ] Webhooks
**Milestone:** Enterprise Ready (31 Dez)
```
## Template User Story
```markdown
## US-123: Export dashboard to PDF
### User Story
Como [Product Manager]
Quero [exportar dashboard para PDF com branding personalizado]
Para que [possa partilhar relatorios profissionais com stakeholders externos]
### Context
- Users pedem isto em 60% dos support tickets
- Concorrentes ja tem (Competitor A, B)
- Workaround actual: screenshots (nao profissional)
### Acceptance Criteria
Given [estou no dashboard com dados carregados]
When [clico em "Export PDF"]
Then [sistema gera PDF em < 5s com:
- Logo da empresa
- Data do relatorio
- Todos os graficos (vectorial)
- Tabela de dados resumida
- Footer com marca d'agua]
And [recebo notificacao quando PDF pronto]
And [posso fazer download ou enviar por email]
### Edge Cases
- [ ] Dashboard sem dados -> mostrar "No data" no PDF
- [ ] Dashboard com 100+ items -> paginar automaticamente
- [ ] Logo nao carregado -> usar placeholder
### Definition of Done
- [ ] Codigo completo e reviewed
- [ ] Testes unitarios (> 80% coverage)
- [ ] Testes E2E (happy path + edge cases)
- [ ] Documentacao API actualizada
- [ ] Changelog entry
- [ ] Deployed to staging
- [ ] QA sign-off
- [ ] Product Manager review
### Effort Estimate
Story Points: 5 (Fibonacci: 1, 2, 3, 5, 8, 13)
Dev: 2 days | QA: 0.5 days | Total: 2.5 days
```
## Template Sprint (2 semanas)
```markdown
# Sprint 23 (3-14 Fev 2026)
## Sprint Goal
"Users podem exportar dashboards profissionais e partilhar com stakeholders"
## Team Capacity
- 3 developers x 8 days = 24 person-days
- Velocity media: 25 story points/sprint
- Buffer para bugs/support: 20% -> 20 SP disponiveis
## Committed Stories
### Must Have (MVP sprint)
- [ ] US-123: Export PDF (5 SP) - @dev1
- [ ] US-124: Email sharing (3 SP) - @dev2
- [ ] US-125: Custom branding settings (3 SP) - @dev3
### Should Have (se tempo)
- [ ] US-126: Schedule exports (5 SP)
- [ ] US-127: Export templates (3 SP)
### Bugs Criticos
- [ ] BUG-45: Login timeout (2 SP) - @dev1
**Total Committed:** 13 SP
**Stretch Goals:** 8 SP
## Definition of Done (Sprint)
- [ ] Todas as US committed DONE
- [ ] Zero bugs criticos open
- [ ] Test coverage > 80%
- [ ] Docs actualizadas
- [ ] Demo preparada para stakeholders
- [ ] Retrospective completa
## Ceremonies
- Planning: Seg 3 Fev, 10h-12h
- Daily: 9h30 (15 min)
- Refinement: Qua 7 Fev, 14h-16h
- Review: Sex 14 Fev, 14h-15h
- Retrospective: Sex 14 Fev, 15h-16h
```