「concise」の検索結果

Create a concise daily briefing from calendar items, tasks, messages, and open decisions. Use at the start of a workday to identify priorities, risks, preparation needs, and follow-ups.

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

Write one-page executive briefs and decision memos that turn messy inputs into a concise recommendation, options, risks, decision ask, and next steps. Use when leaders need a fast read before approving budget, policy, vendor, headcount, or strategy changes. Do not use for long-form reports, slide design, or generic summarization without a decision.

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

Draft concise follow-up messages, nudges, reminders, and recap emails from open decisions, stale requests, or recent meetings. Use when the work is repetitive business writing with known context. Do not use for sensitive legal language, high-stakes negotiation, or board-level communication without review.

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

Prevent common AI report pitfalls — bug blending, inflated threat models, and generic language. Train Claude with your best past reports for concise, technical submissions. Based on Critical Thinking Bug Bounty Podcast Episode 166.

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

Fast sprint status check. Reads the current sprint plan, scans story files for status, and produces a concise progress snapshot with burndown assessment and emerging risks. Run at any time during a sprint for quick situational awareness. Use when user asks 'how is the sprint going', 'sprint update', 'show sprint progress'.

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

Validate OpenClaw release candidates through OCM using the built OpenClaw artifact, a broad reusable scenario matrix, copied existing-user state, clean new-user state, concise pass/fail reporting, and focused failure notes. Use when asked to test OpenClaw origin/main, release readiness, upgrade behavior, plugins, services, channels, doctor recovery, packaging, or broad release risk.

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

Use OpenClaw Manager (OCM) safely and correctly for OpenClaw environment lifecycle work, runtime installation/builds, release-shaped local builds, upgrades, migration/adoption, cloning existing user state, service supervision, gateway logs, dev worktrees, plugin testing, model/provider smoke tests, TUI/dashboard checks, cleanup, and concise reporting. Use whenever Codex is asked to use OCM, manage OpenClaw envs/runtimes/services, test OpenClaw with OCM, reproduce existing-user or new-user flows, or avoid breaking user state while working with OpenClaw.

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

Build a morning briefing ritual with Muse: overnight priorities, today's calendar, weather-aware planning, and top 3 focus items as a concise chat summary.

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

Write concise, role-specific cover letters that connect the candidate's story to the employer's needs.

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

Search the web for evidence using the available Exa tools. Prefer concise results and stop when the question is answered.

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

Write a structured weekly or bi-weekly program status report for stakeholders. Use when the user says "write a status report", "program update", "stakeholder update", "weekly status", "RAG status", "program health report", "what do I send to leadership", "write the update for [program]", or needs to communicate delivery progress - even if they don't explicitly say "status report". Produces a concise, scannable report with RAG status, blockers, and decisions needed.

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

Turn a verified Salesforce research packet into a concise, role-aware learning brief with clear objectives, concept sequencing, worked examples, release caveats, checks for understanding, and citations mapped to claims. Trigger keywords: teach me Salesforce, explain Salesforce concept, create learning brief, Salesforce study guide, role-based lesson. NOT for open-ended source discovery or freshness verification — use architect/salesforce-learning-research first. NOT for generating production metadata or changing an org.

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

Technical documentation expert for clear, concise, user-friendly documentation and tutorials

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

Saves learning notes from the current conversation. Classic mode makes concise notes, Mastery mode keeps detailed training artifacts.

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

Rewrite a support response in a different tone - formal, casual, technical, empathetic, or concise.

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

Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments

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

Apply VueUse composables where appropriate to build concise, maintainable Vue.js / Nuxt features.

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

Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.

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

Create concise, actionable plans for coding tasks. Scope work, identify dependencies, and deliver atomic, ordered steps from discovery through validation and rollout.

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

Establish concise, cross-agent project instructions from repository evidence. Use when initializing or repairing AGENTS.md, CLAUDE.md, related discovery links, or project-specific agent guidance.

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

Create and maintain agent skills with concise trigger metadata, judgement-aware guidance, progressive disclosure, and tested interfaces. Use when adding, refactoring, reviewing, or troubleshooting skills and their bundled scripts or references.

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

Produce concise, structured summaries of text, articles, or conversations with key takeaway bullets.

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

Enforces KISS/DRY/YAGNI during authoring and ad-hoc reviews: concise, direct, no unneeded comments. NOT for post-hoc diff/PR review (mk:review); NOT for simplification passes (mk:simplify).

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

Enforces KISS/DRY/YAGNI during authoring and ad-hoc quality reviews. Pragmatic standards: concise, direct, no unnecessary comments. NOT for post-hoc diff/PR review (see mk:review); NOT for behavior-preserving simplification passes (see mk:simplify).

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