.claude/skills/spec-interview/SKILL.md
# Spec Interview Skill **Name:** spec-interview **Triggers:** `/spec-interview`, when requirements unclear **Version:** 1.0.0 --- ## Purpose Interviews user to gather complete requirements before planning. --- ## Interview Questions When requirements are unclear, ask: ### 1. Feature Clarity **Question:** "What is this feature supposed to do?" **Why:** Need clear objective ### 2. User Impact **Question:** "Who will use this and why?" **Why:** Understand user needs ### 3. Success Criteri
npx skillsauth add CleanExpo/CCW-CRM .claude/skills/spec-interviewInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Name: spec-interview
Triggers: /spec-interview, when requirements unclear
Version: 1.0.0
Interviews user to gather complete requirements before planning.
When requirements are unclear, ask:
Question: "What is this feature supposed to do?" Why: Need clear objective
Question: "Who will use this and why?" Why: Understand user needs
Question: "How will we know this is working correctly?" Why: Define testable outcomes
Question: "Are there any technical or business constraints?" Why: Avoid blocked work
Question: "What should happen if [edge case]?" Why: Handle errors gracefully
Question: "Does this integrate with existing features?" Why: Prevent breaking changes
👋 I need to clarify a few things before planning:
1. **What should this feature do?**
[Wait for answer]
2. **Who will use it?**
[Wait for answer]
3. **How will we test it's working?**
[Wait for answer]
4. **Any constraints or dependencies?**
[Wait for answer]
---
Based on your answers, here's what I understand:
[Summarize]
Is this correct? Ready to plan?
Automatically triggered when:
Manually triggered:
/spec-interview
After interview, create a mini-spec:
## Feature Specification
**What:** [Feature name]
**Who:** [User type]
**Why:** [Problem being solved]
**Success:** [How we know it works]
**Constraints:**
- [Constraint 1]
- [Constraint 2]
**Edge Cases to Handle:**
- [Edge case 1]
- [Edge case 2]
Ready to create implementation plan.
content-media
Autonomously uploads CCW HeyGen demo videos to YouTube as Unlisted, collects video IDs, and patches DemoVideoBanner.tsx + video-registry.json. One-time OAuth setup required. Handles resume, retries, and ID propagation.
data-ai
Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits". (gstack)
development
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)
testing
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic. Use when: "setup deploy", "configure deployment", "set up land-and-deploy", "how do I deploy with gstack", "add deploy config".