skills.rest
NUMU-IO
NUMU-IOOFFICIAL
Explore all skills by this author →
WebsiteGitHub

speckit-plan-review-gate-check

Verify spec.md and plan.md are merged and clean before task generation.

2|Updated Jan 6, 2026
Search Tags:#workflow enforcement#git status#task generation#review gate#spec kit#merge check
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-plan-review-gate-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-plan-review-gate-check
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-plan-review-gate-check
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-plan-review-gate-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents implementation work from starting before the feature spec and plan have been reviewed, committed, and merged, reducing rework and enforcing a clean approval gate.

Core Features & Use Cases

  • Verifies that both spec.md and plan.md exist in the active feature directory before tasks are generated.
  • Checks whether each artifact is present on the default branch so unmerged files are correctly blocked.
  • Detects uncommitted changes to the review artifacts and stops the workflow when the working tree is dirty.
  • Supports an explicit skip-review override for cases where a user intentionally bypasses the gate.
  • Use this when coordinating a Spec Kit workflow that must enforce review sign-off before task creation.

Quick Start

Ask the assistant to check whether the feature’s spec.md and plan.md are merged and clean before allowing task generation.

Frequently Asked Questions about speckit-plan-review-gate-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I block task generation until spec and plan files are merged?▼

A review gate blocks task generation by verifying spec.md and plan.md exist on the default branch. This prevents premature implementation by ensuring feature artifacts are reviewed and merged.

How does the review gate handle uncommitted changes to spec and plan artifacts?▼

The review gate detects uncommitted changes to spec.md and plan.md and stops the workflow when the working tree is dirty. This ensures only committed and merged artifacts proceed to task generation.

Can I bypass the merge check to generate tasks without a review?▼

Yes, you can bypass the merge check using an explicit skip-review override. This allows intentional workflow bypasses for cases where users need to generate tasks without standard review sign-off.

Does this workflow enforcement work with feature-specific Spec Kit folders?▼

Yes, this workflow enforcement applies to Spec Kit repositories using feature-specific folders. It checks the active feature directory for required artifacts before allowing task generation to proceed.

Why does task generation fail when spec.md and plan.md are unmerged?▼

Task generation fails because the review gate checks whether artifacts are present on the default branch. Unmerged files are correctly blocked to prevent implementation work from starting before review sign-off.

Related Skills

Explore More Software Engineering Skills→
ApothecaryManApothecaryMan

speckit-tasks

Generate a dependency-ordered tasks.md file from spec-kit design artifacts.

Community
Advanced
joolbitsjoolbits

latitude-release-discipline

Validate branch, version, build, and tag alignment before software releases.

Community
Advanced
heyAyushhheyAyushh
3

clean-gone

Remove local git branches marked [gone] and their associated worktrees.

Community
Basic
eysenfalkeysenfalk

git-workflow

Enforce Git branch naming, commit message formats, and merge policies.

Community
Advanced