「goal」の検索結果

Japanese (and other non-Hollywood) screenwriting methods (日本编剧方法/原创剧本实战) — distilled from ten Japanese directors and writers in ゼロからの脚本術; Kosawa Ryota (three acts as 起承转合, speed by jumping), Uchida Kenji (beautiful structure, time-axis tricks), Miki Satoshi (small-material notebook, theme emerges later), Sono Sion, Omiya Ellie (dialogue from inner monologue), Kakei Masaya ("if + moreover"), Fukuda Yuichi (character = actor + flaw, audience as tsukkomi), Yokohama Satoko, Takahashi Izumi ("pain"), Yukisada Isao (situation-born originals); plus Arai Haruhiko (IP adaptation, "write what you're ashamed of"). Neighbours; sw-korean-french-screenwriting, ozu-screenplay-style. Use when writing an original Japanese-style script or TV drama, working from small material and fragments, choosing between structure-first and character-first methods, building a Japanese 企画書, designing comedy tsukkomi systems, or when Hollywood models feel wrong for a quiet, daily-life, non-goal-driven story.

Use when the user types /hep-storm, mentions @Hephaestus storm, or asks to force-robustly drive a loop-worthy goal (apps, sites, agents, automations, debugging, multi-step research, data/report generation) to a verified finish. Stormbreaker routes the goal to real Agentlas specialists, materializes a dependency-ordered pipeline fabric, and runs a verifier-first loop that does not stall, run away, or claim false success. Trivial questions are answered directly, not stormed.

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

Use when the user asks OpenClaw to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM chooses the exact roster, which remains goal-bound until explicit completion.

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

Use when the user types /agentlas-storm, /agentlas storm, /hep-storm, or says @Hephaestus storm <goal> to drive a goal through the force-robust Stormbreaker loop with real Agentlas specialists.

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

Use when the user types $hephaestus-network, /hep-network, or /agentlas-network, mentions @Hephaestus, or asks Agentlas to staff a durable goal from registered Local, owner Cloud, and public Hub agents or teams. The active host LLM staffs each turn; the exact roster remains goal-bound until explicit completion.

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

Fast non-interactive briefing before any meeting — auto-detects your next calendar event, pulls relationship history, surfaces open commitments, and produces a one-page brief in under 30 seconds. Use this whenever the user says "brief me", "give me a quick brief", "what's coming up", "background on my next call", "who am I meeting next", "brief me on Sarah", "I have a call in 10 min", "quick rundown", or right before walking into a meeting. Different from /minutes-prep — brief is the fast hook-fireable version that doesn't ask questions and doesn't set goals. Use brief when speed matters; use prep when the user wants to think hard about goals first.

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

Run a company event — the launch party, the customer day, the team celebration — as the operation it is: the goal that shapes every choice, the budget with its forgotten lines, the vendor and venue coordination, the run-of-show with owners, and the day-of roles that keep hosts hosting. Use when asked plan the company event, organize our customer day/holiday party/launch event, what am I forgetting for this event, or be the run-of-show for Thursday. Produces the goal-shaped plan, the budget with the forgotten lines, the run-of-show, and the day-of role card.

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

Run a 复盘 (fupan), the structured project review widely used in Chinese companies: review the goal, assess the result, analyse why, and draw rules for next time, with a blame-free tone and owned actions. Use when asked 帮我做复盘, 项目复盘, 活动复盘, 复盘会怎么开, or a fupan or retrospective in Chinese. Produces the 复盘 document in Chinese with goal versus result, root causes split into controllable and uncontrollable, lessons stated as reusable rules, and an action list with owners and dates, plus a meeting agenda.

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

Help users establish high-impact goals that bridge the gap between abstract company vision and daily execution while maintaining radical focus.

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

Implement a spec using the harness's goal feature.

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

Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: selected by name; one change goes to Plan.

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

Three modes for CS-conference papers (CVPR/ICCV/ECCV vision, ACL/EMNLP/NAACL NLP, ICLR/NeurIPS/ICML/AAAI ML). DIRECT-EDIT mode (common): the user describes a change in Chinese or English and the manuscript (LaTeX or Markdown) is edited directly through a CS-venue writing toolkit with author sign-off (use for 改这段 / 把中文想法写成 latex / polish / de-AI / translate / compress a passage). REVIEW mode (occasional, pre-submission): harden the paper through an adversarial courtroom review engine (N holistic domain reviewers / contestability routing / two-sided trial / three-way verdict / clerk-converged multi-round loop) with consensus-gated, author-signed revisions (use for review / critique / 审稿 / 评审 / mock-review). AUTO mode (unattended, opt-in via /goal): run the review-revise loop toward a verifiable goal, applying safe fixes under a drift-bounded policy and queueing risky ones. Resolves all inputs at runtime, no hardcoded paths. Not a from-scratch drafter (use ml-paper-writing) and not an official-venue rebuttal.

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

Emit and validate the provisional goal block for Autopilot Mode. Owns the 9-field format and resume detection from a pasted goal block.

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

Generate kickoff artifacts for a multi-phase program: umbrella plan, Program Goal Charter, session-goal block, per-phase plan stubs, and the 7-step per-phase inner loop reference.

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

Set up or update a project in the vault: the four-stage folder pipeline, a project-scoped CLAUDE.md with one goal, and links to the concept pages it depends on. Use this skill when the user starts something new they will work on over time, says "create a project", "set up a folder for X", or asks to define the goal and structure of ongoing work. Do NOT use for one-off tasks, for wiki pages about a topic, or for scoping an existing project down to work in it.

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

Track and report on progress toward defined goals

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

Use this skill whenever a lawyer or mediator needs help analyzing a dispute for mediation purposes. This includes: reviewing case materials (pleadings, contracts, correspondence, evidence) to identify issues in dispute, summarizing each party's position and interests, conducting legal analysis of the key issues, proposing mediation strategies or settlement directions, and preparing for mediation sessions. Trigger this skill when the user mentions 'mediation', 'dispute analysis', 'settlement', 'dispute resolution', 'identify issues in dispute', 'party positions', 'mediation brief', 'case analysis for mediation', 'ADR', 'mediation preparation', 'caucus strategy', 'settlement options', or any request to analyze a conflict between two or more parties with the goal of finding resolution. Also trigger when the user uploads case files and asks for a structured breakdown of who wants what, what the core disagreements are, or how the case might settle. Even if the user doesn't explicitly say 'mediation', trigger when the context involves analyzing opposing positions in a dispute with a resolution-oriented (rather than litigation-oriented) goal.

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

Draft STRATEGY.md from a goal - read the operator's brief (goal, repo, links) plus the repo README and memory, then write a tight north-star/priorities/audience/constraints strategy.

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

Zero-config goal-to-tasks engine (the Atlas engine). Takes any goal (software, pentest, business, learning), runs adaptive discovery via brainstorming, generates a validated spec, parses into TaskMaster tasks, and hands off to execution. Use when user says "PRD", "product requirements", "I want to build", invokes /atlas, or wants task-driven development.

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

Start a safe, governed autonomous loop from a plain-language goal. Use when the user says /coco-loop, "run an autonomous loop", "keep my build green for N hours", "work on X autonomously for a while", or wants a bounded self-improving loop that proposes fixes and never commits on its own. Turns a vague goal into a readable charter the user confirms, then arms and runs the loop propose-only under the coco-loops governance framework.

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

Goal-based workflow orchestration - routes tasks to specialist agents based on user goals

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

Draft or lint a bounded long-running goal prompt with a finish line and hard limits. Use when: selected by name; one change goes to Plan.

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

Use when reviewing whether an OpenSpec change's execution goal, acceptance criteria, and implementation or verification tasks are aligned. This should trigger for requests such as Review this OpenSpec change with ATDD; Check acceptance criteria against tasks; Find acceptance criteria without task coverage; Detect tasks that diverge from the execution goal; Explain what is missing, vague, ambiguous, partial, absent, or divergent in this OpenSpec change. Part of Plinth Toolkit

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

Use when you need to create a DEVELOPER.md file for a Maven project — combining a fixed base template with dynamic sections derived from allowlisted Maven POM structure, including a Plugin Goals Reference, Maven Profiles table, and Submodules table for multi-module projects. This should trigger for requests such as Create DEVELOPER.md; Generate DEVELOPER.md; Maven project documentation; Add Maven documentation; Plugin goals reference. Part of Plinth Toolkit

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