Guide structured technical discussions with codebase scouting and assumption-based reasoning.
npx skills add https://github.com/cashwu/Agentflow-SDD --skill cash-discuss
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
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.
Invoke the cash-discuss skill followed by your topic to begin a structured conversation about the project architecture.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
chenwei791129Facilitate structured technical discussions to reach architectural decisions.
tobihagemannGuide a collaborative discussion to produce a project specification at .turbo/spec.md.
DanSnowFacilitate structured technical discussions to reach consensus on architecture decisions.
cashwuFacilitate structured discussions to converge on design decisions.
