arkaos 4.7.1 → 4.8.0

package/departments/org/skills/principles-audit/SKILL.md

@@ -1,9 +1,14 @@
 ---
 name: org/principles-audit
 description: >
-  Annual audit against the 10 Principles of Effective Organizations. Score 1-5
-  per principle, prioritise the 2-3 weakest, and produce a quarterly plan. The
-  three make-or-break principles are Empowerment, Leadership culture, Reward.
+  Annual org-health audit against the 10 Principles of Effective
+  Organizations: score 1-5 per principle with evidence, flag the make-or-break
+  three (Empowerment, Reward, Leadership culture), and produce a quarterly
+  improvement plan with owners. TRIGGER: "auditoria organizacional", "org
+  health check", "audit the organization", "10 princípios", "principles
+  audit", "/org principles-audit". SKIP: values lived-vs-stated assessment ->
+  lead/culture-audit (culture, not org effectiveness); acting on a
+  weak-structure finding -> org/org-design (the redesign itself).
 allowed-tools: [Read, Write, Edit, Agent]
 ---
 

package/departments/org/skills/remote-setup/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: org/remote-setup
 description: >
-  Remote work setup: async communication, tool stack, rituals, culture preservation.
+  Builds a remote-work playbook: async communication norms, tool stack,
+  rituals, policies, culture preservation, and success metrics. TRIGGER:
+  "passar a equipa a remoto", "setup de trabalho remoto", "remote work
+  playbook", "async-first", "políticas de teletrabalho", "/org remote". SKIP:
+  only trimming the meeting load -> org/meeting-optimize (one slice of remote
+  hygiene); defining the values the remote culture must preserve ->
+  org/culture-define.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/org/skills/sop-process/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: org/sop-process
 description: >
-  SOP creation: step-by-step procedures with roles, tools, exceptions.
+  Creates a Standard Operating Procedure: numbered step-by-step procedure with
+  roles, tools, exceptions, ownership, and a review schedule (SOP Lifecycle).
+  TRIGGER: "documenta este processo", "cria um SOP de RH", "SOP for
+  onboarding", "procedimento passo-a-passo", "process documentation", "/org
+  sop <process>". SKIP: operational and Lean procedures owned by the ops
+  department -> ops/sop-create (same artifact, ops-domain processes);
+  automating the process instead of documenting it -> ops/workflow-automate.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/org/skills/team-assess/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: org/team-assess
 description: >
-  Team assessment: topology type, cognitive load, skill gaps, interaction patterns.
+  Assesses a single team with Team Topologies: topology type, cognitive load,
+  skill gaps, and interaction patterns, delivering a topology recommendation
+  and improvement actions. TRIGGER: "avalia esta equipa", "a equipa está
+  sobrecarregada", "team assessment", "cognitive load da equipa", "skill
+  gaps", "/org assess <team>". SKIP: restructuring the whole organization ->
+  org/org-design (multi-team redesign); trust, conflict, or accountability
+  dysfunction -> lead/team-health (Lencioni Five Dysfunctions).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/agile-po/SKILL.md

@@ -1,9 +1,16 @@
 ---
 name: pm/agile-po
 description: >
-  Agile product ownership: user story writing, acceptance criteria,
-  sprint planning, epic breakdown, backlog prioritization, velocity tracking.
-  INVEST-compliant stories with Given-When-Then acceptance criteria.
+  Full agile product ownership: INVEST user stories with Given-When-Then
+  acceptance criteria, epic breakdown into sprint-sized stories, sprint
+  capacity planning, and value/effort backlog prioritization with velocity
+  tracking. TRIGGER: "faz de product owner", "parte este épico em stories",
+  "break down this epic", "plan the sprint and prioritize", "prioriza o
+  backlog e planeia o sprint", "/pm agile-po". SKIP: writing a single
+  standalone story -> pm/story-write (dedicated story-splitting flow);
+  sprint ceremony alone -> pm/sprint-plan (goal + commitment focus);
+  RICE-scored refinement -> pm/backlog-groom (grooming, not the full PO
+  cycle).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
 ---
 

package/departments/pm/skills/backlog-groom/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: pm/backlog-groom
 description: >
-  Backlog grooming: prioritize with RICE, refine stories, ensure INVEST criteria.
+  Backlog grooming with RICE prioritization: scores and ranks items,
+  refines stories to INVEST-ready state, and delivers a prioritized backlog
+  with ready items. TRIGGER: "groom the backlog", "faz grooming do
+  backlog", "prioriza o backlog", "RICE score these items", "refina estas
+  stories", "/pm backlog". SKIP: writing new stories from scratch ->
+  pm/story-write (creation, not refinement); selecting groomed items into a
+  sprint -> pm/sprint-plan (commitment happens there); full PO cycle with
+  epics and velocity -> pm/agile-po.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/discovery-plan/SKILL.md

@@ -1,8 +1,16 @@
 ---
 name: pm/discovery-plan
 description: >
-  Product discovery using Teresa Torres' Opportunity Solution Tree.
-  Map outcomes to opportunities to solutions to experiments.
+  Product discovery with Teresa Torres' Opportunity Solution Tree: maps a
+  desired outcome to opportunities, solutions, assumptions, and
+  experiments, on a dual-track weekly interview cadence. TRIGGER: "product
+  discovery", "plano de discovery", "opportunity solution tree", "que
+  problema devemos resolver", "which opportunities should we pursue",
+  "valida esta ideia com clientes", "/pm discover". SKIP: goal already set
+  and mapping deliverables to it -> pm/impact-map (goal decomposition, not
+  opportunity exploration); sequencing validated bets over quarters ->
+  pm/roadmap-build; shaping one chosen solution for the betting table ->
+  pm/shape-pitch.
 allowed-tools: [Read, Write, Edit, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/estimate-forecast/SKILL.md

@@ -1,7 +1,15 @@
 ---
 name: pm/estimate-forecast
 description: >
-  Estimation and forecasting: story points, throughput, Monte Carlo probability.
+  Estimation and delivery forecasting: story points, throughput analysis,
+  and Monte Carlo simulation producing confidence intervals (50th/85th/95th
+  percentile) for "when will it be done". TRIGGER: "quando fica pronto",
+  "estima este backlog", "when will this ship", "forecast the release
+  date", "Monte Carlo forecast", "/pm estimate". SKIP: sizing items during
+  refinement -> pm/backlog-groom (estimation inside grooming, not
+  probabilistic forecasting); committing capacity for a single sprint ->
+  pm/sprint-plan; quantifying code-quality drag on delivery ->
+  dev/tech-debt (debt economics, not schedule forecasting).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/impact-map/SKILL.md

@@ -1,7 +1,15 @@
 ---
 name: pm/impact-map
 description: >
-  Impact mapping: WHY → WHO → HOW → WHAT connecting goals to deliverables.
+  Impact mapping (Gojko Adzic): connects a business goal through actors and
+  behaviour changes to concrete deliverables — WHY -> WHO -> HOW -> WHAT —
+  so every deliverable traces back to the goal. TRIGGER: "impact map",
+  "mapa de impacto", "liga o objetivo às entregas", "why are we building
+  this", "que features suportam este objetivo", "/pm impact". SKIP:
+  exploring unknown customer opportunities -> pm/discovery-plan
+  (opportunity tree, not goal decomposition); turning mapped deliverables
+  into a timeline -> pm/roadmap-build; defining the measurable objectives
+  themselves -> leadership/okr-define.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/kanban-setup/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: pm/kanban-setup
 description: >
-  Kanban board setup: columns, WIP limits, policies, flow metrics.
+  Kanban system design (Anderson method): board columns, WIP limits,
+  explicit policies, and flow metrics with a measurement plan. TRIGGER:
+  "setup kanban", "monta o quadro kanban", "define WIP limits", "limites de
+  WIP", "melhora o fluxo da equipa", "/pm kanban". SKIP: timeboxed Scrum
+  cadence with sprint goals -> pm/sprint-plan (iterations, not continuous
+  flow); running the daily sync on the board -> pm/standup-run;
+  probabilistic delivery dates from throughput -> pm/estimate-forecast.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/risk-register/SKILL.md

@@ -1,7 +1,15 @@
 ---
 name: pm/risk-register
 description: >
-  Risk register: identify, assess probability x impact, define mitigation strategies.
+  Project risk register: identifies risks, scores them on a probability x
+  impact matrix, and assigns mitigation strategies and owners, using
+  pre-mortem (Gary Klein) to surface failure modes. TRIGGER: "risk
+  register", "registo de riscos", "quais os riscos deste projeto", "what
+  could go wrong", "faz um pre-mortem do projeto", "/pm risk". SKIP:
+  strategic scenario stress-testing of a business bet -> strategy/premortem
+  (strategy-level kill analysis, not project risk tracking); mapping people
+  who can block the project -> pm/stakeholder-map; security-specific
+  threats -> dev/security-audit.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/roadmap-build/SKILL.md

@@ -1,10 +1,16 @@
 ---
 name: pm/roadmap-build
 description: >
-  Outcome-driven product roadmap — North Star + outcome tree + 3-horizon
-  map (Now/Next/Later) + bet selection + capacity allocation + audience-
-  specific communication. Replaces feature-list roadmaps with measurable
-  bets.
+  Outcome-driven product roadmap: North Star metric, measurable outcome
+  tree, Now/Next/Later three-horizon map, bets with appetite and kill
+  criteria, capacity allocation, and per-audience views — replaces
+  feature-list roadmaps with measurable bets. TRIGGER: "roadmap do
+  produto", "build the product roadmap", "define a North Star", "planeia os
+  próximos trimestres", "outcome roadmap", "/pm roadmap". SKIP:
+  company-level direction and market bets -> strategy/growth-strategy
+  (business strategy, not product sequencing); discovering which
+  opportunities matter first -> pm/discovery-plan; shaping a single bet
+  into a pitch -> pm/shape-pitch.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/shape-pitch/SKILL.md

@@ -1,8 +1,14 @@
 ---
 name: pm/shape-pitch
 description: >
-  Shape Up pitch for the betting table. Defines problem, appetite, solution sketch,
-  rabbit holes, and no-gos. Based on Ryan Singer's Shape Up methodology.
+  Shape Up pitch (Ryan Singer) for the betting table: problem, appetite as
+  a time budget, fat-marker solution sketch, rabbit holes, and explicit
+  no-gos, with hill-chart tracking. TRIGGER: "shape this feature", "escreve
+  o pitch", "prepara a betting table", "define o appetite", "Shape Up
+  pitch", "/pm shape". SKIP: detailed requirements and acceptance criteria
+  -> dev/spec (spec defines the buildable WHAT; a pitch sells a bet);
+  sprint-based commitment -> pm/sprint-plan; deciding which bets enter
+  which quarter -> pm/roadmap-build.
 allowed-tools: [Read, Write, Edit, Agent]
 ---
 

package/departments/pm/skills/sprint-plan/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: pm/sprint-plan
 description: >
-  Sprint planning: select items, define sprint goal, capacity check, commitment.
+  Scrum sprint planning (Scrum Guide 2020): selects backlog items, defines
+  the sprint goal, checks team capacity, and locks the commitment with a
+  definition of done. TRIGGER: "planeia o sprint", "plan the sprint",
+  "sprint planning", "o que entra no próximo sprint", "define o sprint
+  goal", "/pm sprint". SKIP: items not yet refined or prioritized ->
+  pm/backlog-groom (groom before you plan); continuous-flow teams without
+  sprints -> pm/kanban-setup; multi-sprint delivery forecasting ->
+  pm/estimate-forecast.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/stakeholder-map/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: pm/stakeholder-map
 description: >
-  Stakeholder mapping: power/interest grid, communication plan, RACI.
+  Stakeholder mapping: power/interest grid, communication plan with cadence
+  per quadrant, and a RACI matrix assigning responsibility per stakeholder.
+  TRIGGER: "stakeholder map", "mapa de stakeholders", "quem decide neste
+  projeto", "who are the stakeholders", "faz a matriz RACI", "/pm
+  stakeholder". SKIP: stakeholder resistance tracked as a project risk ->
+  pm/risk-register (probability x impact, not influence mapping); defining
+  decision rights and org structure -> org/decision-framework.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/standup-run/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: pm/standup-run
 description: >
-  Run structured standup: what done, what next, blockers. Flow-focused, not status.
+  Runs a structured daily standup — what was done, what's next, blockers —
+  focused on flow and unblocking rather than status theatre; outputs a
+  summary with blockers flagged and actions assigned. TRIGGER: "run the
+  standup", "faz o standup", "daily standup", "ponto de situação da
+  equipa", "quais os bloqueios", "/pm standup". SKIP: sprint-boundary
+  ceremonies (item selection, goal, commitment) -> pm/sprint-plan; board
+  flow policies and WIP limits behind recurring blockers -> pm/kanban-setup
+  (fix the system, not the meeting).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/pm/skills/story-write/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: pm/story-write
 description: >
-  Write user stories with INVEST criteria, acceptance criteria, and story splitting.
+  Writes user stories with Jeff Patton story mapping and INVEST criteria:
+  acceptance criteria, edge cases, test scenarios, and splitting oversized
+  stories. TRIGGER: "escreve as user stories", "write user stories", "user
+  story para esta feature", "parte esta story", "split this story", "/pm
+  story". SKIP: full product-owner cycle (epics, sprints, prioritization)
+  -> pm/agile-po (this is the focused single-story flow); ranking existing
+  stories -> pm/backlog-groom; formal technical spec with API contracts ->
+  dev/spec.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/benchmark-compare/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: saas/benchmark-compare
 description: >
-  Benchmark comparison: compare your metrics against industry quartiles.
+  Compares your SaaS metrics against industry quartiles (KeyBanc + Meritech
+  benchmarks) and delivers a traffic-light report with improvement
+  priorities. TRIGGER: "compare com benchmarks do setor", "estamos acima da
+  média?", "how do my SaaS metrics compare", "benchmark my churn/NRR",
+  "quartis da indústria", "/saas benchmark". SKIP: KPIs not yet defined or
+  tracked -> saas/metrics-dashboard (build the metrics stack before
+  comparing it); a below-benchmark churn number needing root causes ->
+  saas/churn-analysis (diagnosis, not comparison).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/churn-analysis/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: saas/churn-analysis
 description: >
-  Churn analysis: cohort breakdown, retention curves, churn reasons, prevention plan.
+  Diagnoses churn with cohort breakdowns, retention curves, and root-cause
+  churn reasons, ending in a prevention plan. TRIGGER: "churn analysis",
+  "análise de churn", "porque estamos a perder clientes", "retention
+  curves", "cohort retention", "/saas churn". SKIP: pass/fail retention
+  check before approving acquisition spend -> saas/leaky-bucket (gate
+  verdict, not diagnosis); collecting qualitative customer feedback ->
+  saas/voc-loop (voice signal, not cohort math); saving individual at-risk
+  accounts -> saas/customer-success.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/customer-success/SKILL.md

@@ -1,7 +1,15 @@
 ---
 name: saas/customer-success
 description: >
-  Customer success playbook: onboard, adopt, expand, renew, advocate.
+  Builds a customer success playbook across the lifecycle — onboard, adopt,
+  expand, renew, advocate — with health score model, touchpoint cadence,
+  and expansion plays (Lincoln Murphy). TRIGGER: "customer success
+  playbook", "plano de sucesso do cliente", "health score dos clientes",
+  "renewal and expansion plan", "gerir contas em risco", "/saas cs
+  <account>". SKIP: aggregate churn numbers and cohorts ->
+  saas/churn-analysis (metrics diagnosis, not account playbooks);
+  self-serve signup activation -> saas/onboarding-optimize (product
+  onboarding, not managed accounts).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/gtm-strategy/SKILL.md

@@ -1,9 +1,15 @@
 ---
 name: saas/gtm-strategy
 description: >
-  Cross-departmental go-to-market strategy: ICP, positioning, motion selection,
-  channel mix, 90-day execution plan. Orchestrates SaaS + Strategy + Marketing
-  + Sales + Landing.
+  Cross-departmental go-to-market strategy: ICP profile, Onlyness
+  positioning, GTM motion selection (PLG/SLG/community/partner), channel
+  mix, and 90-day execution plan — orchestrates SaaS + Strategy + Marketing
+  + Sales + Landing. TRIGGER: "go-to-market", "estratégia GTM", "como levar
+  o produto ao mercado", "define o ICP e posicionamento", "which GTM
+  motion", "/saas gtm <product>". SKIP: strategy already approved, time to
+  ship -> saas/launch-execute (executes the launch this skill plans);
+  company-level growth beyond one SaaS product -> strategy/growth-strategy;
+  launch email/funnel mechanics -> landing/launch-sequence.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/launch-execute/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: saas/launch-execute
 description: >
-  SaaS launch execution: pre-launch, launch, post-launch with PLG or SLG motion.
+  Executes a SaaS launch end-to-end — pre-launch, launch day, post-launch —
+  with a PLG or SLG motion, delivering a launch checklist with timeline,
+  channels, and success criteria. TRIGGER: "lança o produto", "plano de
+  lançamento do SaaS", "launch checklist", "launch the product", "estamos
+  prontos para lançar?", "/saas launch". SKIP: ICP, positioning, or motion
+  still undecided -> saas/gtm-strategy (strategy precedes execution);
+  e-commerce product drops -> ecom/product-launch; launch email sequences
+  and funnel pages -> landing/launch-sequence.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/leaky-bucket/SKILL.md

@@ -1,9 +1,14 @@
 ---
 name: saas/leaky-bucket
 description: >
-  Leaky-Bucket gate — audit churn and retention BEFORE approving acquisition
-  spend. Every 1% of churn compounds against LTV forever, so fix the bucket
-  before pouring more in. Owned by the RevOps squad.
+  Leaky-Bucket gate — pass/fail audit of churn, NRR, and activation BEFORE
+  approving acquisition spend, with LTV compounding math; every 1% of churn
+  compounds against LTV forever. Owned by the RevOps squad. TRIGGER:
+  "leaky bucket", "podemos aumentar o investimento em aquisição?", "should
+  we scale acquisition", "gate de retenção antes do CAC", "check NRR before
+  spending", "/saas leaky-bucket". SKIP: gate failed and you need root
+  causes -> saas/churn-analysis (cohort diagnosis, not verdict); fixing the
+  activation drop-off itself -> saas/onboarding-optimize.
 allowed-tools: [Read, Write, Edit, Agent]
 ---
 

package/departments/saas/skills/metrics-dashboard/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: saas/metrics-dashboard
 description: >
-  Set up SaaS metrics tracking: define KPIs, data sources, dashboard layout.
+  Sets up SaaS metrics tracking (Janz SaaS Metrics Stack): KPI definitions,
+  data sources, dashboard layout, targets, and alert thresholds. TRIGGER:
+  "metrics dashboard", "define os KPIs do SaaS", "métricas do produto",
+  "track MRR/churn/LTV", "setup metrics tracking", "/saas metrics-setup".
+  SKIP: KPIs already tracked and you want to compare against industry
+  quartiles -> saas/benchmark-compare (comparison, not setup);
+  marketing/funnel performance reporting -> marketing/analytics-report;
+  LTV/CAC economics modelling -> finance/unit-economics.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/micro-saas-stack/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: saas/micro-saas-stack
 description: >
-  Micro-SaaS portfolio strategy: stack multiple small products for diversified revenue.
+  Micro-SaaS portfolio strategy (Walling stacking): plan multiple small
+  products for diversified revenue, with portfolio map, synergies, and
+  revenue targets. TRIGGER: "micro-SaaS stack", "portfólio de micro-SaaS",
+  "vários produtos pequenos em vez de um grande", "stack multiple small
+  products", "diversificar receita com micro-SaaS", "/saas stack". SKIP:
+  evaluating a single niche's potential -> saas/niche-evaluate (one niche,
+  not a portfolio); scoping one product's first version -> saas/mvp-build
+  (single-product MVP scope).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/mvp-build/SKILL.md

@@ -1,7 +1,14 @@
 ---
 name: saas/mvp-build
 description: >
-  MVP scope definition: core features, activation metric, time-to-value target.
+  Defines MVP scope: core feature set, activation metric, time-to-value
+  target, and acceptance criteria for a SaaS first version. TRIGGER:
+  "define o MVP", "MVP scope", "que features entram na v1", "what goes in
+  the first version", "métrica de ativação do MVP", "/saas mvp <product>".
+  SKIP: generating the actual project code -> saas/saas-scaffold (files and
+  stack, not scope); idea not yet validated -> saas/validate-idea (validate
+  before scoping); formal implementation spec for the dev squad -> dev/spec
+  (engineering requirements, not product scope).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/onboarding-optimize/SKILL.md

@@ -1,7 +1,15 @@
 ---
 name: saas/onboarding-optimize
 description: >
-  Onboarding optimization: time-to-value, activation metric, drop-off analysis.
+  Optimizes SaaS onboarding (Wes Bush PLG Activation): time-to-value,
+  activation metric, drop-off analysis, and an experiment backlog with
+  activation targets. TRIGGER: "optimiza o onboarding", "utilizadores
+  desistem depois do signup", "users drop off after signup", "melhorar o
+  time-to-value", "activation rate baixa", "/saas onboard <product>".
+  SKIP: designing the whole PLG motion from scratch -> saas/plg-setup
+  (model selection and flywheel; onboarding is one piece); high-touch
+  onboarding of managed accounts -> saas/customer-success (CS lifecycle,
+  not self-serve activation).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/plg-setup/SKILL.md

@@ -1,8 +1,15 @@
 ---
 name: saas/plg-setup
 description: >
-  Product-Led Growth setup: freemium/trial model selection, activation metrics,
-  onboarding flow, PQL definition. Framework: Wes Bush PLG Flywheel.
+  Product-Led Growth setup (Wes Bush PLG Flywheel): freemium vs trial vs
+  reverse-trial model selection, flywheel design, activation metrics, PQL
+  definition, and onboarding flow. TRIGGER: "PLG", "product-led growth",
+  "freemium ou trial?", "motion self-serve", "define PQLs", "/saas plg
+  <product>". SKIP: iterating an existing onboarding funnel ->
+  saas/onboarding-optimize (tunes activation inside a PLG motion already
+  chosen); full go-to-market including sales-led motions ->
+  saas/gtm-strategy; viral and referral loop design ->
+  marketing/growth-loop.
 allowed-tools: [Read, Write, Edit, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/pricing-strategy/SKILL.md

@@ -1,8 +1,15 @@
 ---
 name: saas/pricing-strategy
 description: >
-  SaaS pricing strategy using value-based pricing (Patrick Campbell), Van Westendorp
-  sensitivity analysis, and competitive positioning. Outputs pricing page structure.
+  SaaS pricing strategy via value-based pricing (Patrick Campbell): value
+  metric selection, Van Westendorp willingness-to-pay, competitive
+  positioning, 3-tier structure, and pricing page rules. TRIGGER: "pricing
+  do SaaS", "quanto devo cobrar", "SaaS pricing strategy", "estrutura de
+  planos e tiers", "Van Westendorp", "/saas pricing <product>". SKIP:
+  e-commerce product pricing -> ecom/pricing-strategy; subscription-box
+  commerce models -> ecom/subscription-model; negotiating price inside a
+  live deal -> sales/pricing-negotiate; LTV/CAC and margin math ->
+  finance/unit-economics.
 allowed-tools: [Read, Write, Edit, Agent, WebFetch, WebSearch]
 ---
 

package/departments/saas/skills/saas-scaffold/SKILL.md

@@ -1,9 +1,14 @@
 ---
 name: saas/saas-scaffold
 description: >
-  Scaffold a production-ready SaaS project with auth, database, billing,
-  API routes, and dashboard. Generates file tree, schema, and env config.
-  Technical scaffolding — for strategy use saas/mvp-build.
+  Scaffolds a production-ready SaaS project (Next.js App Router) with auth
+  (NextAuth/Clerk/Supabase), database (Drizzle), Stripe billing, API routes,
+  and dashboard — generates file tree, schema, env config, and a 5-phase
+  validation checklist. TRIGGER: "scaffold o SaaS", "cria o projeto SaaS",
+  "boilerplate com auth e Stripe", "set up a new SaaS codebase", "/saas
+  scaffold <stack>". SKIP: deciding WHAT goes in the first version ->
+  saas/mvp-build (scope precedes code); generic non-SaaS project setup ->
+  dev/scaffold (stack scaffolding without billing/auth SaaS assumptions).
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent]
 ---
 

package/departments/saas/skills/voc-loop/SKILL.md

@@ -1,9 +1,16 @@
 ---
 name: saas/voc-loop
 description: >
-  Voice of Customer loop — collect signal, close the loop with the customer,
-  cluster the themes, and run PDCA. Only 1 in 26 unhappy customers complains,
-  so closing the loop beats collecting more. Owned by the RevOps squad.
+  Voice of Customer loop — collect signal (NPS, CSAT, CES, tickets, churn
+  reasons), close the loop with the customer, cluster themes, and run PDCA;
+  only 1 in 26 unhappy customers complains, so closing the loop beats
+  collecting more. Owned by the RevOps squad. TRIGGER: "voice of customer",
+  "VoC", "feedback dos clientes", "fecha o loop com o cliente",
+  "NPS/CSAT/CES program", "/saas voc-loop". SKIP: quantitative churn
+  cohorts and retention curves -> saas/churn-analysis (numbers, not
+  voice); acting on
+  one account's feedback -> saas/customer-success (account playbook, not
+  theme clustering).
 allowed-tools: [Read, Write, Edit, Agent]
 ---
 

package/departments/sales/skills/challenger-sell/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: sales/challenger-sell
 description: >
-  Challenger selling: teach, tailor, take control. Reframe the customer's thinking.
+  Prepares a Challenger Sale approach (Dixon/Adamson): commercial insight to
+  teach, message tailoring per stakeholder, and take-control moves that
+  reframe the customer's thinking. TRIGGER: "challenger sale", "reframe o
+  cliente", "commercial insight para esta conta", "ensina o prospect algo
+  novo", "/sales challenger <context>". SKIP: question-led needs discovery ->
+  sales/spin-sell (uncovers needs rather than reframing them); handling a
+  specific objection mid-deal -> sales/objection-handle.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/sales/skills/deal-qualify/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: sales/deal-qualify
 description: >
-  Deal qualification: Metrics, Economic Buyer, Decision Criteria, Process, Champion.
+  Qualifies a deal with MEDDIC/BANT — Metrics, Economic Buyer, Decision
+  Criteria, Decision Process, Champion — into a scorecard with a go/no-go
+  recommendation. TRIGGER: "qualifica este lead", "qualify this deal", "vale a
+  pena este negócio?", "MEDDIC", "BANT", "/sales qualify <deal>". SKIP: health
+  of the whole funnel -> sales/pipeline-manage (stage conversion and aging
+  across all deals); preparing the first conversation before qualification
+  data exists -> sales/discovery-call.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/sales/skills/discovery-call/SKILL.md

@@ -1,7 +1,12 @@
 ---
 name: sales/discovery-call
 description: >
-  Prepare discovery call: research prospect, prepare SPIN questions, define goals.
+  Prepares a discovery call end to end: prospect research, SPIN question bank,
+  call goals, and agenda. TRIGGER: "prepara a discovery call", "primeira call
+  com o prospect", "discovery call prep", "pesquisa este prospect antes da
+  reunião", "/sales discovery <prospect>". SKIP: question craft or SPIN
+  methodology alone, without research and agenda -> sales/spin-sell; scoring
+  whether the deal is worth pursuing -> sales/deal-qualify.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---
 

package/departments/sales/skills/forecast-revenue/SKILL.md

@@ -1,7 +1,13 @@
 ---
 name: sales/forecast-revenue
 description: >
-  Revenue forecast: weighted pipeline, historical conversion, confidence intervals.
+  Builds a revenue forecast from probability-weighted pipeline, historical
+  stage conversion, and confidence intervals, with forecast-accuracy metrics.
+  TRIGGER: "revenue forecast", "previsão de receita", "quanto vamos fechar
+  este trimestre?", "forecast do pipeline", "/sales forecast". SKIP:
+  diagnosing velocity, bottlenecks, or deal aging -> sales/pipeline-manage
+  (pipeline health, not the revenue number); cash-in/cash-out or longer-range
+  financial projections -> finance/cashflow-forecast.
 allowed-tools: [Read, Write, Edit, Bash, Grep, Glob, Agent, WebFetch, WebSearch]
 ---