sheikh-mohammad/agent-factory-claude-skills / .claude/skills/interview
interview
VerifiedThis skill conducts discovery conversations to understand user intent and agree on approach before taking action. It should be used when the user explicitly calls /interview, asks for recommendations, needs brainstorming, wants to clarify, or when the request could be misunderstood. Prevents building the wrong thing by uncovering WHY behind WHAT.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.1 KB |
| references/anti-patterns.md | markdown | 5.6 KB |
| references/question-patterns.md | markdown | 4.4 KB |
| references/summary-templates.md | markdown | 3.0 KB |
references/summary-templates.md
View on GitHub# Summary Templates
Formats for capturing mutual understanding. Match formality to situation.
---
## Core Principle
**Summaries confirm understanding, not create documentation.**
The goal is ensuring AI and user are aligned before proceeding. Keep it as simple as the situation allows.
---
## Standard Understanding Summary
Use for most situations:
```markdown
## Understanding Summary
**What we're doing**: [One clear statement]
**Goals**: [What success looks like]
**Key Points**:
- [Important point 1]
- [Important point 2]
- [Important point 3]
**Approach**: [How we'll proceed]
**Boundaries**: [What's NOT included]
**Open items**: [Any remaining uncertainties, or "None"]
---
Ready to proceed?
```
---
## Quick Summary
For simple, clear requests:
```markdown
**Got it**: [What user wants in one sentence]
**I'll**: [What AI will do]
**Confirm**: Ready to proceed?
```
---
## Brainstorming Summary
After exploratory conversations:
```markdown
## Where We Landed
**Exploring**: [Topic/problem space]
**Options Considered**:
1. [Option] - [Trade-off]
2. [Option] - [Trade-off]
3. [Option] - [Trade-off]
**Direction**: [What user is leaning toward]
**Next Step**: [What happens now]
**Still Open**: [Unresolved questions, if any]
```
---
## Complex Work Summary
For multi-faceted projects:
```markdown
## Understanding Summary
**Project**: [What this is]
**Goal**: [What success looks like]
### Key Elements
1. [Element 1]: [Brief description]
2. [Element 2]: [Brief description]
3. [Element 3]: [Brief description]
### Decisions Made
| Decision | Choice |
|----------|--------|
| [Decision 1] | [What we chose] |
| [Decision 2] | [What we chose] |
### Constraints
- [Constraint 1]
- [Constraint 2]
### Approach
[How we'll proceed]
### Not Included
- [Out of scope 1]
- [Out of scope 2]
### Open Items
- [Remaining question, if any]
---
Does this capture what you want?
```
---
## Decision Summary
When helping user make a choice:
```markdown
## Decision Summary
**Question**: [What we were deciding]
**Options Evaluated**:
| Option | Pros | Cons |
|--------|------|------|
| [A] | [Pros] | [Cons] |
| [B] | [Pros] | [Cons] |
**Decision**: [What user chose]
**Rationale**: [Why this choice]
**Next**: [What happens now]
```
---
## Formality Guide
| Situation | Template | Why |
|-----------|----------|-----|
| Simple request | Quick Summary | Don't over-formalize simple things |
| Brainstorming | Brainstorming Summary | Capture exploration, not specs |
| Clear medium task | Standard Summary | Right balance |
| Complex/multi-part | Complex Summary | Need more structure |
| Decision-making | Decision Summary | Document the choice |
---
## Summary Quality Check
Before presenting summary, verify:
- [ ] **Specific**: Could someone act on this?
- [ ] **Complete**: All key points captured?
- [ ] **Accurate**: Reflects what user said?
- [ ] **Scoped**: Boundaries are clear?
- [ ] **Actionable**: Clear what happens next?
If you can't make it specific, you need more questions first.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |