new-feature-design
Design and document new features with GitHub issue, low-level design (LLD), expert review, and testing plan. Creates structured documentation in .scratchpad/ with issue spec, technical design with diagrams and pseudo-code, multi-persona expert review, and a testing plan covering functional (curl and registry_management.py), backwards-compatibility, UX, ECS/terraform, and E2E API tests. Supports starting from a user description OR an existing GitHub issue URL. Folder naming: issue-{number}/ for existing issues, {feature-name}/ for new features.
npx skills add agentic-community/mcp-gateway-registry --skill new-feature-design --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill guides design work for a new feature in the MCP Gateway Registry. It can start from a user-provided description or from an existing GitHub issue URL. It creates a structured set of documents:
- A design folder under .scratchpad/ with a concrete folder name depending on mode (either issue-{number}/ or {feature-name}/)
- GitHub issue related documents (github-issue.md), a low-level design document (lld.md), an expert review (review.md), and a testing plan (testing.md)
- In GitHub Issue URL Mode, it fetches and analyzes the issue via gh, then creates a summarized github-issue.md and proceeds with clarifications.
- In User Description Mode, it gathers requirements through questions, conducts a quick codebase review, and then writes the design docs.
- The workflow includes deep codebase analysis, multi-persona expert review, and a detailed testing plan covering functional, backwards-compatibility, UX, ECS/terraform, and E2E tests.
How it works
- Mode detection: If a GitHub issue URL is provided, operate in GitHub Issue URL Mode; otherwise, switch to User Description Mode.
- Folder creation: Create a .scratchpad/ directory named according to the mode: issue-{number}/ for existing issues or {feature-name}/ for new features.
- Document generation: Produce four primary documents within the folder: github-issue.md, lld.md, review.md, and testing.md.
- GitHub integration (URL mode): Use the gh CLI to fetch issue details and related PRs, then compile a summary in github-issue.md and identify gaps for clarification.
- Analysis and design: Conduct a deep analysis of the codebase (via the Task tool in the specified sections) and produce a Low-Level Design (lld.md) with detailed technical specifics, followed by an expert review (review.md) and a complete testing strategy (testing.md).
- Invariant checks: Reference the theory-of-the-system to ensure the design respects core invariants; if a theory impact is identified, call it out in the LLD and Expert Review.
When to use it
- When you need to design a new feature for the MCP Gateway Registry and want to produce structured, implementation-ready documentation.
- When starting from an existing GitHub issue or from a user-provided feature description.
What it can touch
- The skill relies on claude-code for codebase exploration and documentation tasks. It interacts with the repository to review models, services, routes, storage, configurations, and tests as part of the Deep Codebase Analysis step.
Caveats
- Requires access to the repository to perform deep codebase analysis and to generate accurate LLD content.
- If the feature would violate invariants from the Theory of the System, the tool will flag it in the LLD and Expert Review and provide justification.
- Output is limited to the specified documents under .scratchpad/{...} and does not modify source code unless explicitly extended by subsequent implementation steps.
# New Feature Design Skill Use this skill when the user wants to design a new feature for the MCP Gateway Registry. This skill creates comprehensive design documentation that enables entry-level developers to implement the feature. ## Input Modes This skill supports two input modes: 1. **User Description Mode** - User describes the feature they want to design 2. **GitHub Issue URL Mode** - User provides a URL to an existing GitHub issue ### Detecting Input Mode When the user invokes this skill: - If they provide a GitHub issue URL (e.g., `https://github.com/owner/repo/issues/123`), use **GitHub Issue URL Mode** - Otherwise, use **User Description Mode** ## Workflow ### User Description Mode Workflow 1. **Gather Requirements** - Ask clarifying questions about the feature 2. **Quick Codebase Review** - Explore the codebase to understand structure 3. **Create Design Folder** - Create `.scratchpad/{feature-name}/` directory 4. **Write GitHub Issue** - Create `github-issue.md` for issue creation 5. **Deep Codebase Analysis** - Thoroughly explore relevant code 6. **Write Low-Level Design** - Create `lld.md` with technical details 7. **Expert Review** - Create `review.md` with multi-perso
- Input Modes
- Detecting Input Mode
- Workflow
- User Description Mode Workflow
- GitHub Issue URL Mode Workflow
- GitHub Issue URL Mode
- Step 1: Fetch GitHub Issue
- Step 2: Analyze Issue Content
- Step 3: Create Issue Summary
- Step 4: Clarify Requirements
- User Description Mode
- Step 1: Gather Requirements
- Step 2: Quick Codebase Review
- Step 3: Create Design Folder
Extract owner, repo, and issue number from URL
URL format: https://github.com/{owner}/{repo}/issues/{number}
Fetch issue details
gh issue view {number} --repo {owner}/{repo} --json title,body,labels,state,assignees,comments
For more context, also fetch related PRs if any
gh issue view {number} --repo {owner}/{repo} --json linkedPullRequests
Verify ai-registry-tools (mcpgw) is reachable through the full proxy chain
curl -X POST \What does the new-feature-design skill do?
Design and document new features with GitHub issue, low-level design (LLD), expert review, and testing plan. Creates structured documentation in .scratchpad/ with issue spec, technical design with diagrams and pseudo-code, multi-persona expert review, and a testing plan covering functional (curl and registry_management.py), backwards-compatibility, UX, ECS/terraform, and E2E API tests. Supports starting from a user description OR an existing GitHub issue URL. Folder naming: issue-{number}/ for existing issues, {feature-name}/ for new features.
How do I install it?
Run `npx skills add agentic-community/mcp-gateway-registry --skill new-feature-design --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 agentic-community/mcp-gateway-registry, a repository with 845 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.