598건 · 관련도순
Plan work across several AI agents by defining task owners, deliverables, dependencies, and acceptance criteria. Choose a finite workflow or repeated improvement cycles, then review results before allowing dependent tasks to proceed.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare conference slides, academic posters, and research promotion content after paper acceptance. The skill guides talk structure, visual layout, timing practice, anticipated questions, and drafts for Twitter/X, LinkedIn, and a broader-audience blog post.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Turn a plain language feature request into spec.md with user stories, testable requirements, and acceptance criteria. Create a feature branch and a separate quality checklist, documenting assumptions and clarifying important gaps before planning begins.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
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 this skill when a company needs a written risk assessment method before it builds or rescores a register, or when the current method produces registers where everything scores 3. Triggers: "write our risk methodology", "define likelihood and impact scales", "what is our risk appetite", "risk acceptance criteria", "who can accept a risk", "our auditor says the method is not repeatable", "risk matrix for our ISMS". Drafts a short method with likelihood and impact anchors in the company's own money, hours and records, a scoring rule, an acceptance threshold with an authority ladder, reassessment triggers, and a calibration test on five sample risks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write acceptance speeches for awards and honors. TRIGGERS - Use when user needs help with acceptance-speech related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write clear acceptance criteria for features. TRIGGERS - Use when user needs help with acceptance-criteria related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate a User Acceptance Testing plan with scenarios and sign-off criteria. Use when the user says "UAT plan", "acceptance testing", "user testing plan", "how do we test this with users", "test scenarios for business validation", "sign-off criteria", "go/no-go for release", "acceptance test cases", "validate with stakeholders" - even if they don't explicitly say "UAT".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when authoring INVEST-compliant Salesforce user stories from gathered requirements: shaping the As-A/I-Want/So-That stem, writing Given-When-Then acceptance criteria, sizing complexity (S/M/L/XL), splitting stories that are too large for a sprint, and emitting handoff metadata that names the next downstream agent. Trigger keywords: user story, INVEST, story splitting, story sizing, As-A I-Want So-That, story handoff, recommended_agents, backlog item shape. NOT for requirements elicitation or stakeholder interviews (use admin/requirements-gathering-for-sf). NOT for the Given-When-Then technique itself in depth (use admin/acceptance-criteria-given-when-then). NOT for UAT test case design (use admin/uat-test-case-design). NOT for backlog prioritization (use admin/moscow-prioritization-for-sf-backlog).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when designing the human-executable UAT test cases that prove a Salesforce feature works for a specific persona — the per-persona scripts with preconditions, data setup, permission setup, ordered steps, and pass/fail evidence that close out an RTM row. Trigger keywords: UAT test case salesforce, user acceptance test script salesforce, manual test salesforce feature, UAT script per persona, UAT precondition data setup, UAT permission set assignment for testing, negative path UAT case. NOT for high-level UAT planning, defect classification, regression strategy, or sign-off (use admin/uat-and-acceptance-criteria). NOT for the Given/When/Then technique used to write the AC the case is derived from (use admin/acceptance-criteria-given-when-then). NOT for Apex test method generation (use agents/test-class-generator). NOT for test data factory patterns (use templates/apex/tests/TestDataFactory.cls). NOT for performance or load testing.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write acceptance speeches for awards and honors. TRIGGERS - Use when user needs help with acceptance-speech related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write clear acceptance criteria for features. TRIGGERS - Use when user needs help with acceptance-criteria related tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
운영자가 설정한 Team 서버의 업데이트를 지정된 Night Watch 담당자를 통해 조율합니다. 기존 업데이트 체계의 검증과 복구 결과를 확인하고 정식 승인까지 추적합니다.
대규모 기능의 설계 제안을 의존 관계와 통과 기준이 있는 작업으로 나눕니다. 여러 에이전트의 조사, 구현, 테스트, 검토부터 통합과 최종 검증까지 정리합니다.
Kanban에서 구현 담당자가 넘긴 결과물을 독립적으로 검증합니다. 인수 조건과 테스트 증거를 대조해 승인, 수정 요청 또는 사람의 판단을 구하는 상위 전달을 기록합니다.
기존 구조를 활용해 새 기능이나 외부 연동을 필요한 범위에서 구현합니다. 완료 조건과 제외 범위를 먼저 정하고 관련 계층을 연결해 전체 동작을 완성합니다.
Archify의 실제 도표와 에이전트 작업 기록으로 정확성·가독성·완료 시간을 평가합니다. 변경 전후를 비교해 배치, 연결선 경로와 작성 절차를 개선합니다.
Review a completed epic, a group of related development tasks, against its plans, code changes, and commits. Produce a retrospective with evidence-backed findings, follow-up actions, and a decision on whether to accept the work.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Implement approved development stories and code changes with Amelia, a senior software engineer persona. Follow a test-first process: write a failing test, make it pass, then improve the code while checking every acceptance criterion.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Run repeatable tests of Cherry Studio’s key workflows with Playwright, which checks application behavior through automated interactions. Collect results on macOS and Windows and produce English reports for release acceptance or development validation.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Guide a scoped coding task through specification, implementation, and review. Set acceptance criteria, verification checks, iteration limits, and approval gates, then correct identified gaps until the requirements pass or a stopping condition is reached.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Trace how JWT, JWS, and JWE tokens become accepted identities or privileges in a CTF sandbox. Examine headers, key selection, and claims, the token's attributes, then preserve a minimal reproducible path demonstrating validation confusion.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Trace forced authentication and relay chains in a CTF sandbox. Identify what triggers authentication, which service accepts the forwarded identity, and what privilege or artifact results, while distinguishing captured authentication from a successfully accepted relay.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.