Loading...
Loading...
Found 2,893 Skills
Use when you need to generate/update test plans, test cases, test suites or test reports during the verification phase of Spec Pack, and require strict access control, traceable artifact storage, and no unauthorized routing.
You are updating this project's CLAUDE.md to reflect **meta learnings** (conventions, philosophy, gotchas) and **significant recent changes** to the codebase.
Эксперт по интеграционным спецификациям. Используй для документирования интеграций, webhooks, event schemas и data flows.
Create a stakeholder update when the user asks to write a status update, send a project update, prepare an executive summary, or draft a BLUF update
General Technical Design Document Summarization Skill: Scan documents and diagrams in the current execution directory (Markdown, PlantUML/Mermaid, drawio, images, etc.), extract system objectives, module boundaries, core processes, sequences and states, and output structured technical design documents. Use this skill when users mention "technical design documents", "solution sorting", "summarize design based on existing documents", "summarize documents and diagrams in the directory", or "complete sequence diagrams/state diagrams".
Use when you need to generate an AGENTS.md file for a Java repository — covering project conventions, tech stack, file structure, commands, Git workflow, and contributor boundaries — through a modular, step-based interactive process that adapts to your specific project needs. Part of the skills-for-java project
Create and manage video rooms for real-time video communication and conferencing. This skill provides Go SDK examples.
Search, order, and manage phone numbers by location, features, and coverage.
Generate AGENTS.md file and docs/ knowledge base skeleton in the project root directory, and establish a document governance system for agent-first repositories. Manually triggered, writes the template after checking for existence.
Map an existing codebase into an as-is Memory Bank without inventing roadmap items.
Use before any non-instant feature work, refactor, behavior change, or requirements-shaping conversation where user intent is not yet locked. Extracts and confirms the decisions that planning will depend on, especially when the user knows what they want but has not fully thought through edge cases, scope boundaries, or expected behavior. Output is CONTEXT.md.
Use when you need to execute I1 (Implementation Plan) in the Spec Pack of sdlc-dev, convert requirements/design into `{FEATURE_DIR}/implementation/plan.md` (the single source of truth for execution checklist and status, SSOT), and provide an unambiguous task list for subsequent I2 execution.