Proves
Proves unitàries, d’integració i automatitzades
loom-builder-complexity
rjwalters
"This document covers complexity assessment, issue decomposition, and scope management for the Builder role. For the core builder workflow, see builder.md."
loom-cargo-target-isolation
rjwalters
"Load when: you are about to run (or just ran) a local cargo build/cargo test/cargo run whose result will inform a verdict — a Judge approval or rejection, a Doctor \"the fix works\", or a Builder \"tests pass\" before opening a PR."
loom-judge-reference
rjwalters
"Detailed reference material for the Judge role, split out of judge.md (the largest prompt in the repo) to keep the main workflow scannable — mirroring how champion.md references champion-reference.md / champion-common.md."
schematic
blader
Reverse engineer a detailed product and technical specification document from a git branch's implementation. Use when: (1) a branch has shipped or is in-progress and needs documentation, (2) you need to understand what a branch does at product and architecture level, (3) onboarding to someone else's feature branch, (4) creating PR descriptions or design docs after the fact, (5) user asks to "analyze this branch", "write a spec from the code", or "document what this branch does". Produces a structured markdown spec covering problem statement, product requirements, architecture, technical design, file inventories, testing strategy, rollout plan, and risks.
drive-new-project
p-wegner
Drive a freshly-created project hands-off to a finished multi-ticket epic — the playbook for "use the board to build a new app / implement a 10+ ticket epic" tickets. Encodes the completion CONTRACT (keep the meta-ticket In Progress until the epic is N/N Done, then drive the meta itself to Done — not parked in Review), a preflight prerequisites check, fan-out epic seeding, autodrive enablement, and a REQUIRED resident watch that recovers stalls instead of abandoning them. Use when a ticket asks you to register/scaffold a new project and take it to completion via the board.
test-coverage
Montimage
Expand unit test coverage by targeting untested branches and edge cases. Use when users ask to "increase test coverage", "add more tests", "expand unit tests", "cover edge cases", "improve test coverage", or want to identify and fill gaps in existing test suites. Adapts to project's testing framework.
coverage-intelligence
p-wegner
Build a multidimensional functional-coverage model for a software system and rank the highest-ROI verification gaps. Binds the observable-behaviour model (from behavior-discovery) against requirements (PRD/ADRs/user stories/acceptance criteria), the existing test suites (unit/integration/e2e), and historical signals (git churn, bug history) to compute — per behaviour — whether it is covered / partial / uncovered / undocumented-implemented / documented-missing, across many orthogonal coverage dimensions (capability, requirement, workflow, permission, navigation, API, error, boundary, state-transition, config, accessibility, regression, risk). Produces a coverage matrix, gap report, and an ROI-ranked test backlog. NOT line coverage. Use when the user asks "what's our real test coverage", "what behaviour is unverified", "where are the coverage gaps", "what tests give the most value", "map requirements to tests", "build a coverage model", or as phase 2 of an end-to-end verification effort.
cleanup
p-wegner
"Clean up stale agentic-kanban resources including git worktrees, Claude Code sessions, and E2E test artifacts."
java-backend-planner
p-wegner
Explore codebase in parallel with subagents, interview user on requirements and constraints, then synthesize a phased Java backend implementation plan with tech stack decisions, module structure, risks, and DevOps strategy
pywayne-tts
wangyendt
Text-to-speech conversion tool. Use when converting text to speech audio files (opus or mp3 format). Supports macOS native 'say' command and Google TTS (gTTS) service with ffmpeg audio conversion.
behavior-discovery
p-wegner
Build a high-confidence model of a software system's EXTERNALLY OBSERVABLE behaviour — capabilities, actors, permissions, entry points, workflows, state transitions and error states — by combining many evidence sources (domain docs, OpenAPI/GraphQL schemas, source, routing, running-UI exploration, existing tests, git history) and degrading gracefully when some are absent. Infers business semantics; never paraphrases code. Marks unknowns explicitly instead of guessing. Output is the shared _behavior-model.json that the coverage-intelligence and e2e-test-author skills consume. Use when the user asks to "model what the app does", "discover observable behaviour", "build a verification/behaviour model", "explore the running app and map its capabilities", or as phase 1 of an end-to-end verification effort.
quality-metrics-collector
p-wegner
Collect repository code-health metrics and POST them to the board Quality Metrics API
count-code-lines
p-wegner
Count productive code lines per package using scc, scoped to actual source directories
architecture-review
p-wegner
Exhaustive architecture review — spawns parallel analysis agents, synthesizes findings, and creates kanban tickets for the top weaknesses
flaky-test-triage
p-wegner
Classify a failing test as known-flaky vs real regression, then re-run with the right strategy instead of debugging flakes or wrongly dismissing real failures
robotframework-testcase-builder
manykarim
Generate Robot Framework test cases from structured requirements or scenarios. Use when asked to create test cases, apply tags/setup/teardown/templates, or produce keyword-driven tests.
pywayne-plot
wangyendt
Enhanced spectrogram visualization tools for time-frequency analysis. Use when creating spectrograms, spectral analysis, or time-frequency plots for signals including IMU data (accelerometer, gyroscope), physiological signals (PPG, ECG, respiration), vibration analysis, and audio processing. Supports frequency unit conversion (Hz/bpm/kHz), multiple normalization modes (global/local/none), and MATLAB-style parula colormap.
e2e-test-author
p-wegner
Generate the highest-ROI end-to-end tests from a prioritized coverage-gap backlog, then subject them to an adversarial review that tries to REFUTE them before they land. Consumes the verification model (_priorities.md / _coverage.json from coverage-intelligence), authors complete user-workflow tests (not isolated clicks) using the target project's own anti-flake conventions, makes each test DECLARE the coverage dimensions it contributes, runs independent adversarial reviewer subagents (overfitted assertions, flaky interactions, false positives, missed edge cases), fixes what they find, and writes the new coverage back into the model so re-running the pipeline improves. Use when the user asks to "write the missing tests", "generate high-value e2e tests", "author tests for the coverage gaps", "close the top coverage gaps", or as phase 3 of an end-to-end verification effort. For a single ad-hoc test in agentic-kanban use the project e2e-author skill instead; this skill is the gap-driven, reviewed, batch author.
pywayne-statistics
wangyendt
Comprehensive statistical testing library with 37+ methods for normality tests, location tests, correlation tests, time series tests, and model diagnostics. Use when performing hypothesis testing, A/B testing, data quality checks, time series analysis, or regression model validation. All methods return unified TestResult objects with consistent interface including p-value, statistic, confidence interval, and effect size.
springboot-verification
xu-xiang
Spring Boot 项目的验证循环（Verification loop）：包含构建、静态分析、带覆盖率的测试、安全扫描，以及在发布或 PR 前的差异评审（diff review）。
django-tdd
xu-xiang
使用 pytest-django、测试驱动开发（TDD）方法论、factory_boy、Mock 模拟、覆盖率统计以及 Django REST Framework API 测试的 Django 测试策略。
golang-testing
xu-xiang
Go 测试模式，包括表格驱动测试、子测试、基准测试、模糊测试和测试覆盖率。遵循测试驱动开发（TDD）方法论及地道的 Go 语言实践。
python-testing
xu-xiang
使用 pytest、TDD 方法论、fixtures、mocking、参数化和代码覆盖率要求的 Python 测试策略。
tdd-workflow
xu-xiang
Use this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.