1,758 件 ・ 関連度順
概要と使いどころ
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Turns past decisions into calibrated judgment - scoring old predictions against what happened, assigning credit for delayed results, and separating a bad decision from a good decision that lost. Use during a retrospective, postmortem, quarterly or monthly review, when reviewing decisions taken 30+ days ago, when attributing a result to a cause, or when someone claims to have called something.
日本語の概要は準備中です。原文の説明を表示しています。
Fableクラスの思考プロセスを任意のモデルで再現する思考スキャフォールド。問いの再構築、 前提の検証、選択肢空間の展開、反証、確信度つきの収束という順序をフェーズとゲートで強制する。 設計判断・技術選定・調査・分析・提案など、結論を間違えるコストが高い非自明なタスクで使用。 「深く考えて」「幅広い視野で」「多角的に検討して」「Fableのように考えて」がトリガー。 Use when asked to think deeply, consider all angles, or for high-stakes decisions and analyses.
Generate OpenVEX / CycloneDX VEX attestations from `.vulnetix/memory.yaml` triage decisions, optionally sign with cosign, optionally upload to Vulnetix and post to a GitHub PR. Use when documenting triage decisions for supply-chain consumers, attaching VEX to a CycloneDX SBOM, or satisfying customer attestation requests.
日本語の概要は準備中です。原文の説明を表示しています。
Post-launch review of a shipped PRD against the brief's success metrics. Did we move the metric? What did the data actually show? Which assumptions held, which broke? Which accepted-gap decisions resolved (confirmed vs. invalidated)? What would we do differently? Triggers on "outcome review", "did it work", "post-launch review", "did we move the metric", "retro the feature", "was it worth it". Produces a Confluence outcome-review page and updates the brief + linked decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Builds a self-contained single-file HTML project dashboard (status banner, milestones table, risks heat list, decisions log, links) from the project tracker files the user attaches, pastes or holds in configured knowledge sources, and returns the complete HTML source in chat ready to save as dashboard-project-date.html. Use when the user asks to "build a dashboard for this project", "make a status page I can pin in the team channel", "give me an HTML overview of milestones, risks and decisions", "refresh the project dashboard from the tracker" or "turn these tracker files into a one-page visual summary". Do not use for creating or updating the tracker files or for the written weekly status report, use project-status-tracker instead. Drafts for human review; never approves, authorises or signs off.
日本語の概要は準備中です。原文の説明を表示しています。
Designs and reviews the internal architecture of a WordPress plugin — folder layout, PSR-4 one-class-per-file discipline, Schema/Constants placement, composition-root vs singleton decisions, conditional asset enqueueing, script config via wp_add_inline_script, and prefixed custom-hook naming. Use when scaffolding includes/src, reviewing class organization, asset enqueue code, repeated strings, or "should I make this a singleton" decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Tell the difference between design decisions that age well and decisions that follow the crowd. Use when evaluating whether a design choice is principled or fashionable, or when a client asks to 'make it look modern.'
日本語の概要は準備中です。原文の説明を表示しています。
Study how products evolve over time using archived versions. The decisions that survive redesigns are the taste decisions. Use when understanding what's essential vs. cosmetic in a design, or learning from product evolution.
日本語の概要は準備中です。原文の説明を表示しています。
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
日本語の概要は準備中です。原文の説明を表示しています。
Delegate writing predictable code to the `code-write` command, which has a cheaper writer model write the target file directly so the generated code never enters your context. Use for tests, scaffolding, fixtures, boilerplate, or a new file that copies an existing pattern, and when the user says "code write", "生成を委譲", or "雛形を書かせて". Do NOT use for design decisions, changes to public contracts or shared modules, edits inside an existing file that needs judgment, or logic with subtle correctness requirements.
Three-file state management for session continuity. Maintains STATE.md, DECISIONS.md, and PROGRESS.md as human-readable session context alongside the SQLite ticket database. Use this skill when updating workflow state, logging decisions, tracking session progress, or resuming work after a context break.
日本語の概要は準備中です。原文の説明を表示しています。
MAGI System v2 — AoT 分解 + MELCHIOR/BALTHASAR/CASPAR 合議 + gabriel adversarial probe による 構造化意思決定フレームワーク。判断ポイント 2+ / 影響レイヤー 3+ / 選択肢 3+ で使用。 Use when facing complex decisions with multiple trade-offs or architectural choices.
MAGI System v2 — AoT 分解 + MELCHIOR/BALTHASAR/CASPAR 合議 + lam-harness:gabriel adversarial probe による 構造化意思決定フレームワーク。判断ポイント 2+ / 影響レイヤー 3+ / 選択肢 3+ で使用。 Use when facing complex decisions with multiple trade-offs or architectural choices.
Guide for building and refactoring a FastAPI + Prefect + PostgreSQL/pgvector analytics pipeline that extracts insights from chat data using LLM classification, embeddings, UMAP/HDBSCAN clustering, and narrative generation. Use this skill whenever working on this project's codebase — including adding features, refactoring, debugging, creating new endpoints, modifying pipeline stages, or reviewing architecture decisions. Also trigger when the user asks about project structure, stack decisions, async migration, or best practices for this specific system.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze meeting transcripts, recordings, and notes to extract action items, key decisions, topics, sentiment, and generate summaries using NLP and AI. Use when processing meeting transcripts, extracting action items, summarizing discussions, identifying key decisions, tracking topics and themes, analyzing sentiment, generating meeting notes, or building collaboration and productivity tools.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model and sharpens terminology. Use when user wants to stress-test a plan against their project's language and documented decisions; propose documentation updates for approval as decisions crystallise.
日本語の概要は準備中です。原文の説明を表示しています。
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate one or more thinking frameworks to work through any problem, decision, document, or idea rigorously. Diagnoses which frameworks fit — inversion, pre-mortem, assumption-mapping, socratic, adversarial-hat — then guides the user through them in the right sequence. Load when the user asks for deep thinking, says "help me think through this properly", "apply your best thinking frameworks", "I need to think carefully before deciding", or "what thinking tools should I use here". Also the entry point for any complex problem where the right framework is unclear. Covers product decisions, engineering tradeoffs, personal decisions, strategy, creative challenges — any domain.
日本語の概要は準備中です。原文の説明を表示しています。
Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.
日本語の概要は準備中です。原文の説明を表示しています。
The interview primitive for putting open decisions to an owner. Use on 'grill me', 'stress-test this', or 'what do you need from me before you build this', and whenever a plan, scope, spec, vision, or question ledger needs owner rulings. NOT for steps only a human can perform (use a guided session).
日本語の概要は準備中です。原文の説明を表示しています。
Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic advisor for Evvo Labs business decisions. Use when Vince asks for strategic advice, business opinions, market entry decisions, pricing strategy, product prioritization, resource allocation, partnership evaluation, competitive positioning, or any question about what Evvo should do next. Applies 5 frameworks: VRIO (competitive advantage), Value Stick (pricing/margin), Blue Ocean (market positioning), McKinsey Horizons (resource allocation), Strategy Diamond (initiative planning). Always read references/evvo-strategy.md before advising.
日本語の概要は準備中です。原文の説明を表示しています。