Product & Planning

henriquescastilho Bundle

Performs firmware image extraction and analysis using binwalk to identify embedded filesystems, compressed archives, bootloaders, kernel images, and cryptographic material. Covers entropy analysis for detecting encrypted or compressed regions, recursive extraction of nested archives, SquashFS/CramFS/JFFS2 filesystem mounting, and string analysis for credential and configuration discovery. Activates for requests involving firmware reverse engineering, IoT device analysis, embedded system security assessment, or router/camera firmware extraction.

legioncodeinc Bundle

Designs, reviews, and migrates PostgreSQL data layers: schema, indexing, zero-downtime migrations, performance, ORM choice, and serverless DB platform selection. Use when the user says \\\"design this schema\\\", \\\"review this migration\\\", \\\"is this index right?\\\", \\\"should this be jsonb or columns?\\\", \\\"we need a NOT NULL on a 100M-row table\\\", \\\"Drizzle or Prisma?\\\", \\\"Supabase or Neon?\\\", \\\"production query is slow\\\", or when `db-worker-bee` is invoked. Do NOT use for PRD authoring (library-worker-bee), data-layer consumption in components (react-worker-bee), security audits of RLS / PII / encryption-at-rest (security-worker-bee), or RAG / embedding retrieval pipelines (mind-worker-bee).

legioncodeinc Bundle

Implements end-to-end authentication: provider selection (Clerk / Better Auth / Auth.js / Supabase Auth / WorkOS / Stack Auth / Kinde / Stytch), Google OAuth flows including the October 2025 unused-client-deletion policy and GIS migration, MFA / passkeys, RBAC, session storage, and B2B SSO. Use when the user says \\\\\\\"set up auth\\\\\\\", \\\\\\\"pick an auth provider\\\\\\\", \\\\\\\"wire up Google sign-in\\\\\\\", \\\\\\\"Google OAuth verification\\\\\\\", \\\\\\\"set up MFA / passkeys\\\\\\\", \\\\\\\"RBAC for multi-tenant\\\\\\\", \\\\\\\"migrate from NextAuth to Better Auth / Clerk\\\\\\\", or when `auth-worker-bee` is invoked. Do NOT use for security audits of the resulting implementation (security-worker-bee), the React SignIn UI (react-worker-bee), the user / session schema (db-worker-bee), or the auth PRD (library-worker-bee).

legioncodeinc Bundle

Equips asset-worker-bee with the Universal Asset Registry: the 19-asset taxonomy (Features, Pages, Routes, Surfaces, Controls, Displays, Layouts, NavEntries, DesignTokens, Icons, MediaAssets, Fonts, Motion, Breakpoints, ContentEntries, Translations, FeatureFlagBindings, MeterBindings, Entitlements), the registration workflow, the code-vs-DB drift audit, the sync-generator contract, the deprecation/sunset rules, and the canonical Prisma + SQL schema. Use when registering, auditing, deprecating, or generating sync code for any of the 19 asset types, when checking for drift between code and the registry, or when standing up the registry in a new repo. Not for QA report authorship (use quality-stinger), PRD numbering (use library-stinger), UX design decisions (use ux-ui-svelte-stinger), or security audits of the registry tables (use security-stinger).

legioncodeinc Bundle

Reviews, refactors, and authors React 18/19 codebases using the bulletproof-react architectural pillars and the curated 2025-2026 React ecosystem. Use when the user says \\\"review this React code\\\", \\\"react architecture review\\\", \\\"audit our React app\\\", \\\"state management decision\\\", \\\"what's the bleeding-edge React pattern for X\\\", \\\"propose a React refactor\\\", \\\"is this React anti-pattern\\\", or when `react-worker-bee` is invoked. Do NOT use for visual design (ux-ui-svelte-worker-bee), SEO/Next.js metadata strategy (seo-aeo-worker-bee), security audits (security-worker-bee), or PRD authoring (library-worker-bee).

legioncodeinc Bundle

Designs, audits, and authors Docker / Docker Compose / GitHub Actions / Depot pipelines for Node / Next.js / TypeScript stacks. Use when the user says \\\"review my Dockerfile\\\", \\\"design our CI pipeline\\\", \\\"audit our workflow security\\\", \\\"migrate to Depot\\\", \\\"add a healthcheck to compose\\\", \\\"this build is slow\\\", \\\"we leaked a secret in CI\\\", or when `devops-worker-bee` is invoked. Do NOT use for cloud provisioning (cloud-platform Bees), DB schema or migrations (db-worker-bee, devops-stinger wires the migration step but does not author it), security CVE deep audits (security-worker-bee, devops-stinger surfaces concerns and hands off), or PRD authoring (library-worker-bee).

legioncodeinc Bundle

Equips library-worker-bee with the documentation lifecycle - knowledge-base authoring (public vs private audience split), feature PRD authoring (prd-{###}-{slug}/ with index + sub-PRDs + qa/), issue IRD authoring (ird-{###}-{slug}/ with index + qa/), backwards-PRD generation, sync audits / drift detection, and lifecycle moves (backlog/in-work/completed) against this repo's schema v2 library/. Use when initializing a library/, ingesting issues, planning features, writing knowledge docs, running drift audits, or moving a completed PRD/IRD to its completed/ tier. Not for QA report authorship (use quality-stinger) or narrative knowledge docs (use knowledge-stinger).

legioncodeinc Bundle

Audits a completed implementation against its source plan document and produces a structured findings report. The report goes in the source plan's `reports/` subfolder (e.g., `library/requirements/{lifecycle}/prd-{###}-{title}/reports/{date}-qa-report.md` or `library/issues/{lifecycle}/ird-{###}-{title}/reports/{date}-qa-report.md`); standalone audits go to `library/requirements/reports/{domain}/{date}-qa-report.md`. Use when the user says \\\"QA this\\\", \\\"audit the implementation\\\", \\\"check the plan against the code\\\", \\\"run quality-worker-bee\\\", \\\"verify the PRD was built\\\", or when `security-worker-bee` has just finished and the loop ends with a QA pass before merge. Produces a markdown findings report with scorecard, severity-tagged findings, and a plan-item traceability table. Does not write code, fix issues, or author plans.

legioncodeinc Bundle

Software estimation and forecasting specialist. Covers relative-sizing frameworks (story points, Fibonacci, T-shirt sizing, Planning Poker), the NoEstimates movement and its evidence base, the planning-fallacy literature explaining why estimates are systematically wrong, and cycle-time / throughput-based probabilistic forecasting (Monte Carlo simulation, percentile-based delivery predictions). Invoke when the user says \\\"our story points mean nothing\\\", \\\"should we use NoEstimates?\\\", \\\"how do I do T-shirt sizing for a roadmap?\\\", \\\"we need a 90% confidence delivery date\\\", \\\"explain Monte Carlo to my PM\\\", \\\"why are our estimates always wrong\\\", or any question about sizing, forecasting, or the NoEstimates debate. Do NOT invoke for sprint cadence design, Jira/Linear tool configuration, or team-capacity math -- those belong to the team's agile process or tooling domains.

legioncodeinc Bundle

'Scrum methodology specialist: sprints, ceremonies (Sprint Planning, Daily Scrum, Sprint Review, Retrospective, Backlog Refinement), roles (Scrum Master, PO, Developers), estimation (Fibonacci, Planning Poker, #NoEstimates), Definition of Done templates by maturity, anti-pattern catalog (Scrum-but, Zombie Scrum, HiPPO PO, velocity gaming), framework selection (Scrum vs ScrumBan vs Kanban vs Shape Up), and the \\\"is this actually Scrum?\\\" honesty audit. Use when the user says \\\"audit our Scrum process\\\", \\\"is this Scrum?\\\", \\\"Sprint Planning help\\\", \\\"write our DoD\\\", \\\"retrospective format\\\", \\\"should we switch to Kanban\\\", \\\"Scrum anti-patterns\\\", or when `agile-scrum-worker-bee` is invoked. Do NOT use for project management tooling configuration (Jira, ClickUp), code review (security-worker-bee, react-worker-bee), or general project management without a Scrum context.'

legioncodeinc Bundle

The Svelte 5 + SvelteKit UI enforcement and implementation skill for the OSPRY SvelteKit apps (portal, web, wl). Owns shadcn-svelte 1.x (built on Bits UI v2 + Melt UI), Tailwind v4, the @theme token bridge to the existing PRD-071 design tokens, and the white-label brand contract. Use whenever a PR touches a .svelte file's markup or styling, when adding a shadcn-svelte component, when wiring Tailwind v4 utilities, when bridging an existing CSS custom property into @theme, when verifying an agency brand flows through a component, or when the user says \\\"add a Button\\\", \\\"copy in this shadcn-svelte component\\\", \\\"convert this bespoke style to Tailwind\\\", \\\"does the white-label still work\\\", or \\\"is this on-brief\\\". Do NOT use for the React ux-ui-svelte-stinger's domain (apps/cms Payload chrome) or for bootstrapping a brand-new design system from scratch.

legioncodeinc Bundle

Designs, reviews, and heals vector and embedding storage - schema/column design, index selection (HNSW vs IVFFlat, distance operators), hybrid lexical+vector search, migrations, dataset versioning. Neon plus pgvector plus Drizzle is the primary option for this stack; Deep Lake and Qdrant / managed services remain documented alternatives with a selection matrix. Use when the user says \\\"design this vector table\\\", \\\"which index should this use\\\", \\\"pgvector or Deep Lake or Qdrant\\\", \\\"is this HNSW config right\\\", \\\"wire pgvector into this Drizzle schema\\\", \\\"we need a new embedding column\\\", \\\"how do we heal a missing column\\\", \\\"vector or hybrid search here\\\", or when `vector-store-worker-bee` is invoked. Do NOT use for PRD authoring (library-worker-bee), TypeScript data-access consumption (typescript-node-worker-bee), security audits (security-worker-bee), or recall / embedding retrieval pipelines (retrieval-worker-bee, embeddings-runtime-worker-bee).

legioncodeinc Bundle

Outbound sales specialist for founders running cold email. Covers Apollo / Clay / Smartlead / Instantly / Lemlist tool selection, email deliverability and domain warmup, multi-touch sequence design (3-5 steps), AI personalization without slop (Clay Claygent SKIP rule), reply classification and disqualification, and list hygiene. Use when the user says "set up cold outreach", "my cold email is landing in spam", "write a cold email sequence", "set up Clay personalization", "Apollo vs Instantly", "my reply rate is below 2%", "cold email warmup", "build a list in Apollo", or when cold-outreach-worker-bee is invoked. Do NOT use for inbound SDR workflows, CRM architecture (db-worker-bee), AE discovery call scripts, paid acquisition, or LinkedIn content strategy.

legioncodeinc Bundle

Equips retrospective-worker-bee to run retrospectives that actually change behavior: format selection (Start/Stop/Continue, 4Ls, sailboat, mad/sad/glad, DAKI, Starfish, and more), psychological safety pre-check (Edmondson scale), facilitation playbooks, async retro design, and action-item follow-through discipline. Use when the user says \\\"run a retro\\\", \\\"plan our retrospective\\\", \\\"which retro format should we use\\\", \\\"our retros produce no change\\\", \\\"help with action items from the retro\\\", \\\"how do we do an async retro\\\", or \\\"our team needs better retrospectives\\\". Do NOT use for incident postmortems (different cadence and audience), sprint planning, OKR-setting, or daily standup facilitation.

agentik-os Skill

Create stakeholder alignment artifacts including responsibility matrices, decision frameworks, and communication plans.

agentik-os Skill

Use to orchestrate the ENTIRE CAIO engagement — accompanying a classic company end-to-end to become AI-native — as ONE gap-checked, self-correcting pass that routes every phase to its owner skill and never rebuilds them. It walks the journey law (readiness/go-no-go → offer/sell → discovery → diagnose+architect+roadmap → build → enable+transfer → run+optimize), gap-checks each handoff (is the prior phase's real deliverable present AND sufficient before advancing?), adversarially verifies (≥2-of-3), and ships ONE CAIO Engagement Plan + a live phase tracker the operator drives. EN triggers caio master, run the full CAIO engagement, end-to-end AI transformation, make this company AI-native, orchestrate the CAIO journey, AI-native roadmap end to end, gap-check the transformation, CAIO program plan, where are we in the AI engagement. FR triggers caio master, pilote toute la transformation IA, rendre l'entreprise AI-native de bout en bout, orchestrer le parcours CAIO, plan d'accompagnement IA complet, gap-check de l

agentik-os Skill

Run a guided, role-adaptive AI discovery interview with one employee (usually a C-level or manager) so a Chief AI Officer can understand how the company really works before automating anything. Asks — in the person's own professional language (tech to a developer, marketing to a CMO, finance to a controller, plain words to non-technical people), never AI jargon — about their role, week and month, repetitive vs one-off tasks, handoffs between people, tools, integrations, what's automated vs manual, shadow IT, frictions, what to keep, what to improve, current vs ideal position, and the gap. Scans the company website first, handles consent and anonymization, then exports one standardized ZIP of .md files (identical for every person) ready for the CAIO. ALWAYS use this for an employee discovery interview, AI readiness intake, role or workflow discovery, a "decouverte" or "audit de poste", or CAIO onboarding — even if the word "skill" is never said.

agentik-os Skill

Use BEFORE committing to a Chief-AI-Officer engagement — the pre-sign go/no-go qualification gate, the whitepaper's honest 30-minute discovery call ("I tell you honestly whether your case fits our approach; if not, I redirect you"). Maps a company against a 9-dimension AI-Readiness Maturity Model (0-4 per dimension with evidence), computes a weighted Readiness Index + maturity tier (Nascent / Emerging / Ready / Leading), and returns an honest GO / NOT-YET / REDIRECT verdict — willing to say "not yet, fix X first" or "you don't need us, you need Y". On GO it shapes the engagement (which of the 5 phases, 1-3 months, team size) + indicative investment anchored to the real grid (€2,500 setup + €2,500/member/month, monthly no-minimum) and hands to /market-proposal for the signed SOW. EN triggers AI readiness assessment, AI maturity model, go/no-go, qualify this client, is this company AI-ready, readiness scorecard, pre-engagement qualification, discovery call, should we take this client, CAIO qualification, disqua

agentik-os Skill

Use when a Chief AI Officer (or fractional CAIO) audits an organization, interviews employees, maps daily work, identifies tools and automation needs, designs agentic systems, specifies an AI dashboard, builds a 30/60/90 roadmap, and produces ROI + governance docs — turning a company into a legible, automatable, agentic Company AI OS. EN triggers CAIO audit, enterprise AI audit, company AI strategy, workflow audit, automation backlog, agentic systems design, AI dashboard spec, AI ROI model, company AI OS, AI operating system, build-vs-buy AI, AI governance and HITL. FR triggers audit IA entreprise, audit complet entreprise IA, cartographie des workflows, opportunites d'automatisation, systeme agentique, tableau de bord IA, ROI IA, gouvernance IA, OS IA d'entreprise, rendre l'entreprise lisible. NOT for personal/solo productivity (use personal-os-builder) or implementing a single agent (use agentic-systems-builder).

eturkes Bundle

Therapeutics Data Commons. AI-ready drug discovery datasets (ADME, toxicity, DTI), benchmarks, scaffold splits, molecular oracles, for therapeutic ML and pharmacological prediction.

eturkes Bundle

Pythonic wrapper around RDKit with simplified interface and sensible defaults. Preferred for standard drug discovery including SMILES parsing, standardization, descriptors, fingerprints, clustering, 3D conformers, parallel processing. Returns native rdkit.Chem.Mol objects. For advanced control or custom parameters, use rdkit directly.

eturkes Bundle

PyTorch-native graph neural networks for molecules and proteins. Use when building custom GNN architectures for drug discovery, protein modeling, or knowledge graph reasoning. Best for custom model development, protein property prediction, retrosynthesis. For pre-trained models and diverse featurizers use deepchem; for benchmark datasets use pytdc.

eturkes Bundle

Use when the user is doing AI/ML work in a scientific domain such as biology, chemistry, physics, astronomy, climate, genomics, materials, medicine, ecology, energy, engineering, math, drug discovery, protein design, weather modeling, theorem proving, single-cell, or PDE solving. Hugging Science is a curated catalog of scientific datasets, models, blog posts, and interactive Spaces. This skill helps discover and use resources via `datasets`, `transformers`, the HF Inference API, `gradio_client`, and methodology citations.

griddynamics Bundle

Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.

griddynamics Bundle

Workflow for initializing or upgrading a workspace: context, discovery, documentation, etc.

gaelic-ghost Bundle

Use Hopper on macOS for disassembly, graphs, pseudocode, Objective-C and Swift presentation, procedure and type edits, extensions, and debugging. Use for document setup, navigation, annotation, evidence, comparison, and discovery.

gaelic-ghost Bundle

Test authorized network services with bounded discovery and protocol-aware validation. Use for hosts, ranges, ports, TLS, banners, versions, authentication, exposure, segmentation, configuration, packet evidence, or vulnerability checks.

gaelic-ghost Bundle

Maintain ROADMAP.md as the planning member of the canonical four-document repository suite.

legioncodeinc Bundle

Designs, reviews, and heals the Hivemind Deep Lake data layer - the 7-table ColumnDef schema, USING deeplake DDL, FLOAT4[] embeddings, additive schema healing, append-only version-bump writes, deeplake_index / vector / hybrid search, DeeplakeApi querying, SQL guards, dataset versioning, and BYOC storage. Use when the user says "design this table", "review this ColumnDef", "is this index right?", "should this be a JSONB column or a tensor?", "we need a new NOT NULL column on the memory table", "how do we heal a missing column?", "vector or hybrid search here?", "which storage backend?", or when `deeplake-dataset-worker-bee` is invoked. Do NOT use for PRD authoring (library-worker-bee), TypeScript data-access consumption (typescript-node-worker-bee), security audits of creds / PII / token handling (security-worker-bee), or recall / embedding retrieval pipelines (retrieval-worker-bee for recall, embeddings-runtime-worker-bee for the embedding model).

legioncodeinc Bundle

OKR methodology specialist for writing, grading, and iterating on Objectives and Key Results. Enforces the output-vs-input discipline, diagnoses sandbagged vs. ambitious goal-setting, calibrates quarterly cadence and check-in rituals, contextualizes OKRs against KPIs and MBOs, and adapts the framework for small teams and startups. Activate when the user says "write OKRs", "audit our OKRs", "are these KRs measurable?", "set up a quarterly goal cycle", "OKR vs KPI", "OKR for small team", "grade our OKRs", or when configuring OKR fields in Lattice, 15Five, Weekdone, or Notion. Do NOT activate for company strategy authorship (executives own that), engineering roadmap planning (domain Angels own that), or project management tooling beyond OKR-specific configuration.

legioncodeinc Bundle

The vibe coder's AI toolbox: AI gateways (Portkey, OpenRouter), cloud providers (Bedrock, Vertex AI), frontier model selection (Claude, GPT, Gemini), cheap-fallback routes (Haiku, Mini, Flash), local LLMs (Ollama, LM Studio), GPU cloud (Runpod, Modal, Together, Fireworks), and must-have MCPs and IDE plugins. Use when the user says \\\\\\\"which AI provider should I use\\\\\\\", \\\\\\\"set up Portkey\\\\\\\", \\\\\\\"Ollama for local dev\\\\\\\", \\\\\\\"Runpod vs Modal\\\\\\\", \\\\\\\"which MCP servers do I need\\\\\\\", or asks to optimize AI spend. Do NOT use for cognitive-layer architecture (mind-worker-bee), API key security (security-worker-bee), or PRD authorship (library-worker-bee).

legioncodeinc Bundle

Continuous product discovery coach — Teresa Torres interview cadence, Opportunity Solution Trees, Jobs-to-be-Done interviews, prototype testing, and the "build less, learn more" loop. Use when the user says "run a discovery session", "build an OST", "write an interview script", "map our assumptions", "design a prototype experiment", "weekly discovery summary", or when a team is unsure what to build next and needs to run discovery before planning. Do NOT use for shipped-feature usability testing (quality-worker-bee), UI design decisions (ux-ui-worker-bee), PRD authorship (library-worker-bee), or analytics result interpretation.

legioncodeinc Bundle

Customer-feedback-to-roadmap loop specialist — Userback, Canny, Featurebase, Productboard, Frill, Productlane — platform selection decision tree, in-app-widget vs portal vs voting-board taxonomy, de-duplication discipline, RICE/ICE prioritization, status-transition policy, public vs private roadmap playbook, and CRM/issue-tracker integration wiring. Use when the user says "set up a feedback system", "which feedback tool should I use", "Canny vs Featurebase", "our feature requests are a mess", "set up a public roadmap", "RICE scoring for our backlog", "Productlane + Linear", "voting board for our SaaS", or when product-feedback-roadmap-worker-bee is invoked. Do NOT use for the React UI of an embedded widget (react-worker-bee), the database schema for a custom-built feedback store (db-worker-bee), marketing copy on the public roadmap page (seo-aeo-worker-bee), or billing integration for premium feedback tiers (payments-worker-bee).

agentik-os Bundle

Execute software projects from an approved Blueprint {OS} handoff and a BUILD READY Stepper {OS} graph into tested, reviewed, integrated, documented, release-ready code. Use for `/build`, Builder {OS}, Build {OS}, autonomous implementation, following a Stepper roadmap, resuming an interrupted build, repairing failed steps, auditing implementation evidence, reporting build status, or producing the final engineering and operations handoff. Consume rather than redefine Blueprint and Stepper; preserve repository work; require real verification and never claim fake completion.

agentik-os Bundle

Compile an approved product Blueprint into a challenged, coherent, modern UX/UI definition and a machine-readable Design Handoff for Stepper. Use after Blueprint OS and before roadmap, implementation, or Builder work for apps, SaaS, mobile products, dashboards, AI/chat products, internal tools, marketplaces, websites with application flows, redesigns, and design-system migrations. Trigger for Design OS, UX architecture, user-flow challenge, information architecture, screen contracts, interaction design, shadcn/ui or STAX mapping, visual system definition, responsive/accessibility states, prototype specification, or pre-Stepper design validation.

eturkes Bundle

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.