Discover Documentation skills, compare source repositories and read the instructions for each workflow.
Apply throwaway prototyping methodology when exploring new concepts, unfamiliar technology, or unclear requirements. Build fast, learn deeply, then rebuild properly. Use for feasibility studies, proof-of-concep...
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 mitigation...
Use when analyzing requirements or project specifications - guides shannon analyze command, explains 8D complexity output, caching behavior, context-aware mode with --project flag
Validates task completion by checking for real implementation, working code, test results, and compliance with quality standards. Prevents paper solutions and ensures tasks are actually completed before being m...
Search GitHub Issues and PRs with 30+ qualifiers including labels, dates, users, state, milestones, and content. Use when searching for issues by keywords, metadata, or complex filters.
Generate comprehensive lab member rosters in both markdown and CSV formats. Analyzes member profiles, git history, and alumni information to create detailed rosters with role transitions, team assignments, and...
Read Jira tickets, extract requirements, summarize in developer-friendly format, optionally search codebase for related files, and update ticket status with transitions
Execute approved task specifications sequentially with TDD, comprehensive testing, and validation. This skill should be used for implementing tasks from approved specs with full audit trail.
Assess non-functional requirements across 6 quality categories (Security, Performance, Reliability, Maintainability, Scalability, Usability) with measurable criteria, evidence-based evaluation, and automated ch...
Implement features from task specifications using Test-Driven Development (TDD) with bmad-commands for file operations and testing. This skill should be used when implementing new functionality from approved ta...
Generate a concise end-of-day summary from GitHub activity in the last 24 hours - commits, issues, and PRs
Create comprehensive bidirectional requirements traceability matrix mapping acceptance criteria → implementation → tests with gap analysis, severity ratings, and coverage assessment. Maps each AC to implementat...
Step back and critically reassess project state. Use when asked to "assess", "step back", "fresh eyes", "check alignment", "sanity check", "health check", or "evaluate what's working". Offer to run after major...
Execute Agile methodologies effectively through sprint planning, retrospectives, and ceremony facilitation.
Categorize review feedback into P0/P1/P2 priorities
MCP Agent Mail - mail-like coordination layer for coding agents with memorable identities, inbox/outbox, searchable threads, advisory file reservations, pre-commit guards, and human-auditable Git artifacts. The...
중단된 워크플로우 재개. Use when (1) 일시정지된 워크플로우 계속, (2) 세션 복구 후 워크플로우 재시작, (3) 이전 진행 상황에서 계속.
Synthesize all Scout-phase analyses (build-inspector, runtime-inspector, git-forensics, concept-modeler) into a decision-ready system risk report.
Mind mapping and exploration state tracking for workshops. Use to maintain awareness of explored vs uncharted territory, implement backtracking, and ensure comprehensive coverage or documented gaps.
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
Complete SaaS ideation to implementation workflow - from idea discovery to task breakdown
Execute all tasks from task breakdown to build feature according to plan
ワークフローのエラーに対応するスキルです。エラーの確認、再現、原因特定、対処、検証を体系的に行い、依頼者に説明します。ワークフローの失敗やCI/CDエラーへの対応を依頼された場合に使用してください。
Comprehensive EVE Online project management and ESI integration toolkit. Use when updating, auditing, or integrating ESI into EVE Online projects like EVE_Rebellion, EVE_Gatekeeper, EVE_Ships, or any EVE-relate...
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.