.claude/skills/next/SKILL.md
# Next Skill **Name:** next **Triggers:** `/next` (manual invocation only — not natural language) **Version:** 1.0.0 --- ## Purpose Task transition. Snapshots the current task state to disk, then guides the user to either `/compact` (if the next task is related) or `/clear` (if unrelated). Single biggest token saver in the optimization pack — the audit found that 98.5% of tokens in long sessions are conversation re-reading, and `/clear` between unrelated tasks eliminates that cost entirely.
npx skillsauth add CleanExpo/CCW-CRM .claude/skills/nextInstall 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: next
Triggers: /next (manual invocation only — not natural language)
Version: 1.0.0
Task transition. Snapshots the current task state to disk, then guides the user to either /compact (if the next task is related) or /clear (if unrelated). Single biggest token saver in the optimization pack — the audit found that 98.5% of tokens in long sessions are conversation re-reading, and /clear between unrelated tasks eliminates that cost entirely.
This skill is manual invocation only. It is not triggered by natural language because the decision to compact or clear is intentional and CEO-driven.
/nextRuns three steps:
Step 1 — Snapshot. Writes .claude/snapshots/last-task.md containing:
The snapshot is plain markdown. /resume reads it later to recover state without re-reading the conversation.
Step 2 — Ask. Asks the user one question via AskUserQuestion:
Is your next task RELATED to what we just did, or UNRELATED?
- RELATED — same module, same file, follow-up work → run
/compactand preserve file paths + decisions + test results- UNRELATED — different module, different concern → run
/clearand start fresh
Step 3 — Confirm. After the user picks, the skill prints one line:
Ready. Context [compacted/cleared]. Run /resume to restore the snapshot if needed..claude/snapshots/last-task.md:
# Last Task Snapshot
**Date:** YYYY-MM-DD HH:MM
**Branch:** claude/<worktree>
**Status:** [in-progress | complete | blocked]
## Completed
- [item 1]
- [item 2]
## Files Modified
- apps/backend/src/api/routes/X.py
- apps/web/components/Y.tsx
## Decisions
- [architectural choice + why]
- [pattern used + reference file]
## Next Steps
- [what the user asked for next]
- [open questions]
## Verification State
- Tests: [passing | failing | not run]
- Lint: [clean | dirty | not run]
- Type-check: [clean | dirty | not run]
/clear is destructive to conversation context./next slash command./resume parses it as plain text./next/clear directly.claude/skills/resume/SKILL.md — reads the snapshot this skill writes.claude/skills/ctx/SKILL.md — diagnoses whether /compact or /clear is needed.claude/snapshots/ — directory that holds snapshots and pre-compact diffs (auto-created by hooks + this skill)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)
tools
# 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
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)