Claude Skills by Enakoneschniy

Show 4-option continuation prompt when session budget is low. Options: remind later (CronCreate), auto-continue locally (Desktop task), auto-continue in cloud (Cloud task), continue now. Trigger when: budget warning fires, session limit reached, context is full, user sees budget warning.

Run a quick one-shot task using a fast model (Haiku). Single-dispatch, no multi-turn. For complex work, use Claude Code normally instead.

Search past session observations using the sessions.search MCP tool. Falls back to CLI if the MCP server is not available.

Show project memory statistics: session count, observation counts by type, entity count, top entities, and project planning status.

Use NotebookLM for grounded research — documentation queries, stack comparisons, session log search. Trigger when user needs answers FROM SPECIFIC DOCUMENTATION or FROM PAST SESSIONS: "по документации", "check docs", "как в Payload", "как в Next.js", "что мы решили про", "when did we decide", "по нашим записям", "спроси в нотбуке", "ask notebooklm", "query notebook", "загрузи доки", "load docs", "add to notebook", "найди в сессиях", "search sessions", "когда мы делали". Also for structured co...

Import Notion pages into project vault via MCP. Trigger when user wants to import or sync Notion content into the vault: "import notion", "notion docs", "sync notion", "импортируй notion", "обнови notion", "sync notion pages", "обнови notion docs". Uses the claude.ai Notion MCP server (notion-fetch tool) directly from a live Claude session. Does NOT spawn subprocesses.

Fallback for manual session logging when auto-capture is disabled or fails, plus explicit resume/handoff/status requests. Auto-capture via hooks/session-end-capture.mjs is the primary Stop-time path — this skill is a safety net. Triggers on end-of-session signals ("done", "end", "всё", "хватит", "finish", "конец") and resume-intent requests ("resume", "продолжи", "что делали", "handoff", "what did we do").

Add an idea to the backlog parking lot (999.x numbering)

Add phase to end of current milestone in roadmap

Generate tests for a completed phase based on UAT criteria and implementation

Capture idea or task as todo from current conversation context

Generate AI design contract (AI-SPEC.md) for phases that involve building AI systems — framework selection, implementation guidance from official docs, and evaluation strategy

Analyze phase dependencies and suggest Depends on entries for ROADMAP.md

Autonomous audit-to-fix pipeline — find issues, classify, fix, test, commit

Audit milestone completion against original intent before archiving

Cross-phase audit of all outstanding UAT and verification items

Run all remaining phases autonomously — discuss→plan→execute per phase

List pending todos and select one to work on

Archive accumulated phase directories from completed milestones

Auto-fix issues found by code review in REVIEW.md. Spawns fixer agent, commits each fix atomically, produces REVIEW-FIX.md summary.

Review source files changed during a phase for bugs, security issues, and code quality problems

Archive completed milestone and prepare for next version

Systematic debugging with persistent state across context resets

Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (Claude picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).

Route freeform text to the right GSD command automatically

Generate or update project documentation verified against the codebase

Retroactively audit an executed AI phase's evaluation coverage — scores each eval dimension as COVERED/PARTIAL/MISSING and produces an actionable EVAL-REVIEW.md with remediation plan

Execute all plans in a phase with wave-based parallelization

Socratic ideation and idea routing — think through ideas before committing to plans

Extract decisions, lessons, patterns, and surprises from completed phase artifacts

Execute a trivial task inline — no subagents, no planning overhead

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format

Build, query, and inspect the project knowledge graph in .planning/graphs/

Diagnose planning directory health and optionally repair issues

Show available GSD commands and usage guide

Ingest external plans with conflict detection against project decisions before writing anything.

Insert urgent work as decimal phase (e.g., 72.1) between existing phases

Query, inspect, or refresh codebase intelligence files in .planning/intel/

Join the GSD Discord community

Surface Claude's assumptions about a phase approach before planning

List active GSD workspaces and their status

Interactive command center for managing multiple phases from one terminal

Analyze codebase with parallel mapper agents to produce .planning/codebase/ documents

Generate a comprehensive project summary from milestone artifacts for team onboarding and review

Start a new milestone cycle — update PROJECT.md and route to requirements

Initialize a new project with deep context gathering and PROJECT.md

Create an isolated workspace with repo copies and independent .planning/

Automatically advance to the next logical step in the GSD workflow

Zero-friction idea capture. Append, list, or promote notes to todos.