Validate implementation approaches against Brief decisions

Capture architectural and implementation decisions with rationale to prevent re-debating. Creates and maintains DECISIONS.md.

A decision matrix is a structured tool for comparing multiple alternatives against weighted criteria to make transparent, defensible choices. It forces explicit trade-off analysis by scoring each opti

Create or update a structured decision record

Facilitate data-driven technical decisions using embedded decision matrices and trade-off analysis. Use when relevant to the task.

Git-powered state awareness - track file changes, session context, decisions, and work history. Query what happened in previous sessions and during current session. Auto-activates for state queries and before duplicating work.

Strategic decision-making for CFN Loop progression with robust parsing. Use when evaluating validator consensus and determining PROCEED/ITERATE/ABORT outcomes.

Use when starting plan execution to decompose implementation plans into Claude Code Task tool tasks at H2 (Task) granularity - creates one task per plan task with citation-manager directives, keeping plan as source of truth

Use after writing-plans to decompose monolithic plan into individual task files and identify tasks that can run in parallel (up to 2 subagents simultaneously)

Deep learning-based variant calling with Google DeepVariant. Provides high accuracy for germline SNPs and indels from Illumina, PacBio, and ONT data. Use when calling variants with DeepVariant deep learning caller.

Creates and manages multi-step AI workflows. Use when defining, implementing, or improving DeepWork jobs.

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

Delete files from knowledge base with directory governance. Use when user wants to remove or delete content. Reads RULE.md to check deletion permissions and handles dependencies.

Delta Sharing configuration, monitoring, and recipient management for secure cross-organization data sharing.

Automated dependency management with security scanning, update orchestration, and compatibility validation

>

Manage Python dependencies using uv package manager. Use when installing, adding, removing, or updating packages. Always prefer uv over pip.

Map, track, and manage project dependencies across teams, systems, and organizations. Identify critical path items and prevent blocking issues through proactive dependency management.

deploy-service

Deployment workflow for company repos (pre/pro) using CI, ECR, and Helm.

Set up progressive canary deployments on GCP Cloud Run with traffic splitting, monitoring alerts, and automated rollback.

Production deployment principles and decision-making. Safe deployment workflows, rollback strategies, and verification. Teaches thinking, not scripts.

Azure Deployment Stacks GA 2025 features for unified resource management, deny settings, and lifecycle management

Deployment Strategy Agent. Feature Flag, Canary/Blue-Green 배포, 롤백 전략을 담당합니다. 안전한 배포와 점진적 롤아웃을 관리합니다.

**Purpose**: Systematically validate the application is ready for production deployment, catching common "works locally, fails on Render" issues BEFORE they happen.

deployment-verification

Deep knowledge of legendary designers and their enduring contributions. Learn from Saul Bass, Massimo Vignelli, Dieter Rams, Paula Scher, and others whose work defines excellence. Use when seeking inspiration, understanding design history, or applying proven approaches.

Auto-activates when synthesizing outputs from multiple parallel sub-agents

Detect empty catch blocks and exception swallowing anti-patterns. Finds catch blocks that silently ignore errors without logging or rethrowing. Works across all languages. Use when user asks about error handling issues.

Analyze git changes to determine release scope (marketplace/plugin/variants)

Utilities and patterns for detecting execution environment (CI/CD vs local, network access, available ports, timeouts). Use when you need to adapt scripts or workflows based on where the agent is running, or when creating helper scripts that need environment-aware behavior.

Detects OS command injection vulnerabilities by identifying unsafe system/popen/exec calls with user-controlled input. Use when analyzing command execution, shell operations, or investigating potential command injection points.

Detects logic bypass vulnerabilities including authentication bypass, authorization bypass, and business logic flaws. Use when analyzing authentication mechanisms, access controls, or investigating security control bypasses.

detection

Browser automation that maintains page state across script executions. Write small, focused scripts to accomplish tasks incrementally. Once you've proven out part of a workflow and there is repeated w

Package and dependency management patterns across ecosystems (npm, pip, cargo, maven). Covers lockfiles, semantic versioning, dependency security scanning, update strategies, monorepo workspaces, transitive dependencies, and avoiding dependency hell.

Run isolated mux desktop (Electron) instances (temp MUX_ROOT + free ports)

ring:dev-devops

Manage Jeremy's global dev environment (git, nvim, shell configs) and install tools. Use when asked to change global configs, add tools to the environment, or modify dotfiles.

Standardized development environment configuration including tools, IDE settings, and automation for consistent developer experience.

Development Philosophy & Standards. Use it everytime you plan or implement any code.

Create an isolated git worktree for feature work, ensuring workspace isolation and clean baseline.

执行单个开发任务的工作流指导，采用自顶向下开发模式和分层 TDD。

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->

MUST BE USED for code implementation. Use PROACTIVELY when /implement or /fix commands are invoked, or when coding tasks need execution.

IDE setup, dev containers, and local development tools

Development Workflow Orchestrator

Handle unexpected work during execution. Use when encountering bugs, missing features, blockers, or architectural changes while executing a plan. Not for initial planning or non-execution contexts.

>-