distributed-consensus
Distributed Consensus
Overview
Use this skill when system correctness depends on multiple nodes agreeing on state transitions under crash and partition conditions.
Scope Boundaries
- Replicated writes require explicit safety/liveness guarantees.
- Quorum and leadership behavior determine correctness.
- Membership changes and failover policy must be defined safely.
Shared References
- Consensus policy rules:
references/consensus-policy-rules.md
Templates And Assets
- Consensus policy template:
assets/consensus-policy-template.md
Inputs To Gather
- Replicated state machine requirements.
- Fault model (crash, partition, byzantine assumptions).
- Latency/availability targets and quorum constraints.
- Membership change and recovery expectations.
Deliverables
- Consensus policy decisions (quorum, election, commit semantics).
- Safety/liveness assumptions and risks.
- Operational policy for split-brain and degraded mode.
- Validation plan for failover and rejoin scenarios.
Workflow
- Capture policy baseline in
assets/consensus-policy-template.md. - Define safety invariants and availability targets.
- Select quorum, leadership, and commit rules using
references/consensus-policy-rules.md. - Define partition, degraded-mode, and recovery behavior.
- Define membership change strategy and validation sequence.
- Validate with failure simulation and state convergence checks.
Quality Standard
- Safety invariants are explicit (no divergent committed state).
- Liveness tradeoffs are acknowledged under partition conditions.
- Membership changes preserve quorum guarantees.
- Recovery/rejoin behavior is deterministic and tested.
Failure Conditions
- Stop when quorum or commit semantics are undefined.
- Stop when partition behavior can cause split-brain writes.
- Escalate when membership change procedure risks safety violation.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9