verify-ac

Solid

QA agent: executes Epic AC (Acceptance Criteria) verification against an AC ticket or Epic. Runs all AC steps, classifies each as PASS/FAIL/MANUAL_REQUIRED/UNCERTAIN, and presents observed vs expected as pure facts (no root-cause judgement). On FAIL, surfaces human disposition gate (spec issue vs implementation drift); on PASS, it may transition the AC ticket to Done only after verification artifact/report is current and the shared verification contract resolves to PASS. Trigger: "驗 PROJ-123", "verify {TICKET}", "verify AC", "跑驗收", "AC 驗證". NOT for planning or implementation: implementation drift routes to refinement Bug source mode; spec issue routes back to refinement.

AI & Automation 4 stars 0 forks Updated 3 days ago MIT

Install

View on GitHub

Quality Score: 80/100

Stars 20%
23
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# verify-AC — Epic 驗收 QA Pipeline 的 QA agent。每次 full re-run AC steps，將 observed vs expected 當事實呈現， 不判斷 root cause。PASS 轉驗收單 Done；FAIL 進 human disposition gate。 ## Contract `verify-AC` stateless + comment-driven。它不改 code、不建 branch、不判斷 FAIL 原因、不只跑 上次 FAIL 的 AC。Implementation drift route 到 `refinement Bug source mode`；spec issue route 到 `refinement`。 Handbook exemption：verify-AC 不做 code diagnosis，預設不強制讀 repo handbook。FAIL 後由 refinement Bug source mode 讀 handbook 定位原因。 寫 verification report、V*.md lifecycle metadata 或 handoff artifact 前，必讀 `pipeline-handoff.md` § Artifact Schemas，再讀 `task-md-schema.md` 等對應 artifact-specific schema。atom ownership 邊界（V*.md envelope vs refinement.json verification authority）以 `pipeline-handoff-atom-matrix.md` 為準；SKILL 主文不複製 完整 schema 表。 ## Reference Loading | Situation | Load | |---|---| | Any run | `verify-ac-entry-flow.md`, `pipeline-handoff.md`, `workspace-config-reader.md`, `shared-defaults.md` | | Environment | `verify-ac-environment-prep.md`, `epic-folder-structure.md` | | Step execution and evidence | `verify-ac-execution-flow.md`, `evidence-upload-bundle.md` when visual/manual files need upload, `handoff-artifact.md` when cross-check needed | | JIRA report and transition | `verify-ac-reporting-flow.md`, `workspace-language-policy.md`, `external-write-gate.md`, `epic-verification-structure.md` | | FAIL disposition | `verify-ac-disposition-flow.md`, `starlight-authoring-contract.md`, `refinement Bug source mode-acfail-flow.md`, `refineme...

Details

Author
HsuanYuLee
Repository
HsuanYuLee/polaris
Created
4 months ago
Last Updated
3 days ago
Language
Shell
License
MIT

Integrates with

Jira · Productivity

Similar Skills

Semantically similar based on skill content — not just same category

Testing & QA Solid

verify-qa

Stage ④.d verify sub-workflow — gstack /qa 端到端 QA 验收 (has_ui_changes 触发, 可选 conditional; bundled verify-stage optional /qa step). schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available (gstack-qa + playwright-cli + playwright-test + webapp-testing) + 1 phase (gate ref has_ui_changes conditional)。 Triggered by slash command `/verify-qa` after `harnessed setup`.

2 Updated today
easyinplay
Data & Documents Listed

verify

Consumes an approved SpecScore Feature and produces a machine-checkable per-AC verdict report at spec/features/<feature-slug>/_verify/<sha>.md. Walks `git log` for the `Verifies:` commit-message trailer per AC, dispatches one built-in AI subagent per mapped AC (serial, not parallel), aggregates verdicts into a Markdown report opened by a grep-friendly YAML summary block, emits `verify.completed`, and transitions only to `specstudio:recap`. Applies publication policy to the report checkpoint. Trigger: "verify", "/verify", "verify this feature", "specstudio:verify", or the explicit downstream transition from `specstudio:implement`.

0 Updated 1 weeks ago
specscore
AI & Automation Solid

verify

Active QA verification - full validation before completion

15 Updated today
jmylchreest