technical-discussion

Document technical debates into structured markdown files with context and decisions.

27|1|Updated Nov 23, 2025

Search Tags:#architecture #documentation #decisions #edge-cases #rationale #discussions #debates

Ready to run

npx skills add https://github.com/leeovery/claude-technical-workflows --skill technical-discussion

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: technical-discussion
Source: https://github.com/leeovery/claude-technical-workflows/tree/main/skills/technical-discussion
Command: npx skills add https://github.com/leeovery/claude-technical-workflows --skill technical-discussion

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill captures and documents technical debates as an expert architect and meeting assistant.

Core Features & Use Cases

Documentation of decisions: Record rationale, edge cases, and competing approaches from design discussions.
Structured discussion traces: Create topic-led documentation that preserves the conversation journey for future reference.
Knowledge capture for planning: Provide ready-to-consume context for specifications and implementations.

Quick Start

Start a discussion on a topic and let the skill emit a topic-focused doc at docs/workflow/discussion/{topic}.md.

Frequently Asked Questions about technical-discussion

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

FAQPage Schema

How do I document architectural decisions and rationale from team debates?▼

To document architectural decisions, you provide a topic and context to capture the rationale, edge cases, and competing approaches from technical debates. This generates a structured markdown file preserving the conversation journey for future reference.

What is the best way to capture technical design discussions and edge cases?▼

Capturing technical design discussions involves recording the conversation journey, options, and final decisions into a topic-focused documentation file. This ensures the context and rationale surrounding edge cases are ready for future implementation planning.

Can I generate architecture documentation from meeting context without manual formatting?▼

Yes, generating architecture documentation requires only a topic and its context to automatically output a structured markdown file. This file contains the discussion context, explored options, journey, and final decisions without manual formatting overhead.

Where are documented technical debates and design decisions stored by default?▼

Documented technical debates are stored as markdown files at the relative path docs/workflow/discussion/{topic}.md. This default location organizes decision rationale and discussion traces systematically within your project repository.

Do I need a specific framework to preserve rationale through architecture debates?▼

No specific framework is needed to preserve rationale through architecture debates, as there are no external dependencies. You only need to supply the discussion topic and context to generate the structured decision documentation.

How do technical discussion traces help with software implementation planning?▼

Technical discussion traces help with implementation planning by providing ready-to-consume context from recorded design debates. This documented rationale and explored options give developers immediate insight into why specific architectural decisions were made.