sacco-skills

Structured evaluation framework for cloud architecture and infrastructure decisions. Use when choosing between technical approaches, evaluating build-vs-buy, designing cross-service integrations, selecting distribution mechanisms, or any decision involving trade-offs between security, ownership, coupling, portability, and switching costs. Triggers: "how should we...", "what's the right approach for...", "evaluate options for...", architectural proposals, infrastructure design, vendor/tool selection.

Systematic codebase audit with parallel concern-specific agents and structured findings. Use for code reviews, pre-production hardening, security audits, architecture reviews, or engineering quality assessments. Produces prioritized findings with severity, file:line references, and remediation plan. Triggers: "audit", "review the code", "hardening", "production readiness", "security review", "quality assessment", "deep pass".

Framework for effective cross-team communication via GitHub issues and PRs. Use when a task requires work from another team, when hitting a boundary that isn't yours to cross, when requesting infrastructure changes, when proposing shared tooling, or when tracking cross-repo dependencies. Triggers: "we need infra to...", "this requires changes in another repo", "raise an issue for...", "write a brief for...", blocked by another team's work, cross-repo dependencies.

Contract test parity verification for system rewrites and technology migrations. Generates behavioral tests from a reference implementation, tracks RED/GREEN progress, produces parity reports. Use when rewriting a system in a new language/framework, migrating between platforms, or ensuring API compatibility. Triggers: "parity", "contract tests", "ensure compatibility", "rewrite", "migration", "port from X to Y".

Orchestration playbooks for chaining the sacco-* skills on bigger efforts. Browse with "show me the orchestration playbooks", or use one when a job spans multiple skills: a competitive research barrage feeding requirements, a full-stack rewrite (parity + phased execution), a production-hardening loop, turning a design doc into a phased plan, or coordinating shared concerns across teams/repos.