Results for “approval-process”

Imported skill approval from langchain

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.

UAT Sign-off

Lobster

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

Establish design review gates with criteria, checklists, and approval workflows to maintain design quality.

Acceptance Eval

Interactive triage of the approval gate. Walks each block in inbox/tasks_pending.md and routes it — approve / reject / attach-as-follow-up / edit / skip. See workflows/task_tracking.md for the why.

Lobster

Use only for developer-facing products; plan adoption loops, examples, templates, community, and proof artifacts

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

issue-start 가 증거와 리포트를 게시하고 사람이 승인한 작업을 마무리합니다. 기존 증거의 완결성과 게시 상태를 확인하고, 부족하거나 바뀐 경우에만 보강·재게시한 뒤 PR 을 만듭니다. merge 는 하지 않고 issue-merge 로 넘깁니다. `$issue-end`, "이슈 마무리", "작업 종료", "승인한 작업 PR" 요청에 사용합니다.

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

Iterates through pending development plans in .cursor/plans, implementing tasks, running self-tests, reviewing code, committing locally, and moving completed plans to docs/plans/done.

Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission. Codex designs ablations from a reviewer's perspective, CC reviews feasibility and implements.

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

PASS/FAIL eval rubrics and alignment loops for Sid Orchestra (global). Use when the user says sid evals, @sid-evals, grade this, eval gate, alignment score, or wants to stop AI slop. Works in any workspace; bootstraps EVALS.md from ~/.cursor/skills/sid-orchestra/templates if missing.

Review pull requests against repository standards using automated validation and manual content review.

Use after design approval for milestone plans with executable acceptance.

PR Fleet

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.

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).

Iterate on a PR until CI passes. Use when you need to fix CI failures, address review feedback, or continuously push fixes until all checks are green. Automates the feedback-fix-push-wait cycle.

Validate whether an OSS tool is worth building through staged namespace, existing-solution, and feasibility review

Assess source acceptance coverage before MoonSpec planning.

Use only for video game projects; map genre conventions, player expectations, review complaints, and anti-patterns

阶段① 需求确认。以提问方式逐步确认需求，产出 design.md 第一章。

Decomposes an approved specification into dependency-aware waves and atomic executable tasks with exact file scope, test-first actions, verification commands, and an execution gate.

Check post-launch adoption for a published ORD package and recommend iterate, graduate, or archive

PR Review Skill

Automates the cycle of fixing CI failures, addressing PR review feedback, and pushing changes until all checks pass.

Quality Gates

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

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

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