estimate-stories
Calculate story point estimates for user stories using structured formula (Complexity × Effort + Risk). Analyzes acceptance criteria, assesses complexity (1-5), effort (1-5), and risk (0-3), then documents estimation rationale. Use during backlog grooming or sprint planning when stories need sizing.
risk-profile
Assess implementation risks using Probability × Impact (P×I) scoring methodology across 6 categories (Technical, Security, Performance, Data, Business, Operational). Scores risks (P×I: 1-9), develops mitigations for high-risk items (score ≥6), and prioritizes test scenarios (P0/P1/P2). Use before implementation or during quality review to identify and mitigate potential issues.
review-task
Orchestrate comprehensive quality assessment by executing 5 specialized quality skills in sequence and synthesizing results into a unified quality gate decision. This skill should be used when performing final review of completed implementation.
refine-story
Transform vague or incomplete user stories into sprint-ready stories with clear acceptance criteria, test scenarios, and technical guidance. This skill should be used before sprint commitment for definition of ready check.
document-project
Generate comprehensive architecture documentation automatically from existing codebase analysis. This skill should be used when working with brownfield projects or updating outdated documentation.
create-task-spec
Create hyper-detailed task specifications with embedded context, eliminating implementation lookups. This skill should be used for breaking features into implementable tasks with complete architecture references.
create-prd
Create comprehensive Product Requirements Documents (PRD) from high-level product ideas with structured market analysis, feature definition, and success metrics for both greenfield and brownfield contexts. Use when defining product vision for new projects (greenfield) or formalizing requirements for existing systems (brownfield).
refactor-code
Safely improve code quality through test-driven refactoring with automatic validation and rollback. Use during quality review to reduce technical debt while preserving behavior.
quality-gate
Synthesize all quality assessments (risk, test-design, traceability, NFR) into evidence-based gate decision (PASS/CONCERNS/FAIL/WAIVED) with comprehensive rationale. Generates both YAML (CI/CD) and Markdown (human review) reports with action items. Use during final quality review to make go/no-go deployment decisions based on comprehensive quality evidence.
nfr-assess
Assess non-functional requirements across 6 quality categories (Security, Performance, Reliability, Maintainability, Scalability, Usability) with measurable criteria, evidence-based evaluation, and automated checks. Scores each category, identifies gaps with severity ratings, and provides remediation guidance. Use during quality review to evaluate production readiness and NFR compliance.
create-brownfield-prd
Generate Product Requirements Documents (PRD) for existing systems through systematic codebase analysis, feature extraction, and gap identification with confidence scoring for validation-needed areas. Use when documenting existing systems that lack requirements documentation or preparing for system modernization/migration.
shard-document
Break large documents into smaller, manageable shards with maintained relationships and navigation, improving document usability and maintenance for PRDs, specs, and technical documentation. Use when large documents (>5000 words) need splitting for better maintainability, navigation, or when documentation becomes difficult to navigate.
interactive-checklist
Create interactive, guided checklists for multi-step workflows, validation processes, onboarding sequences, and complex procedures with step-by-step tracking and decision trees. Use when documenting complex workflows, creating validation procedures, or building step-by-step guides requiring user interaction and decision tracking.
breakdown-epic
Break down epics into implementable user stories with acceptance criteria, estimates, dependencies, and sprint groupings. This skill should be used for epic planning and backlog grooming.
compare-architectures
Generate and compare multiple architecture options (minimal, moderate, full modernization) with comprehensive trade-offs analysis across cost, timeline, risk, performance, and maintainability dimensions. Use when evaluating multiple architectural approaches or deciding between modernization strategies with different cost/risk trade-offs.
create-adr
Create Architecture Decision Records (ADRs) documenting key architectural choices. Analyzes context, evaluates alternatives, and captures decisions using standard ADR template. Use when documenting database design, technology selection, pattern choices, or architectural trade-offs.
create-architecture
Generate comprehensive system architecture documents from requirements, supporting Frontend, Backend, and Fullstack projects with scale-adaptive depth and Architecture Decision Records. Use when translating requirements (PRD/epic) into technical architecture for new projects or major features.
run-tests
Execute tests with coverage analysis using bmad-commands, identify coverage gaps, and suggest missing tests. This skill should be used for test execution and quality validation.
sprint-plan
Create comprehensive sprint plans by intelligently grouping estimated user stories based on velocity, dependencies, priorities, and risk. This skill should be used during sprint planning ceremonies to transform backlog into actionable sprint commitments.
test-design
Design comprehensive test strategies with risk-informed prioritization (P0/P1/P2), test levels (unit/integration/E2E), mock strategies, and CI/CD integration. Creates Given-When-Then scenarios for all acceptance criteria, develops mock strategies for external dependencies, and plans CI/CD execution stages. Use during task planning before implementation to ensure comprehensive test coverage.
validate-architecture
Validate architecture document completeness and quality against comprehensive checklist. Checks required sections, technology justifications, NFRs coverage, and generates quality score with actionable recommendations. Use after architecture creation to verify completeness, quality, and NFR coverage before implementation begins.
trace-requirements
Create comprehensive bidirectional requirements traceability matrix mapping acceptance criteria → implementation → tests with gap analysis, severity ratings, and coverage assessment. Maps each AC to implementation evidence (files, functions, code snippets) and test coverage (test files, scenarios, priorities). Use during quality review or for compliance audits to verify complete requirements coverage.
sqlalchemy
Scraped from https://docs.sqlalchemy.org/en/20/ Source: https://docs.sqlalchemy.org/en/20/. Use when questions involve: _modules, changelog, core, dialects, faq, orm.
skills-builder
Build Claude Code skills from documentation websites. Scrapes Mintlify, ReadTheDocs/Sphinx, Docusaurus, GitBook, and static HTML sites. Generates properly formatted skills with SKILL.md and reference files. Use when: creating skills from docs, scraping documentation, generating reference materials from URLs.
sequelize
Scraped from https://sequelize.org/docs/v6/ Source: https://sequelize.org/docs/v6/. Use when questions involve: advanced association concepts, category, core concepts, moved, other topics.
resend-api
Scraped from https://resend.com/docs/ Source: https://resend.com/docs. Use when questions involve: api reference, dashboard, knowledge base, webhooks.
react
Scraped from https://react.dev/ Source: https://react.dev. Use when questions involve: blog, community, docs, learn, link, reference.
remix
Scraped from https://remix.run/docs/en/main/ Source: https://remix.run/docs/en/main.
vuejs
Scraped from https://vuejs.org/guide/ Source: https://vuejs.org/guide/. Use when questions involve: best practices, built ins, components, essentials, extras, reusability.
typeorm
Scraped from https://typeorm.io/ Source: https://typeorm.io. Use when questions involve: docs.
sveltekit
Scraped from https://kit.svelte.dev/docs/ Source: https://kit.svelte.dev/docs. Use when questions involve: cli, kit, svelte.
fastapi
Scraped from https://fastapi.tiangolo.com/ Source: https://fastapi.tiangolo.com. Use when questions involve: advanced, deployment, how to, reference, tutorial.
astro
Scraped from https://docs.astro.build/ Source: https://docs.astro.build. Use when questions involve: en.
aws-cli
Scraped from https://docs.aws.amazon.com/cli/latest/userguide/ Source: https://docs.aws.amazon.com/cli/latest/userguide/.
cortex-docs
Scraped from https://docs.cortex.io/ Source: https://docs.cortex.io/. Use when questions involve: api, configure, docs, get started, guides, improve.
django
Scraped from https://docs.djangoproject.com/en/5.0/ Source: https://docs.djangoproject.com/en/5.0/. Use when questions involve: auth, class based views, contrib, contributing, db, deployment.
docker-docs
Scraped from https://docs.docker.com/ Source: https://docs.docker.com. Use when questions involve: accounts, admin, ai, billing, build, build cloud.
drizzle-orm
Scraped from https://orm.drizzle.team/docs/overview/ Source: https://orm.drizzle.team/docs/overview.
elysia
Scraped from https://elysia.dev/introduction/ Source: https://elysia.dev/introduction.
expressjs
Scraped from https://expressjs.com/ Source: https://expressjs.com. Use when questions involve: 2024, 2025, de, en, es, fr.
flask-docs
Scraped from https://flask.palletsprojects.com/en/stable/ Source: https://flask.palletsprojects.com/en/stable/. Use when questions involve: patterns, tutorial.
github-rest-api
Scraped from https://docs.github.com/en/rest/ Source: https://docs.github.com/en/rest. Use when questions involve: about the rest api, actions, activity, apps, authentication, billing.
google-cloud
Scraped from https://cloud.google.com/docs/ Source: https://cloud.google.com/docs. Use when questions involve: ai ml, authentication, buildpacks, enterprise, generative ai, security, terraform.
hono
Scraped from https://hono.dev/docs/ Source: https://hono.dev/docs/. Use when questions involve: api, concepts, getting started, guides, helpers, middleware.
mintlify-docs
Scraped from https://mintlify.com/docs/ Source: https://mintlify.com/docs/. Use when questions involve: agent, ai, api playground, api reference, authentication personalization, components.
nextjs
Scraped from https://nextjs.org/docs/ Source: https://nextjs.org/docs. Use when questions involve: app, architecture, community, messages, pages.
openai-api
Scraped from https://docs.openai.com/ Source: https://docs.openai.com.
react-native-docs
Scraped from https://reactnative.dev/docs/ Source: https://reactnative.dev/docs/. Use when questions involve: releases, the new architecture.
angular
Scraped from https://angular.dev/overview/ Source: https://angular.dev/overview.
anthropic-api
Scraped from https://docs.anthropic.com/ Source: https://docs.anthropic.com.
Page 1347 of 1571 · 78541 results
