Business skills

Check the terms of a specific side-work assignment offered as gyomu-itaku or freelance work in Japan, item by item: what the client has actually put in writing about the deliverable, the fee, the payment due date, what counts as out of scope, how many revisions are included, who bears expenses, who owns the result, confidentiality, and how either side can end it. Convert the fee into an effective hourly figure over the hours the work will really take including meetings, revisions and unpaid preparation, and count the days from delivery to the payment due date. Use when someone is offered or is discussing a paid side job, a freelance assignment, spot consulting, or paid trial work and wants to know what is still unwritten before starting; do not use to judge whether the fee is fair or the terms lawful, to decide whether to accept, to draft or sign the contract for the user, or to check whether their employer's rules permit side work, which is sidework-rules-check.

The English summary is being prepared. Showing the original description.

Plan a resignation and the move to a new employer: check the intended notice date, last working day, and start date against the notice period the employer's own rules require, count the weekdays left against remaining paid leave, and work through the checklist of handover, documents to receive, items to return, and the insurance, pension, and residual tax steps that a gap between jobs creates. Use when a user has accepted an offer and needs to work out when and how to resign, or wants to know what to confirm before giving notice; do not use to rule on whether they can legally leave, to judge a non-compete clause, to promise the departure will go smoothly, or to notify anyone.

The English summary is being prepared. Showing the original description.

Debrief a finished Otameshi Tenshoku trial from the employer's side: set the observed facts against the completion criteria agreed before the start, keep expectations added afterwards, second-hand or off-the-job observations and the company's own late or missing support apart, settle the hours actually worked separately from any evaluation, and draft feedback to the candidate that states facts, support gaps and what happens next without promising a hire or continuation the company has not decided. Use when a hiring manager, recruiter or small-business owner wants to review a trial, decide what to tell the candidate, or work out the settlement after a shortfall; do not use to judge the candidate's aptitude or predict a hire, to cut pay or demand unpaid rework because of dissatisfaction, to compare candidates, or to send the feedback, pay, or update records on the user's behalf.

The English summary is being prepared. Showing the original description.

Facilitate DDD domain modeling sessions via EventStorming conversation and DML (Domain Modeling Language). Use whenever the user wants to model a business domain by discovering domain events, commands, aggregates, policies, read models, and bounded contexts through dialogue. Produces incrementally-built DML as the primary artifact, plus a Markdown session report. Also invoke for refining existing DML, mapping out a new feature's domain model, or when the user says "ドメインモデリングしたい", "イベントストーミング", "DDDで整理したい", "DMLを育てたい".

The English summary is being prepared. Showing the original description.

Trading strategy patterns for the HoneyComb job position exchange. Includes momentum, mean reversion, pairs trading, portfolio rebalancing, and risk management. Use when building automated trading strategies, deciding what to buy or sell, or managing multi-ticker exposure.

The English summary is being prepared. Showing the original description.

Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.

The English summary is being prepared. Showing the original description.

Generates, normalizes, and converts bedGraph signal tracks (4-column chrom/start/end/value, 0-based half-open) with bedtools genomecov, deepTools bamCoverage/bamCompare/bigwigCompare, bedtools unionbedg, and UCSC bedGraphToBigWig. Covers why a raw coverage bedGraph is not comparable across samples until normalized, the CPM/RPKM/BPM/RPGC normalization menu and the conserved-total assumption that makes them wrong under a global perturbation, the strict sorted-non-overlapping-chrom.sizes bedGraphToBigWig contract that silently corrupts a bigWig, effective-genome-size selection, and bin-size aliasing. Use when building or normalizing a coverage/signal track from a BAM, comparing tracks across samples or conditions, converting bedGraph to a browser-ready bigWig, or diagnosing a track that looks plausible but reports wrong heights.

The English summary is being prepared. Showing the original description.

Run the API contract workflow for public interface changes, compatibility constraints, contract tests, documentation, and review.

The English summary is being prepared. Showing the original description.

Use when generating or modifying any Spring Boot class — controllers, services, repositories, DTOs, mappers, or configuration. Enforces strict layer separation and prevents business logic from leaking across boundaries.

The English summary is being prepared. Showing the original description.

Run the API contract workflow for request/response shape changes, compatibility constraints, contract tests, documentation, and review.

The English summary is being prepared. Showing the original description.

Revisa cambios de performance de queries ClickHouse y Postgres (vambe-datascience, CRM, réplicas) contra los errores y aprendizajes de la ronda

The English summary is being prepared. Showing the original description.

Orientación legal y guía de procesos contractuales para el equipo de Vambe (Chile/MX). Usar SIEMPRE ante preguntas legales o de contratos: 'quiero enviar un contrato', 'cómo mando el NDA', 'el cliente quiere cambios', 'cliente M vs L', '¿me pueden demandar?', 'el cliente no paga', 'cómo finiquito a un empleado', 'protección de datos', 'qué le digo al cliente sobre sus datos', 'nos acusan de incumplimiento', 'me llegó carta de abogados', 'quién puede firmar', 'quién es dueño del código', o cualquier consulta sobre contratos, NDAs, reclamos, laboral, RRHH, PI o cumplimiento normativo.

The English summary is being prepared. Showing the original description.

Build robust, production-grade backtesting systems that avoid common pitfalls and produce reliable strategy performance estimates.

The English summary is being prepared. Showing the original description.

A hard-edged writing style contract for timeless, forceful English prose without modern AI tics. Use when users ask for prose or rewrites that must be clean, exact, concrete, and free of AI cadence, filler, or therapeutic tone.

The English summary is being prepared. Showing the original description.

Build production-ready Web3 applications, smart contracts, and decentralized systems. Implements DeFi protocols, NFT platforms, DAOs, and enterprise blockchain integrations.

The English summary is being prepared. Showing the original description.

Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits. Skip for Q&A or trivial edits.

The English summary is being prepared. Showing the original description.

変更差分に追随してドキュメント（README / docs/ / AGENTS.md / SKILL.md）を更新する。ユーザーが「ドキュメント更新」「README 追随」「docs-sync」等を求めたとき、または実装変更で消えたフラグ・旧名・古い既定値がドキュメントに残っていると気づいたときに使用する。差分から外部契約の語を抽出し、ヒットした箇所だけを更新する。

The English summary is being prepared. Showing the original description.

Reconcile SDD Composy task Markdown and the JSON projection: read-only inspect and plan, then apply only with an explicit authority and the CONFIRM-SDD-SYNC token. Use when task contracts and operational state diverged — 'sincronizar as tarefas', 'o JSON das tasks está desatualizado', 'markdown and json disagree'. Do NOT use to list or advance tasks (sdd-tasks), for a status overview (sdd-status), or to simulate approval.

The English summary is being prepared. Showing the original description.

Planeja estratégia de conteúdo — pilares, clusters de tópico, pauta por estágio de compra e priorização ponderada. Use quando o usuário disser "estratégia de conteúdo", "sobre o que escrever", "pauta", "calendário editorial", "cluster de tópicos", "plano de blog".

The English summary is being prepared. Showing the original description.

Organize, categorize, track, and manage invoices systematically with automated extraction of invoice data, payment tracking, and financial organization. Use when processing invoice uploads, extracting invoice details (date, amount, vendor), categorizing expenses, tracking payment status, organizing receipts, generating financial reports, or building accounting and bookkeeping systems.

The English summary is being prepared. Showing the original description.

CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when asked to "think bigger", "expand scope", "strategy review", "rethink this", or "is this ambitious enough". Proactively suggest when the user is questioning scope or ambition of a plan, or when the plan feels like it could be thinking bigger. (gstack)

The English summary is being prepared. Showing the original description.

Generates a concise, executive-ready performance summary covering key metrics, trends, and what's driving movement. Use this skill when someone needs to produce a briefing, executive summary, performance narrative, or stakeholder readout — for example, "write an exec summary of last week's performance," "create a performance briefing for our leadership team," "produce a monthly business review summary," "what should I tell executives about our metrics," or "generate a performance narrative." Also trigger for "QBR summary," "weekly business review," or "stakeholder briefing."

The English summary is being prepared. Showing the original description.

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

The English summary is being prepared. Showing the original description.

Author the project's non-negotiable engineering rules — the constitution that every feature spec, plan, and implementation must satisfy. Load when the user asks to write a constitution, define project rules, set engineering invariants, write project standards, define non-negotiables, capture agent guardrails as policy, or when spec-driven-development orchestrator routes here. Also triggers on "project constitution", "engineering invariants", "non-negotiable rules", "project policy", "set our standards", "/constitution". Output: docs/constitution.md. The third strategic artifact alongside AGENTS.md (agent behavior) and product-soul (strategy).

The English summary is being prepared. Showing the original description.