investigate-root-cause
Use for root cause analysis of bugs or issues. Systematically investigates problems to identify underlying causes.
Discover Development skills, compare source repositories and read the instructions for each workflow.
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.
Build efficient, scalable Claude Code skills using progressive disclosure and token optimization. Use when creating new skills, optimizing existing skills, or learning skill development patterns. Provides templ...
Start PRISM TDD workflow loop using Ralph Wiggum pattern. Auto-progresses through Planning, TDD RED (failing tests), TDD GREEN (implementation), and Review phases. Use when user wants to run the core developmen...
Use to create or update quality gate decision files for stories. Provides clear pass/fail decisions with actionable feedback.
Jira integration for fetching issue context (Epics, Stories, Bugs) to enhance development workflows. Use for automatic issue detection, retrieving ticket details, acceptance criteria, and linked dependencies.
Use to create QA task documents. Generates test specifications and validation requirements for QA team.
Use for SDLC phase transitions. Ensures proper handoff between development phases with documentation.
Use to assess and document risk factors for stories or features. Creates risk profiles with mitigation strategies.
Use to create failing tests before implementing features (TDD approach). Ensures test-first development workflow.
Use when user mentions a Jira issue key (e.g., PLAT-123) or needs context from Jira. Retrieves and formats issue details for PRISM agent workflows.
Use to generate development task documents for the Dev agent. Creates specifications describing WHAT needs fixing based on validated issues and investigations.
Use when handling sprint changes or scope adjustments. Analyzes change impacts, re-estimates affected stories, and adjusts sprint capacity using PRISM principles.
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.