49건 · 관련도순
Commercial policy: the governance framework defining what terms sales can offer and what triggers approval. Use when authoring a policy charter, defining discount/payment/liability rules, auditing deals, or generating a regional policy.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Verification-first methodology for the post-WWII tribunals: the IMT at Nuremberg, the twelve Nuremberg Military Tribunals, and the IMTFE at Tokyo. Citations are verified against the official records (Blue/Green Series, Pritchard-Zaide) and the digital archives (Avalon, Harvard NTP, UVA IMTFE). Guards the four classic traps (IMT vs NMT; Nuremberg vs Tokyo; Charter article numbers; majority judgment vs separate opinions, e.g. the Pal dissent). Research aid, not legal advice. Part of the open-source "Skills for International Justice" library — methodology: github.com/jeannesulzer/international-criminal-tribunals-skills
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assess whether a Fundamental Rights Impact Assessment (FRIA) is required under Article 27 EU AI Act, and structure or draft that assessment for a specific high-risk AI deployment. Covers deployer scope gating (public bodies and private entities providing public services), affected group mapping, Charter rights analysis, proportionality, safeguards evaluation, residual risk, DPIA/FRIA cross-referencing under the amended Article 27(4), the unconditional notification duty under Article 27(3), and DACH-specific considerations. Use when asked about FRIA obligations, Article 27 scope, fundamental rights and AI, or deployer assessment duties.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MANUAL-ONLY — load solely when the human owner types `/pl`, uses `$pl`, or asks you to act as the Project Lead (PL). Supervise one project lane and its executor agents. A charter or dispatch means: you are an EXECUTOR, not the PL.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
MANUAL-ONLY: load solely when the human owner types `/cos`, uses `$cos`, or asks you to act as the Chief of Staff (COS). The COS is the one agent the owner talks to; it coordinates the owner and the per-project Project Leads (PLs). A task card, charter, or dispatch makes you an executor, not COS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Sets up how you and your team build and work with AI agents, and produces an Agent Workflow Charter (agent lanes, plan-mode loop, autonomy ladder with promotion criteria, rules file, review policy, security rules, rollout plan). Use when you ask 'how should we work with Claude Code / Codex / Cursor', 'how many agents should I run', 'should the agent be autonomous', 'plan mode', 'CLAUDE.md', 'AI-native team', 'roll out AI to my team', or 'my agent keeps screwing up'. Draws on 110 Lenny's Podcast guests incl. Claire Vo, Boris Cherny and Aishwarya Naresh Reganti.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review factory evidence and propose tighter or looser constraints without editing the charter. Use for a periodic constraint review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Show the factory control room from live GitHub labels, open PRs, recent run records, gate health, and charter limits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate PDFs, resumes, CVs, letters, slide decks, portfolios, one-pagers, white papers, and professional documents. Use when user asks to create a PDF, make a resume, write a letter, design slides, format a document, typeset a report, build a portfolio, make a presentation, or create a one-pager. Warm parchment, ink-blue accent, serif-led hierarchy. CN uses TsangerJinKai02, EN uses Charter, JA uses YuMincho (best-effort). Triggers on Chinese: "做 PDF / 排版 / 一页纸 / 白皮书 / 作品集 / 简历 / PPT / slides". Do NOT use for code formatting, data charts, or wireframes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Act as a project-management copilot (PM/PMO) for the delivery loop: charters, plans and schedules, estimates, risk registers, status reports, scope changes, stakeholder communication, meeting actions, lessons learned, and portfolio roll-ups, in a per-project `_project/` workspace. Use whenever the user wants to start, plan, track, rescue, or report on a project: "kick off this project", "make a project plan / timeline / WBS", "what date can I commit to", "build a risk register", "run a pre-mortem", "write the weekly status report", "the deadline slipped, what now", "turn this meeting into action items", "review my project portfolio", in any language ("quản lý dự án", "gestion de projet", "プロジェクト管理", "项目管理"), even when they never say "project management". Also use whenever a `_project/` directory exists and the user asks about schedule, deadline, risk, status, scope, budget, or stakeholders. Not for what to build (product-manager) or company-level bets (strategy-board).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a project status report by reading existing artifacts (charter, backlog, sprint plan, WBS), calculating metrics, identifying blockers, and summarizing progress with RAG indicators for schedule, scope, budget, and quality. Use at the end of a sprint or reporting period, when stakeholders request a health update, before steering committee or governance meetings, or when a new blocker or risk materializes mid-project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply LaReine's quality bar when judging an answer, an artifact or a method.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Stand up or reset project governance for new, complex, or troubled initiatives using PMBOK 8 value delivery, OKR alignment, and Scrum or SAFe cadence choices where relevant. Use when a project needs a charter, decision rights, stakeholder map, RAID logic, escalation path, or reporting rhythm. Do not use for simple task lists, isolated sprint notes, or code implementation planning.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Spin up a new loop (domain) in a file-based knowledge base — bootstrap the substrate if it's missing, gather the loop's charter, scaffold domains/<loop>/README.md, then do ONE real test run and record it in the loop's Timeline and LOG.md. Use when the user says "set up a new loop", "create a domain", "start a new beat/workstream", or names a recurring job they want the agent to own.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, implement, or audit a Change Advisory Board (CAB) process for Salesforce deployments: change classification (standard, normal, emergency), required approvals, deployment gate sequencing, and integration with external ITSM tooling. NOT for scoring how risky one release is - use admin/deployment-risk-assessment. NOT for executing or troubleshooting the deployment itself - use admin/change-management-and-deployment. Also covers: the CAB charter (membership, quorum, decision rights), the CAB decision record artefact and its linter, the change classification matrix, the deployOptions a CAB decision pins (checkOnly, testLevel, rollbackOnError, ignoreWarnings, runTests), the 10-day quick-deploy validity window, the deploy-window vs freeze-register check, and the emergency (ECAB) path with its mandatory retrospective.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Team-wide charter and history optimization through skill extraction
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Establish or audit an agent-operated repository's quality contract or recurring stewardship friction. Skip routine repairs with a known owner and native check. Use for charter/docs ownership, validation gates, evidence paths, maturity proof, consumer/producer boundaries, command-surface evolution, or a repo ecology pass to decide what should be compressed, merged, retired, or moved to checks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds a DRAFT stakeholder map for one project from the charter, organisation chart, RACI, governance terms, steering minutes, meeting notes and messages the user provides: a stakeholder register, interest and influence ratings each with its stated basis, stance as evidenced by a verbatim fragment with source and date, gaps, and a proposed engagement plan per stakeholder, every line traced to a source and every missing fact marked UNKNOWN. Use when the user asks to "build the stakeholder map", "who are the stakeholders on this project", "map interest and influence", "where does each stakeholder stand", "draft the stakeholder engagement plan" or "refresh the stakeholder register". Do not use for a customer account's stakeholders, use account-plan-builder instead; for a one-page brief before one meeting, use meeting-prep-onepager; for logging decisions and risks against the project, use project-status-tracker. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This skill should be used when creating comprehensive project plans for system development or implementation projects. Use this skill when you need to create Project Charters, Project Plans, WBS, Gantt Charts, RACI matrices, Risk analysis, or other PMBOK-aligned project management artifacts. Outputs are in Markdown format with Mermaid diagrams for visualizations. Leverages comprehensive PM knowledge base in references/ directory (544KB, 11 files) including PMBOK standards, Software/SaaS best practices, IT industry guidance, and specialized PM methodologies.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review factory evidence and propose tighter or looser constraints without editing the charter. Use for a periodic constraint review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Show the factory control room from live GitHub labels, open PRs, recent run records, gate health, and charter limits.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Warm editorial, print-leaning document design system — parchment background, single ink-blue accent, serif-led hierarchy (LXGW WenKai for Chinese, Charter for English). For résumés, reports, white papers, letters, and editorial reading pages that should feel authored and published. Not a product-UI / component system.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Execute an explicitly authorized exploratory charter and record notes, findings, evidence, and follow-up without claiming false coverage.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.