「brief」の検索結果

Generate pre-call research briefs with company news, stakeholder backgrounds, and custom discovery question sets.

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

Generates professional Statements of Work from a project brief. Use when a user needs to create an SOW, scope a project, define deliverables and milestones, or produce a consulting engagement document.

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

Turn a marketing brief or product offer into a finished short-form video ad built in HyperFrames — hook, script, shot-by-shot storyboard, scene-by-scene HTML composition, captions, and voiceover. Outputs platform cuts (vertical 9:16, square, 16:9). Use when you need a launch ad, product promo, social video, or paid-creative concept ready to render.

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

Argues the strongest honest case against a decision, plan, belief, hire, pricing move, strategy, or piece of work the user is leaning toward. Steelmans the other side, ranks at most three objections by consequence, runs a short pre-mortem, credits what the user got right, and ends with what would have to be true for their choice to work. Calibrated and collegial, never combative; says plainly when the position is strong. Use whenever the user says "play devil's advocate", "argue the other side", "poke holes in this", "what am I missing", "am I making a mistake", "talk me out of it", "stress-test this idea", "tell me why this is a bad idea", or asks for pushback on something they have mostly decided. Supports gentle, standard, and hard intensity. Not for interrogating requirements before a build (grill-the-brief) or staging a multi-persona debate (debate-simulator).

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

Generates full consulting proposals from a brief. Input client name, problem description, and rough scope. Outputs proposal.md with executive summary, problem statement, proposed approach, timeline, team, pricing tiers, and terms. Researches client company for personalization. Multiple pricing models. Professional formatting matching consulting standards.

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

Generate a complete, premium design system from a brand brief or an existing site — color tokens, type scale, spacing/radius/elevation, motion language, and component specs — exported as Tailwind config, CSS variables, and a usage doc. Built to look editorial and human-crafted, not template-generated. Use when starting a new product/site, unifying an inconsistent UI, or codifying a brand into reusable tokens.

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

Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.

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

Guides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.

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

Use when the user asks to check on agents, manage their fleet, babysit panes, see what needs attention, get a status report, or when they say "check on my agents", "what needs action", "fleet status", "babysit", "brief me". Requires the control MCP server to be registered and the daemon running.

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

Design, generate, review, and revise editable PowerPoint presentations through a rigorous brief-to-PNG workflow using the public pptx-designer Python library.

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

Transfer full task ownership to a fresh agent with a verified brief and explicit release. Use for replacing the current executor, including a directly assigned task with no work card; not for supervising a helper.

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

Give the owner one page when they come back from sleep, a meeting or a long run: what got done, what is stuck, what waits for their answer, and what it cost in quota. Use when the owner asks what happened while they were away, wants a status page, or when you finish a long stretch of work and must report it.

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

Write, revise or review a charter: the one document that tells an executor what to deliver, what is out of bounds, what the owner already decided, and how each success check will be proven. Use when work needs a written brief before someone else does it, or when asked to write, change or check a charter.

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

After the founder brief, turn it into an honest diagnosis and a prioritized, stage-aware GTM roadmap saved as docs/gtm-cofounder/gtm-roadmap.md. This is the hub the user returns to every session to see where they are and the single next move. Use right after start-here, whenever the user doesn't know what to work on next, wants a plan instead of a one-off task, or is drowning in disconnected tactics.

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

Interview the user once and write a docs/gtm-cofounder/founder-brief.md that every other skill reads first, so the advice is about their real business, not a textbook. Use this before anything else, or whenever the agent lacks context on the user's product, ICP, market, or stage, or is giving generic GTM advice.

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

Before showing the user any substantive GTM deliverable (positioning, value prop, homepage, launch post, pricing, sales script, the brief or roadmap), stress-test it against the standard as an independent critic, because the agent that wrote it is the worst judge of whether it is good. Use as a gate right before presenting work, or when the user asks whether something is actually strong.

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

Reconstruct and report long-running or multi-turn research, architecture questions, reviews, decisions, completion results, and status as a clear, self-contained brief. Use when a reader must re-enter earlier context, understand the real question and its relationships, distinguish verified facts from judgment and open evidence, or make a decision without reconstructing the work log. Quote the relevant original user wording before substantive analysis, keep one coherent main line, use spatial diagrams when relationships matter, and finish with an explicit decision boundary and practical next step.

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

Use when planning a modeling solution, selecting the next useful step or briefing a specialist.

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

Use when the user needs engineering or research-paper figures: system architecture diagrams, algorithm workflows, hardware schematics, benchmark charts, ablation plots, figure briefs, redraws, image edits, or exact publication-style plots from numeric data. Covers Gemini, Nano Banana, OpenAI image models, and local plotting workflows.

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

Converges an underspecified request into a typed IntentSpec before planning or acting. Use when the user asks to implement, add, change, refactor, fix, migrate, configure, handle, triage, sort out, look into or decide something and the request leaves decisions open (which objects, which approach, what happens on failure, which trade-off), contradicts itself, admits two readings, or rests on an approach its sources may rule out — in a codebase, a ticket queue, a research brief or a runbook — or when the user says "clarify the intent", "what do you need from me", or invokes intent-router. Looks up what its sources hold (code, history, decision records, a ticket log, an order record, the policy in force) before asking; asks only preference or irreversible questions, one at a time, with a recommended default; halts instead of guessing; checks the delivered work against the spec. Silent on a fully stated task its sources do not contradict. Not for explaining existing state ("what does X do", "why is Y slow").

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

Turn real product images and a verified brief into a clean Seedance 2.0 minimalist product film. Use for 4–15 second e-commerce or launch ads that require faithful product color/material/geometry, independent anchor-image roles, product-specific actions, restrained camera, readable integrated copy, sound, and a stable closing frame; not for talking-head ads or invented product features.

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

Conduct deep web research using the openbrowser-ai agent: decompose a query, investigate sub-questions across multiple sources, and produce a cited markdown report plus structured JSON under local_docs/research/. Trigger when the user asks to: research a topic, do a deep dive, investigate, gather evidence, compare options, write a literature review, build a briefing, or produce a cited report.

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

Fix "content disappears after publishing" bugs caused by REST API indexing lag. Use when: (1) User publishes content but it doesn't appear in their feed/profile, (2) REST API returns stale data immediately after write operations, (3) Async indexing backends (ClickHouse, Elasticsearch, etc.) haven't processed new events, (4) Content shows briefly then vanishes on refresh. Applies to any system with separate write path (WebSocket/direct DB) and read path (REST API with async indexing).

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

Art direction for any content — reads text, PDF, Word, HTML, PPT, then proposes 2-3 creative directions with photography style, mood, and visual language. After selection, generates AI image prompts and visual briefs section-by-section. Use when the user shares content and needs visual direction, image sourcing, or creative direction for any material.

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