feature-design

Name: feature-design
Availability: InStock
Author: notque

Facilitate collaborative feature design discussions and generate design documents.

415|44|Updated Mar 18, 2026

Search Tags:#design #planning #collaboration #ADR #feature #gate #design-document

Ready to run

npx skills add https://github.com/notque/claude-code-toolkit --skill feature-design-notque

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: feature-design
Source: https://github.com/notque/claude-code-toolkit/tree/main/skills/feature-design
Command: npx skills add https://github.com/notque/claude-code-toolkit --skill feature-design-notque

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Collaborative design phase that helps teams align on feature goals, capture requirements, and foreclose design drift before coding begins.

Core Features & Use Cases

Facilitates structured design conversations and clarifying questions
Produces a design document (problem statement, requirements, trade-offs)
Manages gates and context for downstream phases like planning and implementation
Use Case: when starting a new feature or major refactor that needs design before code

Quick Start

Start a design session for a new feature by invoking /feature-design to begin collaborative discussion and generate the design document.

Frequently Asked Questions about feature-design

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

FAQPage Schema

How do I facilitate collaborative feature design before coding begins?▼

Collaborative feature design is facilitated through structured discussions, clarifying questions, and requirement capture to align team goals and prevent design drift. It produces a design document containing the problem statement, requirements, and trade-offs.

When do I need to create an ADR for a feature design?▼

You need to create an ADR for feature design when starting a new feature or undertaking a major refactor that requires upfront exploration and trade-off analysis. ADR-driven decisions enforce gate checks to ensure architectural alignment before implementation.

What is the best way to capture requirements and prevent design drift?▼

The best way to capture requirements and prevent design drift is by enforcing gate checks and generating a formal design document during collaborative sessions. This approach forecloses misalignment by explicitly recording problem statements and trade-offs before coding.

How do I manage gates and context for downstream planning and implementation?▼

You manage gates and context for downstream planning and implementation by applying ADR documentation and context loading during the design phase. This preparation ensures the transition into the plan, implement, and validate phases is guided by approved artifacts.

Does feature design work for both new features and major refactors?▼

Yes, feature design works for both new features and major refactors that require upfront exploration and trade-off analysis. It facilitates the structured design conversations and ADR-driven decisions necessary to guide implementation in either scenario.