「advisor」の検索結果

Workflow Phase 3 — Research and Solution Exploration. Surfaces 2–4 candidate solution approaches with concrete tradeoffs, grounded in current library docs (fetched through the provider named in `.claude/docs-provider.json`) — never in training-data recall. Output lives at `docs/research/<slug>.md`. Candidate ranking and the memo execute in main context; doc/source gathering MAY be delegated to read-only advisory subagents (seed.md §4.2-A).

日本語の概要は準備中です。原文の説明を表示しています。

Workflow Phase 2 — Codebase Scouting and Constraint Discovery. Maps the relevant slice of the codebase for a given task. Produces a scout report at `docs/scout/<slug>.md` naming the files, modules, and patterns the proposed work touches or constrains. Report decisions execute in main context with full conversation visibility; gathering MAY be delegated to read-only advisory subagents (seed.md §4.2-A).

日本語の概要は準備中です。原文の説明を表示しています。

Dev-only check that a drafted spec for THIS baseline repo won't ship dev-tree references to consumer installs. Catches three failure modes — shipped SKILL.md prose that references paths under `src/`, `tests/`, `scripts/`, `obj/` as runtime invocations (in ```bash fences``` OR `inline backticks`, plus shipped `.mjs`/`.js`/`.sh`/`.py` helper-file imports); new Python helpers added under `.claude/skills/<slug>/` (shipped helpers must be `.sh` or `.mjs`/`.js` going forward); and imports of modules that aren't in `obj/template/.claude/manifest.json` (consumer won't have the file). The aggregate scanner (`scan-shipped-skills.mjs`) walks only baseline-owned skill dirs (via `owner: baseline` frontmatter) at top level — `references/` and other subdirs are documentation, not runtime. BLOCKER findings hard-block implementation entry; ADVISORY surfaces but doesn't block. Read-only — surfaces a punch list; maintainer edits the spec and re-runs until CLEAN.

日本語の概要は準備中です。原文の説明を表示しています。

Oracle-bound spec-review check that every structured Rollout prerequisite binds to an enforcement-type acceptance criterion. A prerequisite whose `enforced-by` is missing, dangling, or points at a non-enforcement AC is a BLOCKER (hard-blocks implementation entry via the checker fan-out verdict); a prerequisite left in free prose is ADVISORY. Read-only. Runs in the spec-review fan-out before implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze market conditions, geographic opportunities, pricing, consumer behavior, and product validation across Google Maps, Facebook, Instagram, Booking.com, and TripAdvisor.

日本語の概要は準備中です。原文の説明を表示しています。

Audit npm or pip dependencies for outdated packages and known vulnerabilities. Use when checking package health, preparing for a release, reviewing dependencies before merging a PR, or when asked about outdated packages or security advisories.

日本語の概要は準備中です。原文の説明を表示しています。

Search the web and open-source code for library usage, API syntax, and documentation via Exa. Use this whenever verifying an API signature, looking up how a library is used, checking a config file format, or resolving an error from a third-party dependency -- including when you think you already know the answer, since library APIs drift. Also use for questions documentation cannot answer: release timing, breaking changes, "is X still maintained", licensing, security advisories, and ecosystem comparisons.

日本語の概要は準備中です。原文の説明を表示しています。

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

日本語の概要は準備中です。原文の説明を表示しています。

Code simplification suggestions — clarity, unnecessary complexity, redundant abstractions. Advisory only.

日本語の概要は準備中です。原文の説明を表示しています。

Orientação de liderança técnica para equipes de engenharia, decisões de arquitetura e estratégia de tecnologia. Inclui analisador de débito técnico, calculadora de escalabilidade de equipes, frameworks de métricas de engenharia, ferramentas de avaliação de tecnologia e templates de ADR. Use ao avaliar débito técnico, escalar equipes de engenharia, avaliar tecnologias, tomar decisões de arquitetura, estabelecer métricas de engenharia ou quando o usuário menciona CTO, débito técnico, débito técnico, escalabilidade de equipes, decisões de arquitetura, avaliação de tecnologia, métricas de engenharia, métricas DORA ou estratégia de tecnologia.

日本語の概要は準備中です。原文の説明を表示しています。

Orientação de liderança executiva para tomada de decisões estratégicas, desenvolvimento organizacional e gerenciamento de stakeholders. Inclui analisador de estratégia, modelagem de cenários financeiros, frameworks de governança corporativa e playbooks de relações com investidores. Use ao planejar estratégia, preparar apresentações para conselho, gerenciar investidores, desenvolver cultura organizacional, tomar decisões executivas, ou quando o usuário menciona CEO, planejamento estratégico, reuniões do conselho, atualizações de investidores, liderança organizacional ou estratégia executiva.

日本語の概要は準備中です。原文の説明を表示しています。

[Decision Support] Use when pressure-testing irreversible, high-stakes decisions with adversarial AI advisors.

日本語の概要は準備中です。原文の説明を表示しています。

Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.

日本語の概要は準備中です。原文の説明を表示しています。

Read the Convex deployment's 72h insights (read limits, OCC contention), root-cause each event in code, report evidence-backed perf/cost findings with fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.

日本語の概要は準備中です。原文の説明を表示しています。

Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.

日本語の概要は準備中です。原文の説明を表示しています。

Read the Convex deployment's 72h insights (read limits, OCC contention), root-cause each event in code, report evidence-backed perf/cost findings with fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze market conditions, geographic opportunities, pricing, consumer behavior, and product validation across Google Maps, Facebook, Instagram, Booking.com, and TripAdvisor.

日本語の概要は準備中です。原文の説明を表示しています。

Build structured communication templates for malware incidents including stakeholder notifications, executive briefings, technical advisories, and regulatory disclosures with severity-based escalation procedures.

日本語の概要は準備中です。原文の説明を表示しています。

M&Aアドバイザリー支援スキル。デューデリジェンス（DD）実施、企業価値評価（バリュエーション）、 シナジー分析、PMI（Post Merger Integration）計画策定を包括的に支援。 Use when conducting M&A due diligence (Financial, Legal, IT, HR), company valuation (DCF, Comparable Companies, Precedent Transactions), synergy analysis, or post-merger integration planning. Triggers: "M&A", "デューデリジェンス", "DD", "バリュエーション", "企業価値評価", "DCF", "comparable", "類似企業", "先行取引", "PMI", "統合計画", "シナジー分析", "買収", "合併"

コンプライアンス・内部統制支援の専門スキル。J-SOX/SOX対応、リスクコントロールマトリクス（RCM）作成、 内部監査計画策定をサポート。内部統制の整備・運用評価から監査対応まで一貫した支援を提供。 日英両言語のテンプレートを提供し、グローバル企業にも対応。COSO内部統制フレームワーク（2013年版）に準拠。 Use when: creating J-SOX/SOX compliance documentation, building risk control matrices, planning internal audits, or assessing internal control effectiveness. Triggers: "J-SOX", "SOX", "内部統制", "コンプライアンス", "RCM", "リスクコントロールマトリクス", "内部監査", "compliance", "internal control", "internal audit", "risk assessment", "COSO"

Concrete remediation proposal with Safe Harbour confidence — version bump, inline as first-party code, patch, workaround, or advisory. Use when applying a fix for a triaged CVE, evaluating fix-type trade-offs across registry / source / distro patches, producing rollback-safe manifest edits with dry-run verification, or generating a CycloneDX SBOM after the fix lands.

日本語の概要は準備中です。原文の説明を表示しています。

Advisory checkpoint for deciding whether planning-document edits should be split into a separate planning branch/PR. Use only when the user explicitly asks where to commit `memory/SPEC.md` or `memory/PLAN.md` changes, mentions planning-doc merge conflicts, asks for a planning PR, or instructs you to prepare/submit one. Do not trigger for ordinary ln-* planning edits, one-line status updates, or routine canonical reconciliation.

日本語の概要は準備中です。原文の説明を表示しています。

Knowledge base from the FAA System Safety Handbook (Dec 30, 2000). Use for system safety as a specialty within systems engineering: the five-step safety risk management process (mandated by FAA Order 8040.4 and the AMS), the severity-by-likelihood risk matrix and acceptance bands, the Safety Order of Precedence, system-description models (5M, SHEL(L)), the hazard-analysis activities (PHL/PHA/RHA/SSHA/SHA/O&SHA/HHA), integrated system hazard analysis, the analysis techniques (FTA, FMEA/FMECA, Fault Hazard, Common Cause, Sneak Circuit, Energy Trace), closed-loop hazard tracking (Safety Action Record), and the specialty domains the handbook covers — acquisition-lifecycle safety and contracting (OSA/CSA/SSPP/ISSPP), software safety (control-capability ranking, SHCM, DO-178B), test & evaluation safety, facilities safety, commercial launch safety (AST licensing, expected casualty, MPL/DAMP), system safety training, and Operational Risk Management (ORM) with human/organizational factors. Scope limits: this is a year-2000 FAA how-to; it predates the modern FAA/ICAO Safety Management System (SMS) and Just Culture regulatory frameworks, and many cited orders, advisory circulars, and launch-licensing rules have since been restructured. It is FAA/NAS-centric, leans on MIL-STD-882C, and does not define the SE life-cycle processes themselves (use nasa-npr-7123 / dau-se-guidebook) or reproduce third-party standard text (MIL-STD-882, DO-178B, ISO/IEC/IEEE).

日本語の概要は準備中です。原文の説明を表示しています。