sr-design-gate

Name: sr-design-gate
Availability: InStock
Author: tanghuo

Convert rough ideas into repo-grounded design artifacts for sr-* workflows.

Updated Jun 15, 2026

Search Tags:#design #product development #risk management #workflows #repo truth

Ready to run

npx skills add https://github.com/tanghuo/th-skill --skill sr-design-gate

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sr-design-gate
Source: https://github.com/tanghuo/th-skill/tree/main/skills/sr-design-gate
Command: npx skills add https://github.com/tanghuo/th-skill --skill sr-design-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in turning rough ideas, product questions, or risky change requests into explicit, repo-grounded design artifacts before implementation starts, reducing rework and ensuring clarity in business semantics, source-of-truth ownership, contracts, and more.

Core Features & Use Cases

Design Clarification: Helps clarify intent, inspect current truth, compare approaches, and write a design.
Workflow Integration: Acts as the first stage of the local sr-* workflow, including sr-review, sr-plan-split, sr-task-runner, and sr-task-loop.
Use Case: Before starting on a new feature or behavior change, use this Skill to create a detailed design artifact that outlines the goals, non-goals, affected modules, data model, contracts, and more.

Quick Start

To initiate the design process, use the command: sr-design-gate

Frequently Asked Questions about sr-design-gate

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

FAQPage Schema

How do I turn rough product ideas into implementation-ready design artifacts?▼

To turn rough product ideas into implementation-ready design artifacts, this Skill clarifies intent, inspects current repo truth, compares approaches, and writes detailed designs outlining goals, non-goals, and data models.

When do I need to create a design artifact before starting feature development?▼

You need to create a design artifact before starting feature development when handling risky change requests or new behaviors, ensuring business semantics and source-of-truth ownership are clear to reduce rework.

How do I manage design risk and complexity for new product change requests?▼

To manage design risk and complexity for product change requests, the Skill requires repo truth inspection, user confirmation, and design validation to handle various risk levels and design complexities explicitly.

What is the best way to integrate design clarification into a local development workflow?▼

The best way to integrate design clarification into a local workflow is using this Skill as the first stage of the sr-* workflow, connecting to sr-review, sr-plan-split, sr-task-runner, and sr-task-loop.

Does this design clarification process require inspecting existing repository truth?▼

Yes, this design clarification process requires inspecting existing repo truth to ground the design artifacts, ensuring the proposed product changes align with the actual current codebase and contracts before implementation.

What should a design artifact include when converting rough ideas into implementation plans?▼

A design artifact converting rough ideas into implementation plans should include goals, non-goals, affected modules, data models, and contracts, validated through user confirmation and design validation steps.