sinapse-ai 1.0.0

package/squad-product/tasks/conduct-jtbd-interviews.md

@@ -0,0 +1,75 @@
+---
+task: conduct-jtbd-interviews
+responsavel: "@ps-product-strategist"
+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"
+---
+
+# Conduct JTBD Interviews
+
+## Metadata
+- **Agent:** ps-product-strategist (Charter)
+- **Complexity:** High
+- **Estimated Time:** 1-2h per interview + 2h synthesis
+- **Produces:** JTBD findings, job map, forces of progress diagram
+
+## Purpose
+Entrevistas Jobs-to-Be-Done (Christensen/Moesta) para entender por que usuarios contratam um produto.
+
+## Steps
+
+### Step 1: Preparation
+Target: People who recently made a decision (adopted/switched/churned) within 90 days.
+
+### Step 2: Switch Interview (Bob Moesta)
+**Timeline (work backward from purchase):**
+Phase 1: First Thought (10min) - When did you first start thinking about finding a solution?
+Phase 2: Passive Looking (10min) - What did you do after that first thought?
+Phase 3: Active Looking (10min) - When did you start actively looking?
+Phase 4: Decision (10min) - What made you decide?
+Phase 5: Experience (10min) - What happened after you started using it?
+
+### Step 3: Four Forces of Progress
+```
+PUSHING toward new: Push 1 (Situation problems) + Push 2 (Pull of new solution)
+HOLDING in current: Hold 1 (Habit/comfort) + Hold 2 (Anxiety of new)
+Switching happens when: Push + Pull > Habit + Anxiety
+```
+
+### Step 4: Job Statement
+```
+When [situation/trigger], I want to [motivation], so I can [outcome].
+Functional Job: [what to accomplish]
+Emotional Job: [how to feel]
+Social Job: [how to be perceived]
+```
+
+### Step 5: Job Map (8 Universal Steps)
+DEFINE > LOCATE > PREPARE > CONFIRM > EXECUTE > MONITOR > MODIFY > CONCLUDE
+
+### Step 6: Synthesize (after 5+ interviews)
+Common triggers, shared jobs, recurring forces, switching patterns, underserved steps.
+
+## Output Artifacts
+- `jtbd-interview-[N].md` | `jtbd-synthesis.md` | `job-map.md` | `forces-of-progress.md`
+
+## Quality Criteria
+- Min 5 interviews | Switch format followed | All 4 forces captured | Job includes functional+emotional+social

package/squad-product/tasks/conduct-quarterly-roadmap-review.md

@@ -0,0 +1,68 @@
+---
+task: conduct-quarterly-roadmap-review
+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"
+---
+
+# Conduct Quarterly Roadmap Review
+
+## Metadata
+- **Agent:** ps-orchestrator (Vector)
+- **Complexity:** High
+- **Estimated Time:** 4-6 hours (prep + session)
+- **Depends On:** Quarter metrics available, strategic context current
+- **Produces:** Updated roadmap, quarter retro, next quarter plan
+
+## Purpose
+Review trimestral de roadmap que avalia progresso, atualiza prioridades e alinha expectativas com visão interna e do cliente.
+
+## Steps
+
+### Step 1: Quarter Performance Review
+Planned vs Delivered items, OKR Scores (0.0-1.0, target avg 0.6-0.7), Discovery sprints completed, Hypotheses validated
+
+### Step 2: Roadmap Retrospective
+What Went Well → What Didn't → What We Learned
+
+### Step 3: Update Roadmap (Now/Next/Later — Janna Bastow)
+```
+NOW (Current Quarter): Committed, >80% confidence
+NEXT (Next Quarter): Shaped, 50-80% confidence
+LATER (Future): Opportunities, <50% confidence
+```
+Move completed → Done, NEXT → NOW, new opportunities → LATER, remove irrelevant
+
+### Step 4: Dual Roadmap
+Internal: Full detail, technical items, tech debt, dependencies
+Client-facing: Outcomes-focused, business impact, no internal jargon
+
+### Step 5: Next Quarter Planning
+**Investment Split (70/20/10):** Core 70% | Adjacent 20% | Transformational 10%
+
+## Output Artifacts
+- `quarterly-review-Q[N].md` | `roadmap-updated.md` | `okrs-Q[N+1]-draft.md` | `client-roadmap-Q[N+1].md`
+
+## Quality Criteria
+- Every planned item accounted for
+- OKRs scored with real data
+- Roadmap reflects latest evidence
+- Client version prepared and reviewed by Proxy

package/squad-product/tasks/conduct-user-interviews.md

@@ -0,0 +1,139 @@
+---
+task: conduct-user-interviews
+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"
+---
+
+# Conduct User Interviews
+
+## Metadata
+- **Agent:** ps-discovery-lead (Quorum)
+- **Complexity:** Medium
+- **Estimated Time:** 1-2 hours per interview + 30min synthesis each
+- **Produces:** Interview notes, quotes, behavior patterns, insight cards
+
+## Purpose
+Conduzir entrevistas de descoberta com usuarios seguindo Continuous Discovery Habits (Teresa Torres). O objetivo e entender comportamentos e necessidades, NAO validar solucoes pre-concebidas.
+
+## Steps
+
+### Step 1: Recruit Participants (5-8 per round)
+**Screening Criteria:**
+- Recent behavior (performed target action in last 2-4 weeks)
+- Segment match (fits target persona)
+- Diversity (mix of power users, new users, churned users)
+- Accessibility (available within sprint timeline)
+
+**Recruitment Channels:**
+| Channel | Speed | Quality | Cost |
+|---------|-------|---------|------|
+| In-product intercept | Fast | High (active users) | Free |
+| Customer success referral | Medium | High (known context) | Free |
+| Email outreach | Slow | Medium | Free |
+| Panel/service (UserTesting, etc.) | Fast | Variable | Paid |
+| Social media | Fast | Low (self-selection bias) | Free |
+
+**Anti-Pattern:** Never interview only happy customers. Include frustrated and churned users.
+
+### Step 2: Prepare Interview Guide
+**Structure (45-60 min):**
+
+**Opening (5 min):**
+- Introduce yourself and purpose
+- "There are no right or wrong answers"
+- "I am here to learn from you, not to sell anything"
+- Ask permission to record
+
+**Context Setting (10 min):**
+- "Tell me about your role and what a typical day looks like"
+- "How does [product/domain] fit into your work?"
+- Listen for: pain points, workarounds, frequency of use
+
+**Core Exploration (25-30 min):**
+- "Walk me through the last time you [target behavior]"
+- "What was happening that made you decide to do that?"
+- "What did you try first? What happened next?"
+- "What was the hardest part?"
+- "If you could wave a magic wand, what would change?"
+
+**Teresa Torres Specific Prompts:**
+- **Timeline:** "Take me back to when this started. What was happening?"
+- **Emotion:** "How did that make you feel?"
+- **Comparison:** "Have you tried any other way to solve this?"
+- **Frequency:** "How often does this happen?"
+- **Impact:** "What happens when you cannot solve this?"
+
+**Closing (5-10 min):**
+- "Is there anything I should have asked but did not?"
+- "Who else should I talk to about this?"
+- Thank participant
+
+### Step 3: Conduct Interview
+**During Interview Rules:**
+- [ ] Follow the 80/20 rule (participant talks 80%)
+- [ ] Ask open-ended questions only
+- [ ] Never pitch or explain your solution
+- [ ] Follow interesting threads (deviate from guide when valuable)
+- [ ] Note exact quotes (verbatim, not paraphrased)
+- [ ] Observe body language and emotional reactions
+- [ ] Ask "why" and "tell me more" frequently
+
+**Red Flags (interviewer bias):**
+- Leading questions ("Do you think X would be useful?")
+- Hypothetical questions ("Would you use feature Y?")
+- Showing solution before understanding problem
+- Confirming your hypothesis instead of exploring
+
+### Step 4: Post-Interview Synthesis (within 24h)
+**Per Interview, Create Insight Card:**
+```
+Participant: [ID, not name]
+Segment: [persona/segment]
+Context: [situation that triggered behavior]
+Behavior: [what they actually did]
+Pain Point: [what was hard or frustrating]
+Workaround: [how they solved it without us]
+Quote: "[exact words]"
+Opportunity: [what this suggests we could do]
+Surprise: [what was unexpected]
+```
+
+### Step 5: Cross-Interview Pattern Analysis (after 5+ interviews)
+**Pattern Detection:**
+1. Group insight cards by theme
+2. Count frequency of each theme
+3. Identify strongest patterns (mentioned by 3+ participants)
+4. Note contradictions between participants
+5. Map patterns to Opportunity Solution Tree
+
+**Saturation Check:** Stop interviewing when new interviews reveal no new patterns (typically 5-8 for a defined segment).
+
+**Synthesis Output:**
+| Pattern | Frequency | Confidence | Supporting Quotes | Opportunity |
+|---------|-----------|-----------|-------------------|-------------|
+| [theme] | [N/total] | High/Med/Low | "[quote1]", "[quote2]" | [what to explore] |
+
+## Output Artifacts
+- `interview-notes/[participant-id].md` | `insight-cards/[id].md` | `interview-synthesis.md` | `pattern-analysis.md`
+
+## Quality Criteria
+- Min 5 interviews per segment | No leading questions used | Synthesis within 24h of each | Pattern analysis after 5+ | Exact quotes captured | Opportunities mapped to OST

package/squad-product/tasks/configure-feature-flag-rollout.md

@@ -0,0 +1,195 @@
+---
+task: configure-feature-flag-rollout
+responsavel: "@ps-delivery-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"
+---
+
+# Configure Feature Flag Rollout
+
+## Metadata
+- **Agent:** ps-delivery-manager (Tempo)
+- **Complexity:** Medium
+- **Estimated Time:** 1-2 hours
+- **Produces:** Feature flag configuration, rollout schedule, targeting rules, cleanup plan
+
+## Purpose
+Configurar feature flags para lancamento gradual e seguro de features. Feature flags sao a rede de seguranca que permite lancar com confianca e reverter instantaneamente se algo der errado.
+
+## Steps
+
+### Step 1: Flag Design
+**Flag Specification:**
+```
+Flag Name: [descriptive-kebab-case-name]
+Description: [what this flag controls]
+Type: Boolean | Multivariate | Percentage
+Owner: [who manages this flag]
+Created: [date]
+Planned Removal: [date — flags are temporary!]
+```
+
+**Flag Naming Convention:**
+```
+Pattern: [feature]-[scope]-[purpose]
+Examples:
+  new-dashboard-v2-rollout
+  pricing-page-experiment-variant
+  dark-mode-beta
+  checkout-flow-redesign
+```
+
+**Flag Types:**
+| Type | Use Case | Example |
+|------|----------|---------|
+| Kill Switch | Emergency disable | payment-gateway-fallback |
+| Release Toggle | Gradual rollout | new-feature-rollout |
+| Experiment | A/B testing | checkout-variant-b |
+| Ops Toggle | Operational control | maintenance-mode |
+| Permission | Access control | premium-feature-access |
+
+### Step 2: Targeting Rules
+**User Targeting Configuration:**
+```
+RULE 1: Internal team
+  Condition: user.email ends_with "@agency.com"
+  Serve: ON
+  Purpose: Internal testing
+
+RULE 2: Beta users
+  Condition: user.segment = "beta"
+  Serve: ON
+  Purpose: Early adopter feedback
+
+RULE 3: Percentage rollout
+  Condition: percentage_rollout = [X%]
+  Serve: ON for X%, OFF for rest
+  Purpose: Gradual exposure
+
+RULE 4: Default
+  Serve: OFF
+  Purpose: Catch-all for non-targeted users
+```
+
+**Segmentation Options:**
+| Segment By | Use When |
+|-----------|---------|
+| User attribute (plan, role, tenure) | Targeting specific user types |
+| Organization/account | Enterprise rollout per-company |
+| Geography | Regional launches |
+| Device/platform | Platform-specific features |
+| Percentage (random) | General gradual rollout |
+| Custom list (user IDs) | VIP/beta testing |
+
+### Step 3: Rollout Schedule
+**Phased Rollout Plan:**
+| Phase | Date | Target | % Users | Duration | Gate Criteria |
+|-------|------|--------|---------|----------|---------------|
+| 0 - Internal | [date] | Internal team | 0% external | 1-2 days | No P0/P1 bugs |
+| 1 - Canary | [date] | 5% random | 5% | 2-3 days | Error rate stable |
+| 2 - Beta | [date] | 25% random | 25% | 3-5 days | Metrics within bounds |
+| 3 - Majority | [date] | 75% random | 75% | 2-3 days | No regressions |
+| 4 - Full | [date] | All users | 100% | — | Stable for 48h |
+| 5 - Cleanup | [date] | Remove flag | — | — | Code cleaned |
+
+**Gate Criteria Between Phases:**
+| Metric | Acceptable Range | Block If |
+|--------|-----------------|----------|
+| Error rate | <= baseline + 0.5% | > baseline + 2% |
+| Latency (p95) | <= baseline + 50ms | > baseline + 200ms |
+| Feature usage | > 0 (users engaging) | 0% adoption after 24h |
+| User complaints | < 3 in phase period | > 10 complaints |
+| Revenue impact | Neutral or positive | > 5% negative |
+
+### Step 4: Monitoring Configuration
+**Real-Time Monitoring:**
+```
+Dashboard: [link to feature-specific dashboard]
+Key Metrics to Watch:
+  1. Feature usage rate (adoption)
+  2. Error rate for flagged code paths
+  3. Latency for flagged endpoints
+  4. Business metrics (conversion, engagement)
+
+Alerts:
+  - Error rate spike: > [threshold] → Slack notification
+  - Usage anomaly: 0 usage after 2h of rollout → Check targeting
+  - Performance regression: p95 > [threshold] → Page on-call
+```
+
+### Step 5: Emergency Procedures
+**Kill Switch Protocol:**
+```
+TRIGGER: [what condition triggers emergency disable]
+
+STEPS:
+1. Disable flag immediately (set to OFF for all)
+   Tool: [LaunchDarkly/Unleash/custom] → Toggle OFF
+   Time to disable: < 1 minute (no deployment needed)
+
+2. Verify feature is disabled
+   Check: [how to confirm feature is off]
+
+3. Notify team
+   Channel: [Slack channel / email list]
+   Template: "Feature [name] disabled at [time] due to [reason]. Impact: [scope]. Investigation underway."
+
+4. Assess impact
+   - Users affected: [how many saw the issue]
+   - Data impact: [any data corruption or loss]
+   - Duration: [how long was issue live]
+
+5. Create incident report
+   - Root cause
+   - Fix plan
+   - Prevention measures
+```
+
+### Step 6: Flag Cleanup Plan
+**Technical Debt Prevention:**
+```
+CLEANUP TIMELINE:
+  Flag created: [date]
+  Full rollout target: [date]
+  Cleanup deadline: [full rollout + 2 weeks]
+  Flag removal PR: [deadline for code cleanup]
+
+CLEANUP STEPS:
+1. Verify 100% rollout stable for 2 weeks
+2. Remove flag checks from code
+3. Remove flag from management tool
+4. Remove flag-specific monitoring (or merge into main)
+5. Update documentation
+```
+
+**Flag Lifecycle Policy:**
+| Flag Age | Status | Action |
+|---------|--------|--------|
+| < 30 days | Active | Normal operation |
+| 30-60 days | Warning | Review — should it be permanent or cleaned? |
+| > 60 days | Overdue | Cleanup sprint — remove or convert to config |
+| > 90 days | Critical | Mandatory cleanup this sprint |
+
+## Output Artifacts
+- `feature-flag-config-[name].md` | `rollout-schedule.md` | `flag-monitoring-setup.md` | `flag-cleanup-plan.md`
+
+## Quality Criteria
+- Flag naming follows convention | Targeting rules documented | Rollout phased (not big-bang) | Gate criteria between phases | Kill switch tested | Cleanup deadline set | No flags older than 90 days in codebase

package/squad-product/tasks/create-product-artifact-template.md

@@ -0,0 +1,144 @@
+---
+task: create-product-artifact-template
+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"
+---
+
+# Create Product Artifact Template
+
+## Metadata
+- **Agent:** ps-product-ops-specialist (Mosaic)
+- **Complexity:** Low-Medium
+- **Estimated Time:** 1-2 hours per template
+- **Produces:** Standardized product artifact templates, template library, usage guidelines
+
+## Purpose
+Criar templates padronizados para artefatos de produto que garantam consistencia entre projetos e clientes. Templates reduzem tempo de setup e garantem que nada critico seja esquecido.
+
+## Steps
+
+### Step 1: Identify Template Need
+**Template Inventory Check:**
+| Artifact | Template Exists? | Quality | Last Updated | Needs Update? |
+|---------|-----------------|---------|-------------|--------------|
+| PRD | [Y/N] | [1-5] | [date] | [Y/N] |
+| User Story | [Y/N] | [1-5] | [date] | [Y/N] |
+| Sprint Plan | [Y/N] | [1-5] | [date] | [Y/N] |
+| Release Notes | [Y/N] | [1-5] | [date] | [Y/N] |
+| Research Brief | [Y/N] | [1-5] | [date] | [Y/N] |
+| QBR Deck | [Y/N] | [1-5] | [date] | [Y/N] |
+| Decision Record | [Y/N] | [1-5] | [date] | [Y/N] |
+| Feature Spec | [Y/N] | [1-5] | [date] | [Y/N] |
+
+### Step 2: Template Design Principles
+**Every template must have:**
+- [ ] Clear purpose statement (when to use)
+- [ ] Required sections marked (vs optional)
+- [ ] Placeholder text that guides (not just "[fill in]")
+- [ ] Examples for complex sections
+- [ ] Metadata block (author, date, version, status)
+- [ ] Quality checklist at the end
+
+**Template Quality Standards:**
+- Usable by someone who has never seen it before
+- Completable in reasonable time (not 20-page bureaucracy)
+- Flexible enough for simple and complex use cases
+- Consistent naming and structure across all templates
+
+### Step 3: Build Template Structure
+**Template Header (universal):**
+```
+# [Artifact Type]: [Title]
+
+## Metadata
+| Field | Value |
+|-------|-------|
+| Author | [name] |
+| Date | [date] |
+| Version | [v1.0] |
+| Status | [Draft / Review / Approved / Archived] |
+| Project | [project name] |
+| Client | [client name] |
+```
+
+**Template Body:**
+- Section headers with guidance text
+- Required fields marked with (REQUIRED)
+- Optional fields marked with (OPTIONAL)
+- Inline examples in italics
+- Tips in blockquotes
+
+**Template Footer (universal):**
+```
+## Quality Checklist
+- [ ] All required sections completed
+- [ ] Reviewed by [role]
+- [ ] No placeholder text remaining
+- [ ] Consistent with project standards
+```
+
+### Step 4: Create Template Variants
+**Per Template, Create:**
+| Variant | Use Case | Complexity |
+|---------|---------|-----------|
+| Lite | Simple projects, quick turnaround | Minimal sections |
+| Standard | Most projects | Full template |
+| Enterprise | Large/complex projects | Extended sections |
+
+### Step 5: Template Library Organization
+**Library Structure:**
+```
+templates/
+├── product/
+│   ├── prd-template.md
+│   ├── feature-spec-template.md
+│   └── roadmap-template.md
+├── discovery/
+│   ├── research-brief-template.md
+│   ├── interview-guide-template.md
+│   └── discovery-report-template.md
+├── delivery/
+│   ├── sprint-plan-template.md
+│   ├── release-notes-template.md
+│   └── launch-checklist-template.md
+├── client/
+│   ├── qbr-template.md
+│   ├── scope-agreement-template.md
+│   └── status-update-template.md
+└── README.md (template index + usage guide)
+```
+
+### Step 6: Template Governance
+**Maintenance Rules:**
+| Rule | Details |
+|------|---------|
+| Review frequency | Quarterly review of all templates |
+| Update trigger | After 3+ users report issues |
+| Deprecation | Archive old versions, redirect to new |
+| Feedback | Template feedback channel established |
+| Ownership | Each template has named owner |
+
+## Output Artifacts
+- `templates/[artifact-type]-template.md` | `template-index.md` | `template-usage-guide.md`
+
+## Quality Criteria
+- Template usable without explanation | Required vs optional sections clear | Examples included | Quality checklist embedded | Variants for different complexity levels | Library organized and indexed