文件

Update planning docs and create tickets based on discrepancies report. Use this skill after running analyze-gaps to create tickets for unbuilt features and update roadmap. Handles DOCUMENTED_NOT_IMPLEMENTED gaps.

指定したプラグインの詳細情報を表示する。「プラグインの詳細」「〇〇プラグインについて教えて」「プラグインの情報」「〇〇の機能は？」「プラグインの中身を見せて」「〇〇プラグインの説明」「プラグインのコマンド一覧」などで起動。コマンド、スキル、エージェント、フック、README、バージョン情報を表示。

Comprehensive gap analysis framework for identifying missing capabilities, coverage, and requirements. Use for requirements vs implementation gaps, test coverage analysis, documentation gaps, security posture assessment, performance benchmarks, feature parity analysis, team capability gaps, infrastructure coverage, compliance gaps, and accessibility analysis. Includes SWOT, maturity models, and automated gap detection.

Context-driven development methodology for organized, spec-first coding. Use when:- Project has a `conductor/` directory- User mentions specs, plans, tracks, or context-driven development- Files like `conductor/tracks.md`, `conductor/product.md`, `conductor/workflow.md` exist- User asks about project status, implementation progress, or track management- User wants to organize development work with TDD practices- User invokes `/conductor-*` commands (setup, newtrack, implement, status, revert, validate, block, skip, revise, archive, export, refresh)- User mentions documentation is outdated or wants to sync context with codebase changesInteroperable with Gemini CLI extension and Claude Code commands.Integrates with Beads for persistent task memory across sessions.

PROACTIVE skill - STOP and invoke BEFORE writing dbt SQL. Validates models against coding conventions for staging, integration, and warehouse layers. Covers naming, SQL structure, field conventions, testing, and documentation. CRITICAL - When about to write .sql files in models/, invoke this skill first, write second. Supports project-specific convention overrides and sqlfluff integration.

Generate comprehensive implementation plans using Specification-Driven Development (SDD)methodology. Use when creating technical design, implementation roadmap, or executingthe /plan command.This skill orchestrates the plan-template.md execution flow, generating research, datamodels, API contracts, and test scenarios. It validates constitutional compliance(Library-First, Test-First, Contract-First) and prepares for task generation.Triggered by: /plan command, user request for "implementation plan", "technical design","how to implement", or "design this feature".

Use when creating or developing anything, before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation

Эксперт по документации кода. Используй для JSDoc, docstrings, комментариев и автогенерации документации.

Testing patterns including pytest, unittest, mocking, fixtures, and test-driven development with extended thinking integration. Activate for test writing, coverage analysis, TDD, hypothesis-driven development, and quality assurance tasks.

Maintain consistent code formatting, naming conventions, type safety, and automated code quality standards across PHP and TypeScript/JavaScript. Use this skill when writing or editing any PHP files (.php), TypeScript/JavaScript files (.ts, .tsx, .js, .jsx), when implementing type declarations and return types, when running code formatters (Laravel Pint, Ultracite) or linters, when running static analysis tools (Larastan), when naming variables, functions, classes, or files, when applying DRY principles, when removing dead code, or when preparing code for review or commit.

MUST be loaded before working with any Skill. Covers creating, building, reviewing, assessing, checking, auditing, evaluating, updating, modifying, and improving skills. Invoke PROACTIVELY before writing or changing any SKILL.md file. Provides structure, workflows, and validation for skill development. Supports both personal skills and standalone distributable skills (GitHub repos). (user)

Playwright best practices including selectors, wait strategies, accessibility testing, responsive design, and flaky-test prevention. Use when writing or improving Playwright E2E tests.

Assess technical, financial, operational, and organizational feasibility of learning projects including resource requirements, budget, timeline, and risk analysis. Use when evaluating project viability before committing resources. Activates on "feasibility study", "project viability", "resource planning", or "can we do this".

use this skill to write README.md files

Technical specification writing for implementation details. Use when documenting how to build a solution (post-decision), API contracts, schemas, and system design. Complements RFC skill which handles decision-making.

Improves text quality by enhancing grammar, vocabulary, narrative clarity, flow, pacing, and writing style while preserving the author’s voice.

Create SEO-optimized MDX blog posts with proper frontmatter

Systematic code review guidelines and checklist. Use this skill when reviewing code, conducting pull request reviews, or establishing code quality standards. Provides comprehensive review criteria covering functionality, design, testing, security, and documentation. Complements the code-quality agent.

Evaluates codebase architecture for patterns, anti-patterns, coupling, cohesion, scalability, and technical debt. Use when assessing system design, reviewing architecture decisions, identifying improvement areas, or preparing for major refactoring.

Comprehensive Rust development guidelines based on 6 months of code reviews. Use when writing Rust code, debugging Rust issues, or reviewing Rust PRs. Covers error handling, file I/O safety, type safety patterns, performance optimization, common footguns, and fundamental best practices. Perfect for both new and experienced Rust developers working on CLI tools, hooks, or production code.