Results for “human-approval”

Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Imported skill approval from langchain

UAT Sign-off

Design, review, or troubleshoot Salesforce Approval Processes, covering entry criteria, approver routing, record locking, and recall behavior.

Iterate on a pull request until actionable CI checks pass and high/medium review feedback is addressed, stopping at human approval, draft, or merge gates.

Use when designing or auditing AI product human-in-the-loop — write approval, proposal accept/reject, action confirm, spend caps, run detail, memory capture, or any AI action with irreversible blast radius. Trigger on confirmation UX, undo, cost-before-act, show-the-plan, citations, or keeping the owner in control.

Lobster

Lobster

Give a decisive, project-grounded point of view in the subject's own shape: a graded verdict on an external-adoption question, a holistic take on a document, or a position on a user-supplied approach set. Use for a solo POV, a mid-session second opinion, a named-peer cross-check, any request to consult other models or reconcile their opinions, an `oracle` panel, or a correction-cost-gated proactive cross-check offer. Not for findings review (use ce-doc-review), neutral explainers, or generating options (use ce-ideate or ce-brainstorm).

去除或避免文本中的 AI 味。用于用户强制调用本 Skill，或写作/改写时提到“不要有 AI 味”“不要太假”“真情实感”“有人感”，或对已有文本/上一轮输出反馈“太像 AI”“太空泛”“太模板”“太官方”“不像我说的”等场景。

Acceptance-test newly added features using browser automation, happy-path flows, screenshots, UX notes, and a written report.

Consensus planning entrypoint that auto-gates vague ralph/autopilot/team requests before execution

Apple Human Interface Guidelines interaction and UX patterns.

Write, read, and validate HUML documents, converting between YAML/JSON/TOML and HUML for human-readable configuration files.

Walk a business/UAT approver through a plain-language demo of a verified feature and capture business acceptance signoff.

Acceptance Eval

Create informed consent forms for procedures. TRIGGERS - Use when user needs help with consent-form related tasks.

Structures a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.

Provides Apple Human Interface Guidelines for designing input methods across Apple platforms, including gestures, Apple Pencil, keyboards, game controllers, pointers, Digital Crown, eye tracking, spatial interactions, focus systems, remotes, motion sensors, and nearby interactions.

Simulator.Company access-control specialist — who can view/modify/remove/sign/execute an object (actor, form, account, template, tree layer). Use when the user wants to share or unshare an object, grant or revoke permissions, list who has access, or bulk-share. Activate when the user says "share this with", "give access to", "grant permission", "revoke access", "who can see/edit this", "set permissions", "make read-only", "поділись з", "надай доступ", "забери доступ", "хто має доступ", "права доступу", "дай доступ", "открой доступ", "отзови доступ", "кто имеет доступ", "права доступа". Also activate when a tool fails because the caller has NO access to an object — "request access", "I can't see this actor", "access denied", "403", "no permission", "запроси доступ", "немає доступу", "немає прав", "відмовлено в доступі", "запроси доступ", "нет доступа", "доступ запрещён". For the object's own data use the domain skill (`simulator-actors` / `simulator-forms` / `simulator-finance`).

Guides open source license selection, comparison, compliance review, and drafting of LICENSE/NOTICE files using canonical texts.

Live application prep for Heath Barnett. Given a role name or a job application URL, renders the real application form, reads every field including the bespoke custom questions, drafts each answer grounded in Heath's receipts and resume master, and returns a copy-paste breakdown plus the submit window in the hiring manager's timezone. Built for the hot window: Heath is at the keyboard, this gets him ready to paste and submit in minutes. Trigger on "prep [company/role]", "apply prep", "get me ready to apply to [company]", "prep my application for [role]", "extract the questions for [role]", "what does the [company] application ask", or Heath pasting an application URL with intent to apply. Never submits the form. Never fabricates. No em dashes.

Assess source acceptance coverage before MoonSpec planning.

Alias for $plan --consensus

Create informed consent forms for procedures. TRIGGERS - Use when user needs help with consent-form related tasks.

Universal opt-out mechanism implementation across US state privacy laws. Covers Global Privacy Control (GPC) signal technical implementation, state-by-state recognition requirements, browser detection methods, authenticated vs unauthenticated handling, and compliance testing.

Surfaces Han's shared standard for explaining technical work to a reader who will not implement it into the calling skill's own context, so the caller writes its escalations, confirmation turns, and stops as a concrete outcome the reader could observe rather than as a mechanism. Use when a skill is about to ask a person a question, stop for an input, or explain a technical consequence to someone who will not open the code. Governs what a run says to a person in a turn, where readability-guidance governs the shape of a written deliverable. Runs in the caller's context and hands control straight back; it does not produce a deliverable of its own, rewrite anything, or judge the caller's work. Carries guidance only and adds no self-check step.

Humanizer

Guide human-centered design processes using empathy-driven methodologies. Use when the user says "lets run design thinking" or "I want to apply design thinking"

Use to prove that a support process, policy or script change actually took effect — when, for whom, and whether behaviour followed — rather than that it was approved. Trigger for "prove we made that change", "when did this policy actually change", "did the team adopt the new process", evidencing remediation, "we told everyone" claims, or a change that was signed off and never landed.

Defines a gated Research-Plan-TDD-Review-Commit pipeline for orchestrating feature development, defect fixes, and refactoring tasks through composable phases and human approval gates.