'loop' 검색 결과

Builds a DRAFT change-communication plan from a change description: audience map, key messages per audience traced to the description, channels, sequence with dates or day offsets, owners, feedback loop and open questions, plus drafts of the first messages for the sponsor to approve. Use when the user asks to "plan the comms for this change", "who needs to hear about this and when", "draft the announcement sequence", "build a communication plan for the rollout", "write the first message to managers about this change" or "how do we tell people about this". Do not use for a clause-by-clause comparison of a changed HR policy with its previous version, use policy-change-briefing instead; for a new hire's first weeks, use onboarding-plan-builder. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Proposes the piping content a P&ID adds to an accepted PFD process model: line inventory with off-page continuity and required ancillary lines, line identification elements per the project line numbering procedure, connection items at nozzles matched to a quoted schedule, per quoted standards, specification break questions and observations. Every proposal cites its source and revision; no source, no proposal; never sizes a line or selects a class. Use when the user asks to "run the piping enrichment", "start the discipline enrichment", "list the lines the P&ID adds to this PFD" or "fill the line identifiers from the numbering procedure" after gate G2. Do not use for instruments, loops or instrument tags, use instrumentation-and-control-enrichment instead; do not use before gate G2, use process-model-check. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Flags where a P&ID draft raises a process safety question and points to the candidate evidence an engineer would review (HAZOP register, relief study, SIL assessment, isolation philosophy), as questions and quoted passages with UNKNOWN for missing documents, plus safety functions, relief devices and isolation requirements carried over as stated. Never rates, sizes, classifies, resolves or declares protection adequate. Use when the user asks to "write the process safety flags", "produce the process safety section of the P&ID enrichment", "list which protection questions this P&ID raises" or "map the HAZOP and relief study evidence to the draft" after gate G2, once the piping and instrumentation sections exist. Do not use for proposing loops, alarms or trips from the control philosophy, use instrumentation-and-control-enrichment instead; do not use for checking identifiers, use tagging-and-numbering. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run an always-on Telegram watch loop under a separate assistant account using MCP push tools. Mode 1 answers when the assistant account is mentioned in team chats, with actionable vault-grounded advice; mode 2 ambiently watches designated chats and pings on salient events. Triggers: "/telegram-watch", "start the telegram watch".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Keep serialized build-in-public content continuous: read one canon file of season, arcs, beats and loops and say which narrative beat to advance next, so episodes chain into a series. Pairs with the episode adapter, which does the writing. Triggers: "/reality-show", "season state", "what arcs are open".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Mine the day's sessions for the owner's intentions, cluster them into distinct ones, store them, and write two or three detailed posts with an explicit ask per channel, plus a loop tracking who answered. Drafts only. Triggers: "/intention", "mine today's intentions", "intention posts".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run a daily accountability loop grounded in the owner's identity layer in the vault: a morning kick (mirror, one rock for the day, known-pitfall guard) or an evening review (what moved, what slipped, tomorrow's rock). Triggers: "/coach", "morning review", "evening review", "keep me on track".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Disciplined diagnosis loop for hard bugs, regressions, flaky failures, and performance problems with unclear cause. Use for root-cause debugging after a concrete symptom exists; do not use for routine implementation or speculative cleanup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Explicit-only interview loop for stress-testing a plan, decision, or idea. Use only when the user asks to grill, interrogate, interview, or stress-test their thinking before action.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Build a complete but efficient Nature-style Chinese PPTX presentation from a remote-sensing, Earth-observation, geospatial AI, or broader scientific paper, preprint, PDF, article text, abstract, figure legends, or reading notes. Use this skill whenever the user asks to make slides/PPT/PPTX for journal club, group meeting, paper sharing, thesis seminar, lab meeting, department report, or academic presentation from a remote-sensing research paper. It identifies the paper type and argument, selects only the figures needed for the story, writes Chinese slide content and speaker notes, creates the actual .pptx deck, and runs an explicit self-review/corrective revision loop focused on figure quality, text overflow prevention, and non-template visual design before delivery. Also trigger on general academic-presentation requests even without the word "Nature", such as turning a paper into slides, building an academic talk deck, conference/defense presentations, and Chinese phrasings like 论文做PPT、遥感论文汇报、组会PPT、文献汇报、学术汇报、做幻灯片、讲paper、读书报告PPT.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

因果関係ループ図の良い点・悪い点を分析し、改善点と改善のための問いを生成

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

検証結果に基づいて因果関係ループ図を洗練・修正する

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

因果関係ループ図を作る時の観点を説明する

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

因果関係ループ図の作成を実行

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

YouTube動画の文字起こしから約5,000字のTips向けノウハウ記事を作成しoutput/に保存する。「Tips記事にして」「/tips-post」で起動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

YouTube動画の文字起こしからnote記事（要約再構成型）を執筆し下書き用Markdownをoutput/に保存する。「note記事にして」「/note-post」で起動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

YouTube動画の文字起こし・台本からX(Twitter)投稿文を生成してoutput/に保存する。「X投稿を作って」「/x-post」で起動。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Investigate Symphony run failures, stalls, and retry loops.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Previous Next Close the short story Stay in the loop, with exclusive offers and product previews.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when adding durable execution to AI SDK for Python, building durable agent loops, or serializing messages across workflow steps.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design verification strategy: diagnose observability, select oracle families, map to loop tiers, surface blind spots. Use after ln-plan when frontier items or scoped slices need oracle design — especially for LLM, visual, or compositional work — or when verification coverage has drifted.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scientific debugging for bugs, flakes, failures, and performance regressions. Use when something is broken, throwing, failing, slow, nondeterministic, or when the user says diagnose/debug this. Builds a trusted repro loop, tests falsifiable hypotheses, installs a regression oracle, and routes durable findings back into ln-* planning.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for auto error capture, categorization and skill gen.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Run and grow the OpenAmer Agent-to-Agent swarm: identity, trust, node-to-node ask, signed skill/insight sharing, and the autonomous self-learning loop.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.