cash-discuss

Guide structured technical discussions with codebase scouting and assumption-based reasoning.

1|Updated May 11, 2026

Search Tags:#workflow #architecture #collaboration #decision-making #discussion #codebase-analysis

Ready to run

npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-discuss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: cash-discuss
Source: https://github.com/cashwu/Agentflow-SDD/tree/main/.agents/skills/cash-discuss
Command: npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-discuss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of aimless or unproductive brainstorming by enforcing a structured, task-oriented discussion flow that ensures every conversation reaches a clear, actionable conclusion.

Core Features & Use Cases

Structured Workflow: Guides the AI through codebase scouting, assumption validation, and logical convergence.
Context-Aware Reasoning: Integrates project-specific vocabulary and codebase analysis to ground discussions in reality.
Use Case: Use this skill when you need to make an architectural decision, such as choosing between WebSockets and SSE for a new feature, to ensure you evaluate trade-offs and reach a documented consensus.

Quick Start

Invoke the cash-discuss skill followed by your topic to begin a structured conversation about the project architecture.

Frequently Asked Questions about cash-discuss

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

FAQPage Schema

How do I facilitate structured technical discussions for architectural decisions?▼

Structured technical discussions are facilitated by integrating codebase scouting and assumption-based reasoning to guide conversations toward actionable conclusions. This enforces a task-oriented workflow that resolves architectural questions through logical convergence.

What is the best way to stop unproductive brainstorming when planning software features?▼

To stop unproductive brainstorming, enforce a goal-oriented discussion flow that validates assumptions and grounds the conversation in codebase analysis. This ensures every feature planning session evaluates trade-offs and reaches a documented consensus.

How does assumption-based reasoning work in codebase analysis?▼

Assumption-based reasoning in codebase analysis works by validating project-specific vocabulary and architectural assumptions against the actual codebase. This context-aware approach grounds discussions in reality to ensure logical convergence on design challenges.

Can I use this approach to choose between different architectural patterns for a new feature?▼

Yes, you can use this approach to choose between architectural patterns by guiding the AI through codebase scouting and assumption validation. It ensures you evaluate trade-offs, such as choosing between WebSockets and SSE, to reach a documented consensus.

How do I start a goal-oriented conversation about project architecture?▼

Start a goal-oriented conversation by invoking the discussion skill followed by your specific topic. This initiates a structured workflow that scouts the codebase and integrates project-specific vocabulary to resolve architectural questions.

When should I not use a structured discussion workflow for software development?▼

You should not use a structured discussion workflow when your development context lacks clear architectural questions or defined goals. Without project-specific vocabulary or a codebase to analyze, the enforced logical convergence and assumption validation provide minimal value.