shield

Analyze terraform plan output for security, cost, and destructive action impact

Start TDD-based feature implementation with progress tracking

Set up Shield for a new project — creates .shield.json and ~/.shield/ config structure

Migrate from old plugins (infra-review, clickup-sprint-planner, dev-workflow) to Shield

Run multi-agent plan review with scored analysis

Generate plan documents — architecture/ADR docs and detailed execution plans with stories, plus a JSON sidecar for project management sync

Show sprint/epic status overview from your PM tool

Sync plan stories to your PM tool (ClickUp, Jira, etc.)

Research a technical topic with structured citations and expert sources

Run cost optimization review with the cost reviewer agent

Run security-focused review with the security reviewer agent

Run AWS Well-Architected Framework review across all 6 pillars

Run comprehensive code review with domain-specific agents and AC verification

Use this agent when evaluating sprint-readiness, story quality, sizing, dependency ordering, or acceptance criteria testability. Always dispatch for plans with stories.

Use this agent when reviewing service topology, scalability, high availability, network design, Terraform component structure, or Atmos integration patterns. Dispatch for plan reviews or infrastructure code reviews.

Use this agent when reviewing cost optimization — resource right-sizing, environment tiering, NAT gateway patterns, expensive resource toggles, and FinOps best practices. Dispatch for plan reviews or infrastructure code reviews.

Use this agent when evaluating plan clarity, actionability, software architecture quality, or developer experience. Always dispatch for plans with stories.

Use this agent when reviewing operational readiness — monitoring, logging, failure modes, backup strategy, capacity planning, tagging, blast radius, and day-2 operations. Dispatch for plan reviews or infrastructure code reviews.

Use this agent when evaluating user impact, scope discipline, prioritization, business value alignment, or stakeholder communicability. Dispatch for research framing, research review, plan review, or standalone product analysis.

Use this agent when reviewing security posture — IAM policies, encryption, network exposure, threat modeling, access control, and compliance alignment. Dispatch for plan reviews or infrastructure code reviews.

Use this agent for a holistic infra-code review using the AWS Well-Architected Framework across all 6 pillars: Operational Excellence, Security, Reliability, Performance Efficiency, Cost Optimization, and Sustainability. Dispatch for architecture decision reviews, production readiness gates, or when evaluating overall infrastructure code quality against AWS best practices.

Use when analyzing Terraform plan output for security, cost, and operational impact — parses terraform plan JSON to surface destructive changes, IAM modifications, cost-impacting resources, and drift before apply

Use when auditing Terraform code for security vulnerabilities, reviewing IAM policies, checking encryption, or validating network isolation in AWS components

Use when reviewing Terraform test files (.tftest.hcl), assessing test coverage, or designing new tests for components using mock_provider and plan-only assertions

Use when any workflow needs a product lens — user impact analysis, prioritization, scope discipline, or stakeholder framing. Triggers on product analysis, PM review, user impact, business value.

Use when comparing approaches, evaluating tools, building evidence-based decisions, or the user needs citations and industry backing. Triggers on /research, investigate, compare, evaluate.

Use when code changes need review for security, cost, architecture, or acceptance criteria verification. Triggers on /review, after implementation, pre-merge.

Use when a pipeline phase completes and needs an audit trail summary. Called by other skills, not directly by users.

Use when reviewing, auditing, or improving GitHub Actions workflows in a repository — checks for version drift, permission issues, missing concurrency controls, path filter gaps, and cross-workflow inconsistencies

Use when the user asks about sprint planning, syncing plan docs to a PM tool, managing stories/tasks in bulk, or checking sprint status. Triggers on mentions of sprint, sync, stories, PM bulk operations, or epic planning.

Use when reviewing Terraform components for AWS cost optimization, right-sizing, or identifying unnecessary expensive resources like NAT gateways or over-provisioned subnets

Use when reviewing Atmos infrastructure repositories, evaluating IaC structure, or assessing components/stacks organization for quality and best practices

Use when adding, modifying, or reviewing Terraform components in an Atmos components repository - checks for common mistakes like committed provider.tf, missing terraform-docs, broken linting config, or missing baseline variables

Use when a skill needs step tracking, progress visibility, and resume support within a single phase. Called by skills, not directly by users.

Use when implementing a feature or story, especially with acceptance criteria to verify. Triggers on /implement, build, create feature, add functionality.

Use when breaking down a project phase into stories with acceptance criteria, creating ADRs, or planning infrastructure work. Triggers on /plan, story breakdown, detailed plan, architecture doc.

Use when a plan, architecture doc, or execution plan exists and needs expert review before implementation. Triggers on /plan-review, review my plan, document review.

2 hooks across 2 events