From dev-workflow-skills
Use when a workflow stage is about to be marked complete and outputs, document state, or command-backed evidence must be checked first, including 完成前核对/交付证据校验/阶段完成验收
How this skill is triggered — by the user, by Claude, or both
Slash command
/dev-workflow-skills:completion-verifierThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Completion Verifier is the final evidence gate before any stage, document, or integration batch claims done. It checks the required outputs, confirms command-backed proof, validates metadata and progress alignment, and blocks optimistic completion claims.
Completion Verifier is the final evidence gate before any stage, document, or integration batch claims done. It checks the required outputs, confirms command-backed proof, validates metadata and progress alignment, and blocks optimistic completion claims.
Use these support assets for repeatable completion checks:
references/evidence-checklist.mdreferences/frontmatter-and-progress-checks.mdreferences/boundary-examples.mdreferences/pressure-test-prompts.md (for skill audits or revisions)templates/verification-report.mdRead skills/workflow-protocol/SKILL.md, then repository-root workflow-project.yaml. Resolve paths.progress, then read the progress dashboard at paths.progress. Before accepting a completion claim, use references/evidence-checklist.md and scan references/boundary-examples.md if ownership of the missing work is unclear.
Use this skill when:
paths.progress is about to be updated to reflect completionDo not use this skill to do the missing work itself or to waive evidence because progress already claims success.
paths.progresspaths.changes_dir, blocked gates, or linked upstream/downstream documents when relevantpaths.progress_history for audit trailreferences/evidence-checklist.md to confirm every artifact and command proof is present.references/frontmatter-and-progress-checks.md when document metadata or progress rows are in scope.templates/verification-report.md, citing evidence instead of assertions.workflow-protocol: advance dashboard stage status and append a PASS entry to paths.progress_history only after PASS. On NOT PASS, do not change the dashboard, but still append a NOT PASS entry to paths.progress_history recording the blockers so the audit trail captures failed verification attempts.workflow-project.yaml, never against literal path strings.paths.progress as downstream bookkeeping that must match verified reality, not as proof by itself.paths.progress_history with blocker details.Guides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.
npx claudepluginhub yxzyzh08/dev-workflow-skills --plugin dev-workflow-skills