286건 · 관련도순
PM-mode brainstorm helper. Captures the requirement via Socratic dialogue before any entry phase (`/intake`, `/spec`, `/tdd`) drafts its artifact. Stage 0 skip-check, Stage 1 gap-analysis, Stage 2 probe-loop, Stage 3 confirm-and-persist. Output lives at `docs/brief/<slug>.md`. Never proposes solutions — Stage 2 dialogue discipline is structurally enforced via `discipline.mjs`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
/cs:ai-act-readiness <system> — EU AI Act 6-question forcing interrogation. Use during AI-system intake, before EU deployment, or during annual compliance refresh as Article 113 obligations phase in (2025-02-02 / 2025-08-02 / 2026-08-02 / 2027-08-02).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
當使用者要為新客戶規劃或撰寫全新的 Brand Guideline、品牌手冊、視覺識別規範時使用。互動教練模式：一次只問一題完成 intake，全部問完後產出由知識圖譜推理驅動的 Plan 供確認，使用者確認後才 Build 並寫入 clients/ 下的 blueprint、index.yaml 與 note.md 初稿。Plan 階段以 Design Strategy 推理鏈（產業 → 品牌類型 → 商業問題 → 匹配決策卡 → 架構）運作，並引用 references/research/decision_patterns.yaml、contexts、modules、archetypes、module_graph 與 references/docs/*.profile.yaml 的證據。本 skill 亦涵蓋兩個延伸能力（見 references/）：分析既有 guideline PDF（design-guideline-researcher）、把分析升級成決策卡（design-strategy-extractor）。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Before adding/installing any dependency the agent named — verify the package exists (slopsquatting: ~1 in 5 AI suggestions are hallucinated), isn't typo-adjacent, is pinned + locked, and CVE-scanned
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when consolidating session signals into curated memory — four-phase loop ORIENT → GATHER → CONSOLIDATE → PRUNE. Triggers on 'mine my sessions', 'consolidate memory', 'review intake signals'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Project-level WeChat article drafting workflow for turning source materials, repo intakes, product notes, screenshots, or existing markdown into a publishable Chinese公众号 draft. Use for writing, rewriting, evidence-gating, title options, platform adaptation, and image planning before optional publishing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
ヒアリング結果に図解を配置したいとき、Mermaid 12 と独自 SVG 8 から各セクションに 1〜3 図を選択して visuals.json と PNG を生成したいときに使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
外部連携カタログを参照して候補を選択肢化したいとき、purpose.json を基に options.json を生成したいときに使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
harness-creator / plugin-dev-planner への引き渡しモードを判定したいとき、summary.json から A/B/C/D/E/P のいずれかを決定論的に確定したいときに使う。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Track Two / internal innovation system for running small, fast experiments outside the core business. Runs in three modes — Diagnostic for designing the full Protoloop from scratch (intake channels, loop structure, team, exit paths), Review for running the monthly heartbeat meeting (loop-by-loop decisions, forward-loading, portfolio health), and Alert Triggers for defining tripwires that protect, feed, and maintain momentum in the system. Updates company-context.md after every run. Triggers on questions about innovation pipelines, intrapreneurship, Track Two strategy, experimentation systems, handling ideas that don't fit the core business, or building systematic exploration alongside exploitation. Based on 20 years of practice by Eterdis (eterdis.com).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
/cs:ai-act-readiness <system> — EU AI Act 6-question forcing interrogation. Use during AI-system intake, before EU deployment, or during annual compliance refresh as Article 113 obligations phase in (2025-02-02 / 2025-08-02 / 2026-08-02 / 2027-08-02).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews one employee software request (tool, purpose, users, data handled, cost, urgency) against the approved-tools list and the policies the user provides and returns a draft review for the reviewer: match state on the list with the row quoted, approved tools the list itself describes as covering the same need, policy clauses that bear on the request with quoted text, questions for the requester and the reviewer, and one suggested decision with its basis. Never approves, procures, installs or adds a tool to the list. Use when the user asks to "review this software request", "is this tool on the approved list", "check this request against our software policy", "do we already have something approved that does this" or "prepare the decision note for this tool request". Do not use for a full vendor security assessment, use vendor-risk-screening-brief instead; for sorting mixed requests, use request-intake-triage. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Checks an extracted PFD register as a process model and returns findings and unknowns only: connectivity closure, stream numbering, presence of design conditions, equipment duty text, phase and service labels, package and off-sheet scope, boundaries, operating cases, and agreement between the drawing and attached process documents, then holds at gate G2. Creates no design values. Use when the user asks to "check the process model", "verify connectivity" or "is the PFD ready for enrichment" after gate G1 and before enrichment. Do not use for extraction from the drawing, use pfd-intake-and-extraction instead; do not use to propose lines or instruments, use piping-enrichment. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds a DRAFT interface register between disciplines or parties from meeting notes, action lists and drawings or document lists: one row per interface with the requesting and providing party, the information needed, the related document number, the need-by date with its source, the status as minuted and a quoted source, plus UNKNOWN and questions where the notes are silent. Never sets a date, rates priority, assigns ownership beyond what the notes state or closes an interface. Use when the user asks to "build an interface register from these minutes", "list the interfaces between piping and civil", "who owes what to whom on this package", "update the interface register from this week's meeting" or "turn these action items into an interface list". Do not use for recording a design or document change raised in a meeting, use management-of-change-intake instead. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reads a process flow diagram (image, PDF or native export) with its job header and returns a provenance-tagged extraction register: equipment, streams, tags, connectivity, instruments already shown, notes and legends, connectivity findings and an explicit UNKNOWN list, then holds at gate G1. Extracts and records only; never enriches, tags or proposes. Use when the user asks to "start a PFD to P&ID job", "read in the attached PFD", "extract the equipment and streams from this PFD" or "read this PFD into a register". Do not use for checking the model, use process-model-check instead; do not use to propose lines, instruments or tags, use piping-enrichment or instrumentation-and-control-enrichment after gate G2. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Triages a batch of customer support tickets (helpdesk export, shared mailbox, chat transcripts, web forms) into one row per ticket with category, urgency graded on the evidence in the ticket, suggested next action and owner, plus a DRAFT customer reply for every ticket that needs one, returned as one Markdown pack. Use when the user asks to "triage these tickets", "sort the support queue", "what needs an answer first", "categorise this backlog", "draft replies for these tickets" or "build today's queue review". Do not use for internal requests from colleagues, use request-intake-triage instead; for one long thread that needs handing over, use escalation-summary; for a personal mailbox, use inbox-triage. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
新しいソフトウェアプロジェクトのオンボーディング標準手順：機能分析、コード品質レビュー、オンボーディングチェックリスト、タスク作成。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Стандартная процедура онбординга новых программных проектов: анализ функций, проверка качества кода, чек-лист и создание задач.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Procedimiento estándar para la incorporación de nuevos proyectos de software: análisis de funciones, revisión de calidad de código, lista de verificación e integración de tareas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
新软件项目入职的标准流程：功能分析、代码质量审查、入职检查清单和任务创建。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Standard procedure for onboarding new software projects: Feature analysis, code quality review, onboarding checklist, and task creation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Single-mainline governance for deployless repositories. Use after a deployless audit when a repo needs trunk-based branch rules, branch protection, contribution guidance, review gates, merge queue policy, AI PR intake rules, or agent-ready mainline practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.