Agent skill · Security

verification-gates

Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.

Rohit Ghumare73,165★ · +3,601/wk · 3 repos on radarProfile →
codexcursorApache-2.0
Install
npx skills add rohitg00/skillkit --skill verification-gates --agent codex

Same command for any agent — swap --agent for claude-code, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 7 KB
Bundled scripts: none
Version: 1.0.0
Path: packages/core/src/methodology/packs/planning/verification-gates/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,422
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Verification Gates You are implementing verification gates - explicit checkpoints where work is validated before proceeding. This prevents cascading errors and ensures quality at each phase. ## Core Principle **Never proceed to the next phase with unverified assumptions from the previous phase.** A verification gate is a deliberate pause to confirm that prerequisites are met before continuing. ## Standard Verification Gates ### Gate 1: Requirements Verification Before starting design: - [ ] All requirements are documented and clear - [ ] Ambiguities have been resolved with stakeholders - [ ] Non-requirements are explicitly stated - [ ] Acceptance criteria are defined - [ ] Edge cases are identified **Actions:** 1. Review requirements document 2. Identify any unclear items 3. Get explicit confirmation on ambiguous points 4. Document answers ### Gate 2: Design Verification Before starting implementation: - [ ] Design addresses all requirements - [ ] Technical approach is validated - [ ] Interfaces are defined - [ ] Data model is complete - [ ] Error handling is planned - [ ] Design has been reviewed (self or peer) **Actions:** 1. Walk through design against requirements 2. Review w

What's inside
Steps it walks through
  1. Core Principle
  2. Standard Verification Gates
  3. Gate 1: Requirements Verification
  4. Gate 2: Design Verification
  5. Gate 3: Implementation Verification
  6. Gate 4: Integration Verification
  7. Gate 5: Deployment Verification
  8. Gate Types
  9. Automated Gates
  10. Manual Gates
  11. Conditional Gates
  12. Implementing Gates
  13. In Your Workflow
  14. Gate Documentation Template
More from skillkit
All skills →
About this skill
What does the verification-gates skill do?

Creates explicit validation checkpoints (verification gates) between project phases to catch errors early and ensure quality before proceeding. Use when the user asks about quality gates, milestone checks, phase transitions, approval steps, go/no-go decision points, or preventing cascading errors across a multi-step workflow. Produces acceptance criteria checklists, automated CI gate configurations, manual sign-off requirements, and conditional review rules for scenarios such as security changes, API changes, or database migrations.

How do I install it?

Run `npx skills add rohitg00/skillkit --skill verification-gates --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From rohitg00/skillkit, a repository with 1,422 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going