Multica Verification

Gatekeeping function: objectively check whether an artifact satisfies the acceptance criteria. Triggered by the Leader to rerun at gate points (G1/G2/G3); members can also use it for self-check. Used for design review / implementation acceptance / test-report review.

279 stars 33 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add it235/multica-best-practices --skill multica-verification
Manual install
git clone --depth 1 https://github.com/it235/multica-best-practices.git /tmp/multica-best-practices
mkdir -p ~/.claude/skills
cp -r /tmp/multica-best-practices/templates/en_US/skills/leader/multica-verification ~/.claude/skills/multica-verification

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Verification (gatekeeping)

## What this is

Verification is a **function**, not a role. It answers one question:

> For every acceptance criterion, is there objective evidence that it is satisfied?

The key: verification must be an **objectively decidable action** (run commands, read output, map item by item), not "I feel it's fine."
It doesn't rely on anyone's character — it relies on the evidence itself. Whoever runs it, the result is the same.

## Who executes it

- **Gatekeeping**: the **Leader** triggers this Skill at the gate points (G1 / G2 / G3) and reruns independently. The Leader produces no artifacts, so it's naturally a third party.
- **Self-check**: after finishing, a producer may first run this Skill to self-verify (pasting the command output), but self-check is not gatekeeping — gatekeeping must be rerun by a non-producer.

> The gate issuer must be a different party from the gated. Authors cannot stamp "PASS" on themselves.

## Process

1. Read the Issue's acceptance criteria.
2. Map every criterion to evidence (which test / which command / which output).
3. **Rerun** the verification commands; don't cite someone else's described output.
4. Check the change scope: does the diff only touch this requirement?
5. Give PASS / FAIL for each criterion.

## Result

**PASS** — every criterion has sufficient evidence.

**FAIL** — at least one criterion unmet. Must provide: the problem, why it matters, where, and the fix direction.
Read the full skill on GitHub

Details

Skill name
multica-verification
Path
templates/en_US/skills/leader/multica-verification/SKILL.md
License
MIT
Repo updated
4 November 2026

FAQ

What does the Multica Verification skill do?

Gatekeeping function: objectively check whether an artifact satisfies the acceptance criteria. Triggered by the Leader to rerun at gate points (G1/G2/G3); members can also use it for self-check. Used for design review / implementation acceptance / test-report review.

How do I install the Multica Verification skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-verification. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Multica Verification popular?

It lives in it235/multica-best-practices, which has 279 GitHub stars and 33 forks.

Related skills

Multica Artifact Architect

279

it235/multica-best-practices

Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.

Testing & QA33

Multica Artifact Architect

279

it235/multica-best-practices

架构师产物薄编排:校验设计草稿规范,落地时只调 multica-platform-confluence + multica-platform-jira。用于 @Architect 发布设计文档。

Other33

Multica Artifact Backend

279

it235/multica-best-practices

Land API contract artifacts to the API collaboration platform (default Apifox). Used by @BackendDev to upload API contract for downstream frontend / test consumption. Swappable platform.

Software Development33

TDD Methodoly Expert

194

thedaviddias/skill-check

Use when implementing features or fixing bugs with strict Test-Driven Development (TDD). Activate for coding tasks that require new functionality, refactoring, or comprehensive test coverage, especially when the user mentions TDD or Test Driven Development.

Testing & QA

Multica Test T3 UI Automation

279

it235/multica-best-practices

T3 UI 自动化:pytest+Playwright,1 功能用例 = 1 个 e2e 测试;路径读 MULTICA.md §2;在 deploy URL 执行。

Testing & QA33

Specx Project Tooling

198

maksimzayats/specx

Add strict Python project tooling for a specx service. Use when creating or updating `pyproject.toml`, `uv` dependency groups and lock checks, Ruff formatting and linting, mypy strict mode, pytest and HTTPX2 test configuration, Makefile commands, root `AGENTS.md` command guidance, or CI-like local guardrails.

Testing & QA33

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.