Claude Skills by Canhada-Labs

PLAN-020 Phase 0 item 5 governance probe — verifies that `check_agent_spawn.py` BLOCKS dispatch via the native subagent rail when the spawn prompt has no skill content (neither `## SKILL CONTENT` inline NOR `## SKILL REFERENCE`). Expected hook output for any Task tool call dispatching this agent: `{"decision":"block","reason":"GOVERNANCE: missing_skill_content: ..."}`. If the hook ALLOWS this dispatch, native rail has a governance gap and Phase 1 is NO-GO.

Meta-agent that drafts a new squad bundle (team-personas, pitfalls, skill-selection, personas roster, rationale) from an Owner-supplied domain brief. Read-only on canonical paths; writes ONLY into the sandboxed plan subdir. Sentinel-gated mutations.

AI system and LLM Council management for {{PROJECT_NAME}}. Covers the 3-model

Architecture decision-making framework for {{PROJECT_NAME}}. Covers

How Claude (the CEO) orchestrates a named team of specialist agents. Decision framework, escalation rules, spawn protocol, quality gates, planning, and 3-strike policy. This is the operating system of the CEO.

Chaos engineering, resilience patterns, failure recovery, and fault

Engineering doctrine for using Language Server Protocol tools in agent

Structured code review process for the {{PROJECT_NAME}}. Covers

Structured codebase orientation workflow for {{PROJECT_NAME}}. Produces an actionable mental map — entry points, dependency graph, architectural layers, hot-path identification, and a recommended reading order — before any modification work begins. Invoked via the /onboard <path> slash command or directly by any agent that must reason about an unfamiliar codebase.

LGPD (Lei 13.709/2018) compliance for a Brazilian SaaS platform.

Consent as an auditable state machine for Brazilian LGPD and equivalent regimes. Covers consent event schema (grant, revoke, expire, re-up), per-purpose granularity, downstream propagation windows, consent replay for audit, revocation SLAs, and the invariants every consent mutation must preserve. Use when designing signup flows, consent banners, preference centers, data-subject-request handlers, or any change that alters the consent graph. Combines with state-machines-and-invariants (core) fo...

Advise on 4 Anthropic Cookbook 2026 patterns (COOK-P1..P4) — surface UX hints when a task signature matches a pattern trigger class. Advisory-only emit; never blocks.

Read-only cross-artifact consistency analyzer (port of spec-kit /analyze). 6 detection passes (Duplication/Ambiguity/Underspec/Constitution-Align/Coverage/Inconsistency) with CRITICAL/HIGH/MEDIUM/LOW severity. Capped at 50 findings. Manual-only invocation via /spawn coverage-audit <PLAN-NNN>. Never modifies files.

Cross-LLM Pair-Rail dispatch + verdict interpretation — when to invoke, Cases A-F asymmetric matrix outcomes, Owner override semantics, post-verdict labeling protocol, promotion gate workflow, and anti-patterns to avoid.

PostgreSQL schema design including migration strategy and cross-ORM

CI/CD pipeline design, Docker optimization, PaaS deployment, health

Data Protection Officer reporting discipline for Brazilian LGPD compliance. Covers the Registro de Operações (Art. 37), Relatório de Impacto à Proteção de Dados (RIPD, Art. 38), Data Subject Request response SLAs and tooling, incident notification to ANPD within the 72-hour window (Art. 48), and the signed-trail artifacts auditors expect. Use when designing the DPO dashboard, wiring DSR endpoints, writing incident playbooks, or preparing for an ANPD audit. Combines with compliance-lgpd (core)...

Evidence-based quality assurance doctrine for {{PROJECT_NAME}}. Teaches

Authoritative git workflow doctrine for {{PROJECT_NAME}}. Encodes the mandatory phase sequence (branch → draft-commits → PR-open → review-gate → merge → tag) that every multi-commit plan must follow; phases are not suggestions — out-of-order execution breaks release integrity and invalidates canonical-path governance. Use when authoring a branch strategy, writing commit messages, opening a PR, enforcing a review gate, merging to main, or cutting a release tag. Pairs with `task-chains.yaml:git...

Invite-only product launch, coupon systems, referral tracking,

Natural-language assistant that recommends <=3 contextual skills/commands for the Owner's current task. Activates on `/help me` slash command. Reads the active repo-profile + smart-loading resolver output, scores active skills against the redacted user description, returns top-3 with confidence labels and one-sentence rationales. Future canonical at .claude/skills/core/help-me/SKILL.md.

Identity and trust doctrine for {{PROJECT_NAME}} — token lifecycle (JWT access <= 1h, mandatory refresh rotation), authorization patterns (RBAC/ABAC, scope-based, least privilege), service-to-service trust (mTLS, signed JWTs, no implicit trust), OAuth/OIDC pitfalls (PKCE, state parameter, callback validation, alg=none and audience-check defenses), and zero-trust principles. EXTENDS core/security-and-auth for the identity sub-domain. Use when designing or reviewing any code that issues, valida...

Live-incident operational doctrine for the {{PROJECT_NAME}} —

Safely evolving existing production codebases through incremental

LLM routing and cost-governance doctrine for {{PROJECT_NAME}}. Covers

Engineering doctrine for building MCP (Model Context Protocol) servers

Operational doctrine for scoping code changes to the minimum necessary

Implementing Stripe billing, subscription management, tiered access

Designing observability into systems from the start, including

Detect decomposable tasks and dispatch <=6 sub-agents in parallel. Mandatory primitive per Owner velocity thesis. Activates when CEO would otherwise sequentially execute work a Sonnet/Haiku sub-agent could do equally well. Future canonical at .claude/skills/core/parallelization-by-default/SKILL.md.

Performance engineering for Node.js real-time systems. Covers V8 internals

Inventorying and governing personally identifiable information (PII) as it flows through a B2B SaaS under LGPD. Covers PII classification (sensitive, regular, public), dataflow mapping, egress tracking (third-party processors, backups, analytics), retention per classification, minimization strategy, and the audit views needed to satisfy Art. 37 Registro de Operações. Use when designing new services that touch user data, onboarding a third-party processor, planning analytics or backup, auditin...

Requirements elicitation checklist run by the CEO or a delegated VP Product/VP Engineering before drafting an L3+ plan. Resolves ambiguity, maps stakeholders, surfaces constraints, enumerates tradeoffs, and emits a `spec.md` artifact that downstream Plan→Debate→Execute consumes via `## SPEC CONTEXT`. Kill-switch `CEO_BRAINSTORM_GATE=0` skips the phase.

Patterns for transforming a functional product into one that

Designing and implementing public-facing APIs with versioning,

Use when receiving code-review feedback or a critique — from the

'Unit Tests for English' — validates requirements writing quality, NOT implementation. 5 categories (Completeness/Clarity/Consistency/Coverage/Edge-Cases). Rejects implementation testing language (Verify/Test/Confirm). Writes checklist.md artifact with falsifiable items + spec citations. Manual-only via /spawn requirement-quality-checklist <PLAN-NNN>. Port of spec-kit /checklist.

Security architecture, authentication, authorization, and hardening for

Disciplined ambiguity reduction for PLAN-NNN. 10-category taxonomy (Functional/Domain/UX/NFQ/Integration/Edge-Cases/Constraints/Terminology/Completion/Misc) with 5-question hard cap per session. Dated write-back into PLAN ## Clarifications section. Manual-only via /spawn spec-clarify <PLAN-NNN>. Port of spec-kit /clarify.

Governing correctness through explicit state machines and enforced

Doctrine for authoring clear, precise technical documentation in

Output-economy skill for research-heavy flows. Sacrifices prose polish for token efficiency in exploratory loops. VETO auto-off for code-review, security-engineer, compliance, debate consensus, audit artifacts.

Testing strategy, patterns, and quality assurance for the project.

Anthropological lens for product, market, and organizational research. Covers ethnographic fieldwork design, participant observation, emic/etic perspective management, thick description (Geertz), cultural relativism, and the application of kinship, ritual, and exchange frames to user research and team dynamics. Applies reflexivity discipline throughout: the researcher's positionality is acknowledged and surfaced, not hidden. Enforces IRB-equivalent informed-consent standards and LGPD/GDPR com...

Geographic lens for product, market, and operational analysis. Applies spatial reasoning, GIS and remote-sensing literacy, regional differentiation, place-based analysis, scale awareness, and cartographic discipline to problems of market sizing, supply-chain mapping, regulatory jurisdiction overlays, climate-risk geography, and catchment-area delineation. Operationalises the five geographic themes (location, distribution, interaction, region, scale) as an analytical frame rather than a decora...

Historical method discipline for product, organisational, and market analysis. Applies primary-vs-secondary source hierarchy, provenance verification, contextualisation, periodisation, historiography awareness, counterfactual reasoning, and change-over-time analysis to product evolution, market history, and technical-decision archaeology. Enforces presentism avoidance and single-source prohibition throughout. Use when: tracing the origins of a technology decision, market structure, or organis...

Narrative analysis applied to product, brand, and organisational communications. Grounds every recommendation in established narratological frameworks — Freytag pyramid, Campbell monomyth, Propp morphology, Genette focalisation, Hall reception theory — and enforces the plot-versus-story distinction as the primary diagnostic surface. Covers story structure selection and cultural specificity claims, focalisation as a brand-voice choice, reliable versus unreliable narrator in founder stories, an...

Applied psychology discipline for product, organisational, and research contexts. Covers the full analytical lifecycle: cognitive-bias diagnosis, behavioural experiment design, individual-differences modelling, group dynamics analysis, replication-crisis literacy, and ethical research conduct. Grounds every inference in evidence hierarchy (case study through meta-analysis) rather than pop-psychology shorthand. Distinct from `core/product-conversion-readiness` behavioural-nudge augmentation — ...

Business intelligence reporting discipline covering data-source-of-truth selection, dashboard design, narrative reporting, statistical literacy, visualisation discipline, and audience-tailored output. Governs how business metrics are surfaced to executives, operations teams, and analysts: canonical source per metric, one decision per page, insight over data, and chart type matched to question. Distinct from `core/observability-and-ops` (technical telemetry and system health) — this skill conc...

Executive summary authoring discipline covering Pyramid Principle (Minto SCQ), one-page architecture, decision-enabling structure, audience-aware compression, and the never-bury-bad-news rule. Applies answer-first sequencing, cognitive-economy writing, and named-owner recommendation framing to all outputs. Distinct from `domains/sales/skills/proposal-strategist` (persuasion-to-close focus) and `domains/business-support/skills/analytics-reporter` (data-narrative focus). Use when: converting a ...