design-discussion

Name: design-discussion
Availability: InStock
Author: citybear3

Orchestrates engineering design discussions to clarify requirements and route to next steps.

Updated Nov 4, 2022

Search Tags:#requirements #decision tree #ultrathink #engineering design #architecture trade-offs #routing workflow

Ready to run

npx skills add https://github.com/CityBear3/dotfiles --skill design-discussion-citybear3

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-discussion
Source: https://github.com/CityBear3/dotfiles/tree/main/claude/skills/design-discussion
Command: npx skills add https://github.com/CityBear3/dotfiles --skill design-discussion-citybear3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you kick off engineering work by turning an initial topic into shared understanding, decision pathways, and a clear next step for downstream planning or documentation.

Core Features & Use Cases

Engineering kickoff via guided dialogue: Clarifies requirements and constraints through structured conversation, including deep investigation of the codebase and existing specs before questioning.
Relentless decision-tree grilling: Surfaces assumptions, edge cases, and trade-offs one decision at a time so critical-path choices are not missed.
Mandatory routing to the next workflow skill: Concludes with an explicit next step based on whether you need formal design docs, planning, debugging, or execution.

Quick Start

Use /design-discussion with your topic (for example, /design-discussion "Add a new authentication flow") and respond to each single question to reach a routed next step.

Frequently Asked Questions about design-discussion

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

FAQPage Schema

How do I clarify engineering requirements before starting development?▼

To clarify engineering requirements, use a guided design discussion that investigates the codebase and specs, then applies one-question-at-a-time grilling to surface assumptions, edge cases, and trade-offs. This turns initial ambiguity into shared understanding and a routed plan.

What is the best way to evaluate architecture trade-offs for a new feature?▼

Evaluating architecture trade-offs for a new feature is best done through relentless decision-tree grilling, which surfaces critical-path choices one decision at a time. This method ensures edge cases and assumptions are explicitly addressed before routing to execution.

How do I start an engineering design discussion for a refactoring task?▼

You start an engineering design discussion for a refactoring task by providing the topic, then answering single questions posed after deep investigation. This guides you through constraints and concludes with a specific next step for planning or debugging.

Can I use a guided workflow to route engineering tasks to planning or debugging?▼

Yes, you can use a guided workflow to route engineering tasks to planning or debugging. The discussion concludes with an explicit next step based on your answers, directing you to formal design docs, planning, debugging, or execution workflows.

When do I need a structured decision tree for software engineering design?▼

You need a structured decision tree for software engineering design when starting new features, bug fixes, refactors, or exploratory tasks where trade-offs exist. It clarifies requirements and drives structured decision-making before downstream execution.