EffortlessMetrics

Review system calibration from run data in RUN_BASE. Use when analyzing patterns across runs for improvement opportunities, triggered by Wisdom flow or manual review.

Review new dependencies for security and maintenance risk. Use when adding or updating dependencies.

Ensure safe deployments with rollback planning. Use when preparing deployments or reviewing deploy readiness.

Plan and document deprecations with staged lifecycle, migration guide, and tooling requirements. Use when deprecating or breaking compatibility.

Route known failure patterns to standard fixes. Use when matching error signatures to detour catalog.

Classify and route errors by category (transient, permanent, retriable, fatal). Use when diagnosing failures, deciding retry vs escalate, or triggering circuit breaker.

Turn claims into evidence-bound verification. Use when validating tests/lint/security claims, gate decisions, or reviewer checklists.

Safe git operations for branch management and history. Use when working with branches, commits, or repo operations.

Load perl-lsp coding standards for code-writing or code-review work in this repo. Use when implementing, fixing, reviewing, or validating code.

Merge approved PRs in safe batches — checks CI, fixes policy failures, handles conflicts, ratchets corpus after parser merges.

Run a TDD parser-fix workflow for perl-parser-core or related parser crates. Use when a parser bug has a concrete failing construct and needs tests, a minimal fix, and verification.

Turn a discovery into a builder-ready handoff packet. Use when a scout or coordinator has identified a concrete slice and needs exact scope, verification, and routing rather than code changes.

Research-first workflow that scouts exact scope before launching a constrained builder. Use when a feature or fix is too unconstrained for a direct builder — converts ~50% success into ~90% by eliminating implicit decisions.

Load roadmap weighting for scouts and coordinators so slices are ranked by actual repo priorities instead of convenience.

Load shared swarm behavioral rules for coordinators and workers. Use for task routing, receipts, direct messaging, dedup, worktree boundaries, and lifecycle discipline.

Start a continuous swarm with agent teams. Orchestrator-only skill.

Run the relevant tests for the current change and summarize results. Use in Flow 3 (Build) and optionally in Flow 5 (Gate).

Run linters/formatters on changed files and apply safe, mechanical fixes. Use in Flow 3 and Flow 4.

Open questions register. Use for: QID generation, OQ-SIG-001 format IDs, append questions, open_questions.md. Generate sequential QIDs, append questions with context. Use in clarifier when registering open questions instead of guessing. Invoke via bash .claude/scripts/demoswarm.sh openq next-id|append.

Run policy-as-code checks (e.g., OPA/Conftest) based on the policy_plan. Use in Flow 2 and Flow 4.

Grep/wc replacement for .runs artifacts. Use for: count, extract, Machine Summary, receipt reading, marker counts. Null-safe counting (REQ/NFR/QID/RSK markers), YAML block parsing, BDD scenario counting. Deterministic read-only - no judgment. Use when cleanup agents need mechanical counts/extraction. Invoke via bash .claude/scripts/demoswarm.sh.

Update index.json status. Use for: upsert index.json, update status/last_flow/updated_at. Deterministic writes - stable diffs, no creation. Use only in run-prep and *-cleanup agents. Invoke via bash .claude/scripts/demoswarm.sh index upsert-status.

Publish gate secrets scanning. Use for: safe_to_publish, scan for secrets, redact in-place. Determines publish gate status. Scan files for secrets (locations only - NEVER prints secret content). GitHub tokens, AWS keys, private keys, bearer tokens. Use ONLY in secrets-sanitizer. Invoke via bash .claude/scripts/demoswarm.sh secrets scan|redact.

AC-first feature development workflow for the Rust-as-Spec platform cell. Use when implementing new features, adding ACs, or working on tasks with status=Todo. Follows the ac_first flow from devex_flows.yaml and uses xtask + /platform APIs for governance.

Diagnose and fix selftest failures in the Rust-as-Spec platform cell. Use when cargo xtask selftest fails, when user reports "governance broken", or when policy violations are detected. Systematically isolates and resolves issues across the 7 selftest steps.

Platform upkeep, dependency updates, policy fixes, and doc maintenance for the Rust-as-Spec platform cell. Use when fixing governance drift, updating dependencies, resolving policy violations, or maintaining documentation. Follows the maintenance flow from devex_flows.yaml.

Version management and release tagging for the Rust-as-Spec platform cell. Use when cutting a new version, preparing for production deployment, or when user explicitly requests a release. Follows the release flow from devex_flows.yaml. IMPORTANT: Always ask user before tagging (high-risk operation).

One-command environment setup and health check for the Rust-as-Spec platform cell. Use when first entering the repository, after major environment changes, or when the environment appears broken. Follows the 'onboarding' flow from _flows.yaml.

Run linters/formatters on changed files and apply safe, mechanical fixes. Use in Flow 3 and Flow 4.

Diagnose and repair selftest failures by running diagnostic commands and proposing fixes

Run policy-as-code checks (e.g., OPA/Conftest) based on the policy_plan. Use in Flow 2 and Flow 4.

Run the relevant tests for the current change and summarize results. Use in Flow 3 (Build) and optionally in Flow 4 (Gate).

Break down a large task into smaller, actionable steps

Prepare a pull request summary and identify risks

Generate a detailed receipt or log of the work completed

Use this when a task explicitly involves moving work between EffortlessMetrics/adze, adze-dev, and adze-swarm — promoting swarm work to public, syncing external PRs back, or migrating between repos. Do not use for normal work inside a single repo.