developer-gate

Standardize developer decision points with AskUserQuestion consent gates.

Updated Feb 22, 2026
One-click install
npx skills add https://github.com/YangTaeyoung/go-clean-arch-toolkit --skill developer-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: developer-gate
Source: https://github.com/YangTaeyoung/go-clean-arch-toolkit/tree/main/skills/developer-gate
Command: npx skills add https://github.com/YangTaeyoung/go-clean-arch-toolkit --skill developer-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures critical development decisions are made with explicit developer approval, preventing unauthorized changes and maintaining code quality.

Core Features & Use Cases

  • Decision Gates: Implements standardized checkpoints for crucial steps like spec finalization, implementation start, and review feedback incorporation.
  • Guided Workflows: Uses AskUserQuestion to present clear options and gather developer consent or specific instructions.
  • Use Case: Before starting code implementation for a new feature, the /develop command will present a detailed task list and implementation plan for the developer to approve, ensuring alignment and preventing wasted effort.

Quick Start

Use the developer-gate skill to approve the implementation plan for issue PD-210.

Frequently Asked Questions about developer-gate

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

FAQPage Schema
How do I enforce explicit developer approval before starting code implementation?

You can enforce explicit developer approval by implementing decision gates that present an implementation plan and gather consent before code implementation starts, preventing unauthorized changes and wasted effort.

What is a decision gate in the software development workflow?

A decision gate is a standardized checkpoint at critical workflow junctures like issue specification, implementation approval, and review feedback incorporation that requires explicit developer consent before proceeding.

How do I standardize developer decision-making for issue specification and review feedback?

Standardize developer decision-making by applying a common gate pattern that uses AskUserQuestion to present clear options and gather specific instructions for issue specification and review feedback.

Can I use a gate pattern to manage review feedback incorporation in my development workflow?

Yes, you can use a gate pattern to manage review feedback incorporation by presenting clear options and requiring explicit developer consent before applying any review changes to maintain code quality.

What is the best way to prevent unauthorized changes during feature development?

The best way to prevent unauthorized changes is to require explicit developer consent at critical junctures using decision gates, ensuring actions like implementation start and review incorporation are approved.