sinapse-ai 1.0.0

package/squad-product/tasks/generate-product-health-report.md

@@ -0,0 +1,72 @@
+---
+task: generate-product-health-report
+responsavel: "@ps-orchestrator"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Generate Product Health Report
+
+## Metadata
+- **Agent:** ps-orchestrator (Vector)
+- **Complexity:** Medium
+- **Estimated Time:** 2-3 hours
+- **Depends On:** Analytics data available, sprint data current
+- **Produces:** Product health dashboard, executive summary, action items
+
+## Purpose
+Gerar relatório consolidado de saúde do produto combinando métricas de produto (Delta), status de delivery (Tempo), saúde do cliente (Proxy) e progresso estratégico (Charter).
+
+## Steps
+
+### Step 1: Collect Metrics from Each Domain
+**Product (Delta):** Activation Rate, DAU/MAU, Feature Adoption, Retention D7/D30, NPS
+**Delivery (Tempo):** Sprint Velocity, Variance, Goal Completion, Bug Escape Rate, Tech Debt Ratio
+**Client (Proxy):** Satisfaction, Communication Cadence, Scope Changes, Relationship Temperature
+**Strategy (Charter):** OKR Progress, Roadmap Delivery, Discovery Pipeline, PMF Indicators
+
+### Step 2: Calculate Composite Health Score (0-100)
+```
+Product Health = (Product Metrics × 0.30) + (Delivery × 0.25) + (Client Health × 0.25) + (Strategic Progress × 0.20)
+
+Health Bands:
+  80-100: 🟢 Green — Maintain course
+  60-79:  🟡 Yellow — Investigate, improvement plan
+  40-59:  🟠 Orange — Escalate, dedicated improvement sprint
+  0-39:   🔴 Red — Emergency intervention
+```
+
+### Step 3: Trend Analysis
+Compare with prior periods: ↑ Improving (>5%), → Stable (±5%), ↓ Declining (>5%), ⚡ Significant (>15%)
+
+### Step 4: Generate Insights & Recommendations
+For each dimension below target: root cause hypothesis, recommended action, expected impact, timeline
+
+### Step 5: Compile Report
+Executive Summary → Dimension Breakdown → Trend Analysis → Key Risks → Recommended Actions → Appendix
+
+## Output Artifacts
+- `product-health-report-[date].md` | `health-executive-summary.md` | `health-action-items.md`
+
+## Quality Criteria
+- All 4 dimensions covered with real data
+- Trend comparison with at least 1 prior period
+- Every metric below target has an action item

package/squad-product/tasks/generate-product-metrics-report.md

@@ -0,0 +1,136 @@
+---
+task: generate-product-metrics-report
+responsavel: "@ps-product-analyst"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Generate Product Metrics Report
+
+## Metadata
+- **Agent:** ps-product-analyst (Delta)
+- **Complexity:** Medium
+- **Estimated Time:** 2-3 hours
+- **Produces:** Weekly/monthly product metrics report, narrative analysis, action recommendations
+
+## Purpose
+Gerar relatorio periodico de metricas de produto que transforma numeros em narrativa acionavel. O relatorio nao e apenas dados — e uma historia sobre o que esta acontecendo com o produto e o que fazer a respeito.
+
+## Steps
+
+### Step 1: Report Configuration
+| Attribute | Value |
+|-----------|-------|
+| Report Type | Weekly / Monthly / Quarterly |
+| Period | [date range] |
+| Audience | [product team / stakeholders / client] |
+| Distribution | [email / Slack / dashboard link] |
+| Previous Period | [for comparison] |
+
+### Step 2: Executive Summary (1 paragraph)
+**Template:**
+```
+This [period], [product name] [improved/declined/maintained] overall health
+from [previous score] to [current score]. [Top positive highlight in one sentence].
+[Top concern in one sentence]. [Key action needed in one sentence].
+```
+
+**Example:**
+"This week, ProductX maintained healthy performance at 74/100. Activation rate improved to 42% following onboarding changes (+5pp WoW). However, D30 retention continues to decline for the third consecutive week, now at 28% (-2pp). Recommend prioritizing retention investigation this sprint."
+
+### Step 3: Key Metrics Dashboard
+**Metric Summary Table:**
+| Metric | Current | Previous | Change | Target | Status |
+|--------|---------|----------|--------|--------|--------|
+| Health Score | [N] | [N] | [+/-N] | [N] | GREEN/YELLOW/RED |
+| North Star | [N] | [N] | [+/-N%] | [N] | GREEN/YELLOW/RED |
+| Activation Rate | [%] | [%] | [+/-pp] | [%] | GREEN/YELLOW/RED |
+| D30 Retention | [%] | [%] | [+/-pp] | [%] | GREEN/YELLOW/RED |
+| DAU/MAU | [ratio] | [ratio] | [+/-] | [ratio] | GREEN/YELLOW/RED |
+| NPS | [score] | [score] | [+/-] | [score] | GREEN/YELLOW/RED |
+| Error Rate | [%] | [%] | [+/-pp] | [<%] | GREEN/YELLOW/RED |
+| Sprint Velocity | [pts] | [pts] | [+/-] | [pts] | GREEN/YELLOW/RED |
+
+**Status Legend:**
+- GREEN: At or above target
+- YELLOW: Within 10% of target
+- RED: More than 10% below target
+
+### Step 4: Narrative Analysis (per metric group)
+**For Each Section, Write:**
+```
+WHAT HAPPENED: [factual description of metric movement]
+WHY: [root cause analysis or hypothesis]
+SO WHAT: [business impact of this movement]
+NOW WHAT: [recommended action]
+```
+
+**Sections:**
+1. **Acquisition & Growth** — new users, channels, CAC movement
+2. **Activation & Onboarding** — activation rate, TTV, onboarding funnel
+3. **Engagement & Usage** — DAU/MAU, feature usage, session metrics
+4. **Retention & Churn** — cohort retention, churn rate, at-risk users
+5. **Revenue & Monetization** — MRR movement, ARPU, conversion rate
+6. **Quality & Performance** — error rate, latency, bug count, incidents
+
+### Step 5: Highlights & Lowlights
+**Top 3 Wins This Period:**
+| Win | Impact | What Drove It |
+|-----|--------|--------------|
+| 1. [positive outcome] | [metric improvement] | [cause] |
+| 2. [positive outcome] | [metric improvement] | [cause] |
+| 3. [positive outcome] | [metric improvement] | [cause] |
+
+**Top 3 Concerns This Period:**
+| Concern | Impact | Recommended Action |
+|---------|--------|-------------------|
+| 1. [negative trend] | [metric decline] | [what to do] |
+| 2. [negative trend] | [metric decline] | [what to do] |
+| 3. [negative trend] | [metric decline] | [what to do] |
+
+### Step 6: Experiment & Initiative Updates
+**Active Experiments:**
+| Experiment | Status | Preliminary Result | Expected Completion |
+|-----------|--------|-------------------|-------------------|
+| [name] | Running / Complete / Paused | [early signal if available] | [date] |
+
+**Recently Shipped:**
+| Feature/Change | Ship Date | Early Metrics | Notes |
+|---------------|-----------|--------------|-------|
+| [feature] | [date] | [initial data] | [observations] |
+
+### Step 7: Action Items
+**This Period Action Items:**
+| Action | Owner | Priority | Due Date | Metric Impact |
+|--------|-------|----------|----------|--------------|
+| [action 1] | [agent/person] | P1/P2 | [date] | [which metric] |
+| [action 2] | [agent/person] | P1/P2 | [date] | [which metric] |
+
+**Carried Forward (unresolved from last period):**
+| Action | Owner | Status | Blocker |
+|--------|-------|--------|---------|
+| [action] | [owner] | [in progress/blocked] | [what blocks it] |
+
+## Output Artifacts
+- `product-metrics-report-[period].md` | `metrics-narrative-[period].md` | `action-items-[period].md`
+
+## Quality Criteria
+- Every metric has comparison to previous period + target | Narrative explains WHY, not just WHAT | Recommendations are specific and assigned | Wins and concerns balanced (honest) | Action items have owners and deadlines | Report delivered within 24h of period end

package/squad-product/tasks/identify-aha-moment.md

@@ -0,0 +1,154 @@
+---
+task: identify-aha-moment
+responsavel: "@ps-discovery-lead"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Identify Aha Moment
+
+## Metadata
+- **Agent:** ps-discovery-lead (Quorum)
+- **Complexity:** High
+- **Estimated Time:** 4-6 hours (analysis) + ongoing monitoring
+- **Produces:** Aha moment definition, activation metrics, onboarding optimization recommendations
+
+## Purpose
+Identificar o momento exato em que usuarios percebem valor do produto (Aha Moment). Essencial para otimizar onboarding, reducir churn e acelerar ativacao. Referencia: Chamath Palihapitiya (Facebook Growth), Hiten Shah, Wes Bush (Product-Led Growth).
+
+## Steps
+
+### Step 1: Hypothesize Aha Moment Candidates
+**Common patterns by product type:**
+| Product Type | Typical Aha Moment |
+|-------------|-------------------|
+| SaaS Tool | First successful task completion |
+| Marketplace | First match/transaction |
+| Content platform | First content that resonates |
+| Communication tool | First reply/response received |
+| Analytics tool | First insight that changes a decision |
+| Collaboration tool | First team interaction |
+
+**Generate Candidates:**
+- From user interviews: "When did you realize this product was valuable?"
+- From analytics: What actions correlate with retention?
+- From support: What do successful users do that churned users did not?
+- From power users: What was the turning point?
+
+**Candidate List:**
+| # | Candidate Aha Moment | Data Source | Hypothesis Strength |
+|---|---------------------|-----------|-------------------|
+| 1 | [action/event] | [interviews/analytics/both] | High/Med/Low |
+| 2 | [action/event] | [interviews/analytics/both] | High/Med/Low |
+| 3 | [action/event] | [interviews/analytics/both] | High/Med/Low |
+
+### Step 2: Quantitative Validation
+**For each candidate, analyze correlation with retention:**
+
+**Cohort Analysis:**
+```
+Users who did [candidate action] within [timeframe]:
+  - Day 7 retention: [%]
+  - Day 30 retention: [%]
+  - Day 90 retention: [%]
+
+Users who did NOT do [candidate action] within [timeframe]:
+  - Day 7 retention: [%]
+  - Day 30 retention: [%]
+  - Day 90 retention: [%]
+
+Delta (lift): [percentage point difference]
+```
+
+**Threshold Analysis:**
+- Test different thresholds: Did it once? 3 times? Within 1 day? 7 days?
+- Find the threshold that maximizes retention delta
+
+**Statistical Significance:**
+- Sample size sufficient? (min 100 per cohort)
+- Chi-square or Fisher test for significance
+- Control for confounders (user segment, acquisition channel)
+
+### Step 3: Qualitative Validation
+**Interview Activated Users:**
+- "Tell me about the moment you realized this product was worth using"
+- "What changed between your first visit and when you decided to stay?"
+- "If you had to convince a friend to try this, what would you tell them?"
+
+**Interview Churned Users:**
+- "What were you hoping to achieve?"
+- "At what point did you decide it was not working for you?"
+- "What would have changed your mind?"
+
+**Pattern Match:** Does the qualitative "aha" match the quantitative retention driver?
+
+### Step 4: Define the Aha Moment
+**Aha Moment Statement:**
+```
+When a [user type] performs [specific action]
+[N times] within [timeframe] of signing up,
+they are [X%] more likely to become a retained user
+(vs [Y%] for users who do not reach this milestone).
+
+Retention lift: [X-Y] percentage points
+Time to Aha (median): [N days/hours]
+Current reach rate: [% of new users who reach Aha]
+```
+
+### Step 5: Define Activation Metric
+**Based on Aha Moment, create trackable metric:**
+
+```
+ACTIVATION METRIC
+────────────────────────────────
+Name: [descriptive name]
+Definition: [exact event/action that counts]
+Timeframe: [within N days of signup]
+Threshold: [min occurrences or value]
+Current rate: [% of new users activated]
+Target rate: [% goal]
+Measurement: [analytics event/query]
+```
+
+**Activation Funnel:**
+```
+Signup → [Step 1] → [Step 2] → [AHA MOMENT] → Retained User
+[100%]   [X%]       [Y%]       [Z%]           [W%]
+```
+
+### Step 6: Onboarding Optimization Recommendations
+**Reduce Time-to-Aha:**
+| Barrier | Current Impact | Recommendation | Expected Lift |
+|---------|---------------|----------------|---------------|
+| [what blocks users from Aha] | [% drop-off here] | [specific change] | [estimated improvement] |
+
+**Key Strategies:**
+- Remove steps between signup and Aha moment
+- Add guided tours that lead TO the Aha action
+- Use empty states that prompt the Aha action
+- Send triggered emails/notifications when users stall before Aha
+- Personalize onboarding path by user segment
+
+## Output Artifacts
+- `aha-moment-analysis.md` | `activation-metric-definition.md` | `activation-funnel.md` | `onboarding-optimization-recommendations.md`
+
+## Quality Criteria
+- Min 3 candidates tested quantitatively | Retention correlation validated with sufficient sample | Qualitative and quantitative evidence aligned | Activation metric clearly defined and measurable | Onboarding recommendations specific and prioritized

package/squad-product/tasks/initiate-product-handoff.md

@@ -0,0 +1,73 @@
+---
+task: initiate-product-handoff
+responsavel: "@ps-orchestrator"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Initiate Product Handoff
+
+## Metadata
+- **Agent:** ps-orchestrator (Vector)
+- **Complexity:** High
+- **Estimated Time:** 2-4 weeks
+- **Produces:** Handoff package, knowledge transfer plan, transition timeline
+
+## Purpose
+Orquestrar handoff completo de produto da agência para equipe do cliente com todo conhecimento, contexto e assets transferidos.
+
+## Steps
+
+### Step 1: Handoff Readiness Scorecard (6 dimensions, 1-5 each, threshold ≥3.5)
+Documentation completeness | Code quality & test coverage | Analytics instrumentation | Client team capability | Open issues resolved | Knowledge transfer plan
+
+### Step 2: Handoff Package Assembly
+| Document | Owner |
+|----------|-------|
+| Product Backlog | Vector |
+| Decision Log | Mosaic |
+| Analytics Setup Guide | Delta |
+| Roadmap (Now/Next/Later) | Charter |
+| Tech Debt Register | Tempo |
+| Operations Runbook | Mosaic |
+| Research Repository | Quorum |
+| Feature Flag Inventory | Tempo |
+| Stakeholder Map | Proxy |
+| OKR History | Charter |
+
+### Step 3: Knowledge Transfer Sessions (7 sessions)
+Vision & OKRs (Charter, 2h) → Discovery findings (Quorum, 2h) → Analytics & metrics (Delta, 2h) → Delivery process (Tempo, 1.5h) → Client communication (Proxy, 1.5h) → Operations & tools (Mosaic, 1.5h) → Q&A + shadow planning (Vector, 1h)
+
+### Step 4: Shadow Period (2-4 weeks)
+Week 1: Agency leads, client shadows | Week 2: Co-lead | Week 3: Client leads, agency shadows | Week 4: Client independent, agency on-call
+
+### Step 5: Handoff Gate
+- [ ] All documentation delivered and reviewed
+- [ ] KT sessions completed (100%)
+- [ ] Client can run ceremonies independently
+- [ ] No critical open issues
+- [ ] Client sign-off obtained
+
+## Output Artifacts
+- `handoff-package/` | `knowledge-transfer-plan.md` | `handoff-gate-report.md` | `client-signoff.md`
+
+## Quality Criteria
+- All 10 documents complete | KT recorded | Client operates independently | Formal sign-off obtained

package/squad-product/tasks/intake-and-reframe-client-request.md

@@ -0,0 +1,161 @@
+---
+task: intake-and-reframe-client-request
+responsavel: "@ps-client-product-manager"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Intake and Reframe Client Request
+
+## Metadata
+- **Agent:** ps-client-product-manager (Proxy)
+- **Complexity:** Medium
+- **Estimated Time:** 1-2 hours
+- **Produces:** Reframed request, problem statement, impact assessment, recommendation
+
+## Purpose
+Receber pedidos de clientes e reframeá-los de features para problemas. Baseado em Rich Mironov: "Client says feature, PM finds problem." Transformar pedidos reativos em oportunidades de produto.
+
+## Steps
+
+### Step 1: Capture Raw Request
+**Request Intake Form:**
+```
+REQUEST ID: [auto-generated]
+Date: [date received]
+Client: [client name]
+Requester: [person name + role]
+Channel: [email/meeting/Slack/ticket]
+Urgency Stated: [ASAP/This Sprint/This Quarter/Flexible]
+
+RAW REQUEST (exact words):
+"[verbatim what the client asked for]"
+```
+
+### Step 2: Reframe (Rich Mironov Method)
+**5 Reframing Questions:**
+1. **What problem are you trying to solve?** (not "what feature do you want?")
+2. **Who specifically is affected?** (which users, how many)
+3. **How are they handling it today?** (current workaround)
+4. **What happens if we do nothing?** (real impact)
+5. **How would you know the problem is solved?** (success criteria from their perspective)
+
+**Reframe Template:**
+```
+CLIENT SAID: "[verbatim request — usually a feature]"
+
+REFRAMED PROBLEM: "[the underlying problem, not the solution]"
+
+CONTEXT:
+  Who is affected: [specific users/roles]
+  Current workaround: [how they manage today]
+  Frequency: [how often this problem occurs]
+  Impact if unsolved: [business/user impact]
+  Success criteria: [how client would measure success]
+```
+
+### Step 3: Classify Request Type
+**Request Classification Matrix:**
+| Type | Definition | Typical Route | SLA |
+|------|-----------|--------------|------|
+| Bug Report | Something is broken | Engineering → Triage → Fix | 24-48h response |
+| Feature Request | New capability desired | Product → Evaluate → Backlog | 1 week evaluation |
+| Enhancement | Improvement to existing | Product → Prioritize | Sprint-level |
+| Strategic Initiative | Large new direction | Product → Strategy → Roadmap | Quarter-level |
+| Scope Change | Change to agreed scope | Delivery → Scope process | Per contract |
+
+### Step 4: Impact & Effort Assessment
+**Quick T-Shirt Sizing:**
+| Dimension | XS | S | M | L | XL |
+|-----------|-----|-----|-----|-----|------|
+| User Impact | <10 users | 10-50 | 50-500 | 500-5K | >5K |
+| Revenue Risk | None | <$1K | $1K-10K | $10K-100K | >$100K |
+| Effort | <1 day | 1-3 days | 1-2 weeks | 2-6 weeks | >6 weeks |
+| Urgency | Flexible | This quarter | Next sprint | This sprint | Hotfix |
+
+**Combined Assessment:**
+```
+Impact: [HIGH/MEDIUM/LOW]
+Effort: [XS/S/M/L/XL]
+Urgency: [CRITICAL/HIGH/MEDIUM/LOW]
+Strategic Alignment: [HIGH/MEDIUM/LOW/NONE]
+```
+
+### Step 5: Generate Recommendation
+**Decision Framework:**
+| Impact | Effort | Urgency | Recommendation |
+|--------|--------|---------|---------------|
+| HIGH | XS-S | Any | DO NOW (quick win) |
+| HIGH | M-L | HIGH | PRIORITIZE (schedule this sprint/next) |
+| HIGH | L-XL | MEDIUM | ROADMAP (plan for quarter) |
+| MEDIUM | XS-S | Any | BATCH (group with similar requests) |
+| MEDIUM | M+ | LOW | BACKLOG (evaluate at next planning) |
+| LOW | Any | LOW | DECLINE (with explanation) |
+
+**Recommendation Template:**
+```
+RECOMMENDATION: [DO NOW / PRIORITIZE / ROADMAP / BATCH / BACKLOG / DECLINE]
+
+SUMMARY:
+[1-2 sentences explaining the recommendation]
+
+IF APPROVED:
+  Effort estimate: [T-shirt size]
+  Target sprint/quarter: [when]
+  Team needed: [who]
+  Dependencies: [if any]
+
+IF DECLINED:
+  Reason: [why this is not the best use of resources now]
+  Alternative: [what we suggest instead]
+  Revisit: [when we will reconsider]
+```
+
+### Step 6: Client Communication
+**Response to Client:**
+```
+Hi [Client Name],
+
+Thank you for raising [brief description of their request].
+
+I want to make sure I understand the underlying need:
+[Reframed problem statement — confirm with them]
+
+Here is our assessment:
+- Impact: [summary]
+- Our recommendation: [action]
+- Timeline: [when they can expect resolution or next update]
+
+[If declined: explain WHY and offer alternative]
+[If approved: explain next steps]
+
+I will keep you updated on progress. Let me know if I have
+captured the problem correctly.
+
+Best,
+[Name]
+```
+
+## Output Artifacts
+- `client-request-[id].md` | `reframed-problem.md` | `request-recommendation.md`
+
+## Quality Criteria
+- Raw request captured verbatim | Reframing questions answered | Problem stated (not just feature) | Impact and effort assessed | Clear recommendation with rationale | Client responded within SLA | If declined, explanation and alternative provided

package/squad-product/tasks/maintain-decision-log-system.md

@@ -0,0 +1,93 @@
+---
+task: maintain-decision-log-system
+responsavel: "@ps-product-ops-specialist"
+responsavel_type: Agent
+atomic_layer: Task
+elicit: false
+
+Entrada:
+  - campo: context
+    tipo: object
+    origem: "workflow ou manual"
+    obrigatorio: true
+
+Saida:
+  - campo: resultado
+    tipo: document
+    destino: "stakeholders"
+
+Checklist:
+  - "[ ] Validar inputs e pre-condicoes"
+  - "[ ] Executar steps conforme documentado"
+  - "[ ] Verificar criterios de qualidade"
+  - "[ ] Gerar output no formato especificado"
+---
+
+# Maintain Decision Log System
+
+## Metadata
+- **Agent:** ps-product-ops-specialist (Mosaic)
+- **Complexity:** Low-Medium
+- **Estimated Time:** 1 hour/week (ongoing maintenance)
+- **Produces:** Updated decision log, decision patterns analysis, governance compliance report
+
+## Purpose
+Manter sistema de registro de decisoes operacional e util. Decision logs morrem quando ninguem mantem — este task garante manutencao ativa.
+
+## Steps
+
+### Step 1: Weekly Log Review
+**Review Checklist (15 min/week):**
+- [ ] All decisions from this week captured?
+- [ ] Each entry has rationale documented?
+- [ ] Decision status current (active/superseded/reversed)?
+- [ ] Cross-references updated (related decisions linked)?
+- [ ] Review dates checked (any decisions due for revisit?)
+
+### Step 2: Decision Quality Metrics
+**Monthly Health Check:**
+| Metric | Target | Current | Status |
+|--------|--------|---------|--------|
+| Decisions logged this month | >= 3 | [N] | [status] |
+| % with rationale documented | 100% | [%] | [status] |
+| % with options considered | >= 80% | [%] | [status] |
+| Avg time to document | < 48h after decision | [hours] | [status] |
+| Decisions revisited on schedule | 100% | [%] | [status] |
+| Team aware of log location | 100% | [%] | [status] |
+
+### Step 3: Pattern Analysis (Monthly)
+**Decision Patterns:**
+| Pattern | Frequency | Insight |
+|---------|-----------|---------|
+| Decisions reversed within 30 days | [N] | [rushing? insufficient data?] |
+| Same decision revisited 3+ times | [N] | [unclear ownership? changing context?] |
+| Decisions without data | [N] | [gut-feel culture? lack of analytics?] |
+| Decisions overruled by client | [N] | [alignment issue? authority unclear?] |
+| Decisions blocked by dependencies | [N] | [dependency management issue?] |
+
+### Step 4: Governance Compliance
+**Decision Governance Rules:**
+| Rule | Compliance | Corrective Action |
+|------|-----------|-------------------|
+| All strategic decisions have exec approval | [Y/N] | [if no, escalate] |
+| Scope changes follow change process | [Y/N] | [if no, enforce] |
+| Technical decisions have architect input | [Y/N] | [if no, involve] |
+| Client-impacting decisions communicated | [Y/N] | [if no, communicate] |
+| Decisions with deadlines reviewed on time | [Y/N] | [if no, schedule] |
+
+### Step 5: Decision Log Maintenance Tasks
+**Ongoing:**
+| Task | Frequency | Action |
+|------|-----------|--------|
+| Archive old decisions | Quarterly | Move >12 month decisions to archive |
+| Update superseded links | As decisions change | Link old → new decision |
+| Index update | Monthly | Refresh master index |
+| Access review | Quarterly | Verify right people have access |
+| Template update | Semi-annually | Improve template based on usage |
+| New member onboarding | Per new member | Show log, explain importance |
+
+## Output Artifacts
+- `decision-log-health-[month].md` | `decision-patterns-[quarter].md` | `governance-compliance-[month].md`
+
+## Quality Criteria
+- Weekly review conducted | All decisions have rationale | Patterns analyzed monthly | Governance compliance checked | Archive maintained | New members onboarded to system