technical-discussion
Collaborative technical discussion with proactive requirements gathering
When & Why to Use This Skill
This Claude skill facilitates proactive technical discussions and structured requirements gathering to ensure software projects are built on a solid foundation. By employing an iterative questioning technique, it helps developers and stakeholders align on project scope, technical constraints, and implementation strategies before proceeding with code execution, significantly reducing development errors and technical debt.
Use Cases
- Project Scoping: Defining the technical boundaries and functional requirements for a new software feature or application.
- Technical Feasibility Analysis: Conducting deep-dive discussions to evaluate the impact and viability of proposed code enhancements or system changes.
- Requirement Refinement: Transforming vague user requests into actionable technical specifications through focused, one-at-a-time questioning.
- Constraint Identification: Proactively uncovering hidden technical limitations, dependencies, or security considerations early in the development lifecycle.
| name | technical-discussion |
|---|---|
| description | Collaborative technical discussion with proactive requirements gathering |
When To Use
- Use this skill PROACTIVELY when user asks for a technical discussion on a project, requirement or feature scope to implement, or an enhancement to existing requirement
Examples
Following are some (non-exhaustive) example prompts when this skill should be used:
- I want to have a thorough technical discussion about: $ARGUMENTS
- Enhance the code to implement: $ARGUMENTS
- Conduct a technical analysis of: $ARGUMENTS
- Fix the code so that it implements: $ARGUMENTS
- We need a technical discussion first
- Analyze the requirement
- Continue the technical discussion about: $ARGUMENTS
Before proceeding with any implementation or detailed analysis, I need you to gather important context through focused questions. Ask me relevant questions to understand my requirements and constraints, ensuring we build the right solution.
Ask questions ONE AT A TIME to keep our discussion focused and efficient. Incrementally build up on the previous questions and ask more detailed questions.
Each question should be tailored to the specific topic and help uncover the technical details needed to move forward effectively.
Start by asking me questions related to $ARGUMENTS to better understand what I'm looking to achieve and how we should approach this together.