A readiness review for deciding whether a software project can move to its next delivery phase. It checks required documents, quality conditions, and operational blockers across stages from concept to release.

Use it to validate a stage such as production, polish, or release and, when the checks pass, record the new project stage.

It makes phase transitions explicit by showing whether the project has the required evidence and whether unresolved problems still block progress.

gate-check — Skill for Claude Code by tranhieutt

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add tranhieutt/software_development_department --skill gate-check

Clone the repo

git clone --depth 1 https://github.com/tranhieutt/software_development_department

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tranhieutt/software_development_department/gate-check/github.svg)](https://agentmods.dev/skills/tranhieutt/software_development_department/gate-check)

Your own site

<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/gate-check"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/gate-check/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tranhieutt/software_development_department/gate-check"><img src="https://agentmods.dev/badge/skills/tranhieutt/software_development_department/gate-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,661 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00045	$0.02661
Opus 5	$0.00023	$0.01331
Sonnet 5	$0.00009	$0.00532
Haiku 4.5	$0.00005	$0.00266

Measured 7d ago against content hash fdda5e7d590e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

gate-check scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/gate-check/SKILL.md · 284 lines

How it starts

The opening of the file, as written. The whole thing — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Phase Gate Validation

This skill validates whether the software project is ready to advance to the next delivery phase. It checks for required artifacts, quality standards, and operational blockers.

Distinct from /project-stage-detect: That skill is diagnostic ("where are we?"). This skill is prescriptive ("are we ready to advance?" with a formal verdict).

Production Stages (7)

The project progresses through these stages:

Concept - Problem framing, product concept document
Systems Design - Requirements, workflows, architecture boundaries
Technical Setup - Stack selection, CI/CD, environments, architecture decisions
Pre-Production - Spikes, prototypes, acceptance criteria, delivery planning
Production - Feature development and integration work
Polish - Stabilization, QA hardening, performance, operational readiness
Release - Go-live prep, support readiness, rollback and communication planning

When a gate passes, write the new stage name to production/stage.txt (single line, e.g. Production). This updates the status line immediately.

1. Parse Arguments

With argument: /gate-check production - validate readiness for that specific phase
No argument: Auto-detect current stage using the same heuristics as /project-stage-detect, then validate the NEXT phase transition

2. Phase Gate Definitions

Gate: Concept -> Systems Design

Required Artifacts:

design/docs/product-concept.md exists and has content
Product pillars defined (in concept doc or design/docs/product-pillars.md)
Success metrics or launch goals captured in the concept or PRD seed notes

Quality Checks:

Product concept has been reviewed (/design-review verdict not MAJOR REVISION NEEDED)
Primary user workflow or business outcome is described and understood
Target audience and problem statement are identified

Gate: Systems Design -> Technical Setup

Read the full file on GitHub · 284 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

7d ago First seen · 284 lines · 45 tokens per session scan A fdda5e7d590e

Subscribe to this mod's changes

gate-check is a skill published in the GitHub repository tranhieutt/software_development_department (72 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 2,661 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Planning antigravity-skills brainstorming claude claude-skills harness-engineering human-in-the-loop

playwright-cli

Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…

testdino-hq/playwright-skill · 64 tokens

gate-check