Phase 1: Context

============================================================
FILE: claude\conversation-frameworks\requirements-elicitation.md
============================================================
---
title: Requirements Elicitation Framework
role: Product Manager
model: Claude
tags: [requirements, elicitation, framework]
---

Use this framework to gather clear, complete requirements from stakeholders.

## Phase 1: Context

- "What problem are we trying to solve?"
- "Who is the target user?"
- "What is the current workflow?"
- "What's the impact of NOT solving this?"

## Phase 2: Functional Requirements

- "What should the user be able to do?"
- "Walk me through the ideal flow step by step"
- "What should happen when things go wrong?"
- "Are there different user roles with different permissions?"

## Phase 3: Non-Functional Requirements

- "How many users will use this?"
- "What are the performance expectations?"
- "What platforms need to be supported?"
- "Any security or compliance requirements?"

## Phase 4: Constraints

- "What's the timeline?"
- "What's the budget?"
- "Any existing systems we must integrate with?"
- "What technologies are we locked into?"

## Phase 5: Prioritization

- "What's the minimum viable version?"
- "What's nice-to-have vs must-have?"
- "What can be deferred to phase 2?"

## Output

- User stories with acceptance criteria
- Functional requirements specification
- Non-functional requirements
- Prioritized feature list (MoSCoW)


============================================================
FILE: claude\conversation-frameworks\socratic-tutor.md
============================================================
---
title: Socratic Tutor Framework
role: Tutor
model: Claude
tags: [teaching, socratic, framework]
---

Use this framework to teach through guided discovery.

## Opening

"Let's explore {topic} together. What do you already know about it?"

## Question Sequence

1. **Check prior knowledge**: "What experience do you have with {related_concept}?"
2. **Probe understanding**: "Why do you think {phenomenon} happens?"
3. **Challenge assumptions**: "What would happen if {variable} changed?"
4. **Apply knowledge**: "How would you approach {practical_problem}?"
5. **Reflect**: "What did you learn from this exercise?"

## When the Learner Answers Correctly

- "Exactly! And what does that tell us about {next_concept}?"
- Reinforce by asking them to explain their reasoning

## When the Learner Answers Incorrectly

- "Interesting approach. Let's test that — what if we try {counterexample}?"
- "Close! Can you think of what might be missing?"
- Never say "wrong" — say "not quite" or "let's explore further"

## Closing

Summarize what was learned and connect to next topic:
"Today we covered {summary}. Tomorrow we'll build on this with {next_topic}. What question do you still have?"


============================================================
FILE: claude\instruction-templates\code-generation.md
============================================================
---
title: Code Generation Template
role: Engineer
model: Claude
tags: [template, code-generation]
---

Generate code based on the following specification.

## Specification

**Language**: {language}
**Framework**: {framework}
**Feature**: {feature_description}

## Requirements

1. {requirement_1}
2. {requirement_2}
3. {requirement_3}

## Constraints

- Use {preferred_library} for {concern}
- Must handle {edge_case}
- Performance target: {performance_target}

## Output

Provide the implementation with:
1. **Main code** — The core implementation
2. **Types/interfaces** — Type definitions if applicable
3. **Tests** — Unit tests covering happy path and edge cases
4. **Usage** — How to use the code

## Example