skills.rest
Nickalus12
Nickalus12COMMUNITY
Explore all skills by this author →
GitHub

design-dialogue

Guide engineers through depth-controlled design conversations to converge on approved architectures.

2|Updated Apr 4, 2026
Search Tags:#design#planning#architecture#dialogue#engineering#risk-management#decision-making
One-click install
npx skills add https://github.com/Nickalus12/Loom --skill design-dialogue-nickalus12
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: design-dialogue
Source: https://github.com/Nickalus12/Loom/tree/main/claude/skills/design-dialogue
Command: npx skills add https://github.com/Nickalus12/Loom --skill design-dialogue-nickalus12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured design conversations help teams converge on approved architectures for complex engineering tasks, reducing ambiguity and rework.

Core Features & Use Cases

  • Depth-gated questioning (Quick/Standard/Deep) to adapt reasoning rigor to task needs.
  • Phase 1 Loom orchestration integration with Plan Mode activation and user confirmations.
  • Grounding protocol, depth propagation, and risk-awareness to maintain alignment across turns.

Quick Start

Begin Phase 1 by enabling Plan Mode and selecting a depth level for the design discussion.

Frequently Asked Questions about design-dialogue

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

FAQPage Schema
How do I structure engineering design conversations to reach approved architectures faster?▼

Structured design conversations use depth-controlled questioning to guide engineers toward approved architectures, reducing ambiguity and rework. They enforce a grounding protocol to maintain alignment across discussion turns.

How do I adjust design discussion rigor based on task complexity?▼

Depth-gated questioning adapts design discussion rigor by offering Quick, Standard, and Deep levels. This dynamic depth selection matches reasoning effort to the specific complexity of the engineering task at hand.

Can I use Plan Mode for structured design discussions and user confirmations?▼

Yes, structured design discussions integrate with Plan Mode for Phase 1 orchestration. This workflow uses a guided user-confirmation flow and an AskUserQuestion protocol to navigate from simple to complex engineering tasks.

How does risk management factor into architectural decision-making during design planning?▼

Architectural decision-making incorporates risk-awareness by enforcing a grounding protocol and YAML frontmatter metadata like design_depth and task_complexity. This maintains alignment and ensures consistent design outcomes across discussions.

What is the best way to document design depth and task complexity for engineering planning?▼

Document design depth and task complexity using enforced YAML frontmatter metadata. This approach propagates depth selections and maintains structural consistency throughout the entire design conversation workflow.

Related Skills

Explore More Design & Creative Skills→
qazuorqazuor

task-from-spec

Parse spec.md and metadata.json to generate scored task states with dependencies.

Community
Advanced
skanehiraskanehira
88

planning-tasks

Generate a TDD-compliant TODO.md from an approved design document.

Community
Intermediate
prince3626ezechiel-langprince3626ezechiel-lang

council

Orchestrate structured multi-agent debates for complex decision-making.

Community
Advanced
zMynxxzMynxx

ponytail

Enforce minimal implementation choices and avoid over-engineering in coding tasks.

Community
Intermediate