Discover Databases skills, compare source repositories and read the instructions for each workflow.
Operational support and maintenance for released software. Monitoring and observability, incident management, maintenance and patch management, continuous improvement, security operations, compliance and audit,...
Shared compliance and audit framework across all phases. Regulatory requirements, compliance matrix, audit readiness, documentation requirements, and gap analysis. Warm, story-driven Expert Mentor style for 202...
You'll transform your business idea into a concrete, funded, and approved product vision. Through structured workshops and stakeholder alignment, you'll create a compelling business case, detailed PRD, and secu...
Git operations with conventional commits.
Use when writing applications in OxCaml, using modes (local, portable, contended), unboxed types (float#, int32#, I64, I32, F64, UFO), SIMD vectors, stack allocation, immutable arrays, labeled tuples, zero_allo...
Use to set up Obsidian vault and populate it with existing codebase knowledge. Enables context memory for AI development.
Use to trace requirements through implementation. Maps acceptance criteria to code and tests.
Use to improve story sizing accuracy by analyzing historical estimation data. Identifies patterns, updates size definitions, and refines PROBE proxy selections.
Use to identify and prepare the next logical story based on project progress. Creates comprehensive story files with full technical context.
Manage Claude Code hooks for workflow automation. Create, configure, test, and debug hooks that execute at various lifecycle points. Supports all hook events (PreToolUse, PostToolUse, SessionStart, etc.) with e...
Use to apply PROBE (PROxy-Based Estimation) method for story sizing. Uses historical data for accurate effort estimation.
Use for root cause analysis of bugs or issues. Systematically investigates problems to identify underlying causes.
Initialize PRISM .context folder in current project. Use when starting PRISM work in a new project or setting up context management.
Use to validate reported issues. Confirms reproducibility and documents validation evidence.
Use as reference guide for strangler pattern implementation. Provides patterns and best practices for legacy migrations.
Create custom Claude Code sub-agents with specialized expertise and tool access. Use when you need to build reusable agents for specific tasks like code review, debugging, data analysis, or domain-specific work...
Use to create complete architecture documentation structure. Creates all required architecture documents from templates.
Use to systematically validate documents, stories, or processes against defined checklists. Ensures quality and completeness.
Use to design test strategies and create test specifications. Documents testing approaches for stories.
Use to break down large stories into optimally-sized stories (1-3 days). Applies PSP measurement discipline.
Use to perform comprehensive test architecture review with quality gate decision. Creates both story updates and detailed gate files.
Use when creating new Epic documents. Groups related user stories, includes risk analysis, integration points, and story breakdown with PROBE estimation.
Use when Dev agent needs to implement fixes based on QA gate results. Reads QA outputs, creates prioritized fix plans, and applies code/test changes to address identified issues.
Use to analyze and document any project codebase. Creates comprehensive reference documentation for AI-assisted development including architecture and patterns.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.