上記に当てはまらないスキル（1.3万 件）
Founder orchestrator persona for Marcus Tiongson's gaia-skill-tree sessions. Activates the planner-and-delegator role defined in founder/ORCHESTRATOR.md — thinking partner, session steward, subagent spawner. Use at the start of any founder-mode work session on this repo.
日本語の概要は準備中です。原文の説明を表示しています。
Repair verified review and CI failures and monitor bounded CI windows at the current SHA. Use for "address review items", "run to green", or the CI stage; diagnose and repair authorized failures without waiting at routine milestones.
日本語の概要は準備中です。原文の説明を表示しています。
Turn verified findings into a bounded file-aware plan and reuse or prepare a draft PR. Use for "plan the fix", "draft the implementation plan", or the planning stage of feature-pipeline; preserve actual human gates without making every plan require approval.
日本語の概要は準備中です。原文の説明を表示しています。
Adversarially review the full relevant PR diff with isolated probes and meaningful before/after checks. Use for "review the PR", "sandbox review", or the review stage; retain required reviewer independence and report self- review limits honestly.
日本語の概要は準備中です。原文の説明を表示しています。
Use for broad, sharded discovery-only Gaia curation; for one source page use gaia-curate. A Sol/Terra-class orchestrator preflights capacity, shards safe volume work to configurable Luna workers, converges risky cases, and stops at human L4 review.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect scope and unexpected registry drift against the actual PR base and leave a concise final receipt. Use for "check for PR drift" or the final stage of feature-pipeline; never silently discard unknown changes or infer a clean diff from validator success.
日本語の概要は準備中です。原文の説明を表示しています。
Define Malli schemas for commands, events, and queries using defschemas
日本語の概要は準備中です。原文の説明を表示しています。
Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification.
日本語の概要は準備中です。原文の説明を表示しています。
Implement query handlers that read from event-sourced read models
日本語の概要は準備中です。原文の説明を表示しています。
Build read models by reducing events into queryable state
日本語の概要は準備中です。原文の説明を表示しています。
Implement command handlers that validate state and emit events using the Grain framework
日本語の概要は準備中です。原文の説明を表示しています。
Analyze thermal-fluid engineering systems, experiments, CFD, and correlations with explicit assumptions, validity limits, uncertainty, and mechanism-based interpretation. Use for heat transfer, fluid mechanics, phase change, HVAC, energy systems, turbomachinery, piping, or thermal management.
日本語の概要は準備中です。原文の説明を表示しています。
Run structured product thinking exercises before writing a spec. Use this skill when: - You need to think through a feature idea before writing a PRD - You want to run the 11-star experience exercise for a feature - You need a positioning statement using Geoffrey Moore's framework - You want to define product principles and success vision for a new feature - You have a raw feature idea and need to turn it into a structured brief
日本語の概要は準備中です。原文の説明を表示しています。
Prioritize a feature backlog or list of ideas. Use when the user says "help me prioritize", "prioritize this backlog", "RICE score these", "MoSCoW", "opportunity solution tree", "what should we build first", "rank these features", or has a list of items and needs to decide order - even if they don't explicitly say "prioritization".
日本語の概要は準備中です。原文の説明を表示しています。
Generate a pre-launch readiness checklist for feature releases. Use this skill when: - A feature is nearing completion and you need a launch readiness checklist - You want to ensure all pre-launch items are covered (docs, training, support, rollback) - You are planning a phased rollout and need a structured go-to-market plan
日本語の概要は準備中です。原文の説明を表示しています。
Write OKRs (Objectives and Key Results). Use when the user says "write OKRs", "help me set goals", "create objectives and key results", "quarterly goals", "team OKRs", "I need to define success for this quarter", "Doerr method", or wants to translate a strategic direction into measurable targets - even if they don't explicitly say "OKRs".
日本語の概要は準備中です。原文の説明を表示しています。
Write a Product Requirements Document (PRD). Use when the user says "write a PRD", "document this feature", "product requirements for X", "write requirements", "I need a PRD", "pitch this feature", or wants to formalize a feature or product idea into a structured doc - even if they don't explicitly say "PRD".
日本語の概要は準備中です。原文の説明を表示しています。
Run product discovery to identify what to build. Use when the user says "product discovery", "how do I know what to build", "validate this idea", "talk to customers", "are we building the right thing", "discovery process", or wants to reduce the risk of building something users don't want - even if they don't say "discovery".
日本語の概要は準備中です。原文の説明を表示しています。
Write a concise feature spec for engineering handoff. Use when the user says "write a spec", "feature spec", "one-pager for eng", "spec this out", "write up this feature", "I need to hand this off to engineering", "shape this up", or wants a concise technical brief - even if they don't say "feature spec".
日本語の概要は準備中です。原文の説明を表示しています。
Write an empowered team brief. Use when the user says "team brief", "product brief", "give the team a problem", "empowered team", "how do I brief engineering", "delegate to the team", "product mission", or wants to give a team clear goals without dictating the solution - even if they don't say "team brief".
日本語の概要は準備中です。原文の説明を表示しています。
Maintain a centralized living risk register across projects. Use this skill when: - You need to create or update a risk register for a project or feature - You want to consolidate risks from individual specs into one register - You need to review and update risk status, mitigations, and owners - You want a cross-project risk view
日本語の概要は準備中です。原文の説明を表示しています。
Assess and improve product-market fit. Use when the user says "product-market fit", "PMF", "do we have PMF", "why aren't users retaining", "we're not growing", "users aren't sticking", "PMF pyramid", "find our target customer", "are we building for the right person", or wants to diagnose why a product isn't growing or retaining - even if they don't explicitly say "product-market fit".
日本語の概要は準備中です。原文の説明を表示しています。
Run a structured incident response. Use when the user says "we have an incident", "production is down", "service is degraded", "on-call response", "p0 incident", "something is broken in prod", "help me manage this incident", "incident commander", or there is an active production issue requiring coordinated response - even if they don't explicitly say "incident response".
日本語の概要は準備中です。原文の説明を表示しています。
Navigate a new leadership role using Michael Watkins' First 90 Days 30/60/90 framework. Use when someone says "I just started a new role", "I'm starting as a new manager", "I joined a new company as a leader", "I was just promoted", "how do I onboard as a leader", "what should I do in my first 30 days", "I inherited a team", "I need a 90 day plan", or "I'm new to this team". Also trigger when someone describes feeling overwhelmed in a new leadership role, unsure where to start, or tempted to make changes too quickly before they've listened. Applies to first-time managers, leaders joining new companies, and leaders moving into new functions or teams within the same company.
日本語の概要は準備中です。原文の説明を表示しています。