Help users define a compelling, qualitative description of a future state that aligns decentralized teams and motivates long-term innovation.
日本語の概要は準備中です。原文の説明を表示しています。
2,255 件 ・ 関連度順
概要と使いどころ
Help users define a compelling, qualitative description of a future state that aligns decentralized teams and motivates long-term innovation.
日本語の概要は準備中です。原文の説明を表示しています。
Help users master the transition from product development to active selling by leveraging their unique status as founders to bridge the trust gap and define a scalable sales motion.
日本語の概要は準備中です。原文の説明を表示しています。
Help users define, validate, and operationalize a North Star Metric that bridges the gap between customer value and business success while driving team alignment.
日本語の概要は準備中です。原文の説明を表示しています。
Help users define precise liquidity metrics, set competitive take rates based on value delivery, and manage the delicate balance between supply-side health and platform profitability.
日本語の概要は準備中です。原文の説明を表示しています。
Help users transition from individual execution to a coaching-centric leadership style that scales through the growth of their team. It focuses on identifying skill deficits, providing reflection space, and leveraging frameworks to accelerate professional maturity.
日本語の概要は準備中です。原文の説明を表示しています。
Help users move beyond ambitious goal-setting to create a rigorous diagnosis of challenges and a clear, actionable plan for winning in their specific market.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user explicitly sets an Aegis goal with /aegis-goal, Aegis goal:, or asks to define goal, success evidence, stop condition, or task boundaries before work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when defining ambiguous or high-complexity new features, product behavior, UI/component design, architecture choices, contract changes, or when grilling/pressure-testing a plan or design. Routine small requests stay on the fast path.
日本語の概要は準備中です。原文の説明を表示しています。
Define or review a visual system, DESIGN.md, or redesign direction. Use for typography, layout, color, motion, and interaction design decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Use the local Codex CLI as an independent second agent. Two branches — (1) proactively run `codex review` for a second opinion after completing a substantive change, before presenting it as done or committing; (2) delegate a well-defined implementation task via `codex exec`, ONLY when the user explicitly asks for Codex to do it. Also covers how to prompt Codex.
日本語の概要は準備中です。原文の説明を表示しています。
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.
日本語の概要は準備中です。原文の説明を表示しています。
Use when proactively verifying an installed BGS modpack batch before declaring it good. Triggers - "test the pack", "verification", "post-install check", "is it stable", "what should I test", "测试整合包", "验证安装". NOT for reactive crash/performance diagnosis after failure (use diagnosing-bgs-problems), pre-install mod evaluation (evaluating-bgs-mods), or defining batch boundaries/style (curating-bgs-modpack).
日本語の概要は準備中です。原文の説明を表示しています。
Create LangChain agents with create_agent, define tools, and use middleware for human-in-the-loop and error handling.
日本語の概要は準備中です。原文の説明を表示しています。
Use when framing the system and describing the model for an Agricultural Systems (AgSy) manuscript — defining system boundaries, components, hierarchical levels, and feedbacks, then choosing, describing, and calibrating the model (process/simulation, whole-farm, bio-economic, agent-based, or integrated assessment). This is the distinctive core of an AgSy paper. Structures the model and system; it does not run code for you.
日本語の概要は準備中です。原文の説明を表示しています。
Use when choosing and applying a theory-construction method for an Academy of Management Review (AMR) manuscript — building constructs, defining their domain, specifying relationships, articulating the underlying logic/mechanisms, and setting boundary conditions. This is the THEORY-CONSTRUCTION craft, NOT empirical method; AMR publishes no datasets, no measures, and no statistical tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building the actual theory for an Academy of Management Review (AMR) manuscript — turning a positioned puzzle into defined constructs, explicit relationships, propositions, and boundary conditions. Constructs the theory; it does NOT stress-test the argument's logic (that is amr-data-analysis) or design any data collection (AMR has none).
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or verifying the institutional / accounting-standard / regulatory background for a 《会计研究》 (Accounting Research) manuscript — getting standard clauses, regulatory rules, and effective dates exactly right, since precise institutional detail is a defining bar of this journal. Use before measurement and identification.
日本語の概要は準備中です。原文の説明を表示しています。
Use when strengthening AAMAS reproducibility evidence for interaction claims, including proofs and game definitions, opponent and population sets, self-play protocols, random seeds, compute, uncertainty on strategic outcomes, baselines, and consistency between what the paper claims about agents and what the artifact can actually show.
日本語の概要は準備中です。原文の説明を表示しています。
Use when preparing AAMAS supplementary material - proofs, extended game and mechanism definitions, extra multiagent experiments, opponent-set details, and the anonymized artifact zip - under the size cap, anonymity, and reviewer-discretion limits, including how to split a game-theory-plus-experiments paper across the 8-page body and the supplement.
日本語の概要は準備中です。原文の説明を表示しています。
Use when packaging AAMAS multiagent code, environments, opponent and population sets, random seeds, game definitions, and logs as anonymous supplementary evidence or a public post-acceptance release, even without a separate artifact badge, so that game-theory and MARL reviewers can inspect and re-run the interaction claims.
日本語の概要は準備中です。原文の説明を表示しています。
Audit Xcode project configuration, build settings, scheme behavior, and script phases to find build-time improvements with explicit approval gates. Use when a developer wants project-level build analysis, slow incremental builds, guidance on target dependencies, build settings review, run script phase analysis, parallelization improvements, or module-map and DEFINES_MODULE configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Pipeline analysis composite. Pulls deal/meeting data from any CRM or tracking system, analyzes the pipeline over a user-defined period (weekly, fortnightly, monthly, quarterly), and produces both an executive summary and a detailed diagnostic report. Covers volume, qualification rates, source effectiveness, stage velocity, stuck deals, and actionable recommendations. Tool-agnostic — works with any CRM (Salesforce, HubSpot, Pipedrive, Close, Supabase, CSV).
日本語の概要は準備中です。原文の説明を表示しています。
Web scraping with structured data extraction - define your output schema
日本語の概要は準備中です。原文の説明を表示しています。
Research a company or idea, define the Ideal Customer Profile, and route to the right next step — either mapping the TAM or finding leads/prospects directly. The entry point for any "find me leads", "map my market", or "who should I sell to" request. Auto-loads when a user provides a company URL or idea and asks for leads or market mapping.
日本語の概要は準備中です。原文の説明を表示しています。