type: user

role: user

content:
Read and review `/Users/steve.briggs/projects/operations/terraform/iac-library/aws/storage/database-tools-db/output.tf`.

Verify:
1. All these outputs are present: `address`, `admin_password` (must have `sensitive = true`), `admin_password_secret_arn`, `admin_password_secret_name`, `admin_username`, `arn`, `availability_zone`, `db_access_security_group_arn`, `db_access_security_group_id`, `db_access_security_group_name`, `endpoint`, `hosted_zone_id`, `id`, `name`, `port`, `resource_id`, `status`
2. KMS outputs: `kms_arns`, `kms_key_ids`, `kms_replica_arn`, `kms_replica_id` — all using `one(...)` with count-gated splat syntax
3. `vault_secret_path` output referencing `vault_generic_secret.admin_credentials.path`
4. `admin_password` is marked `sensitive = true`

End with `REVIEW: ✅ APPROVED` or `REVIEW: ❌ ISSUES` with details.

userType: external

entrypoint: cli


content:
- obsidian-load: Load context from Obsidian notes in the `Claude/` directory into the current conversation.
- obsidian-save: Save current conversation context to an Obsidian note under the `Claude/` directory.
- mind:search: Search memories for specific content or patterns
- mind:stats: Show memory statistics and storage information
- mind:ask: Ask questions about memories and get context-aware answers
- mind:recent: Show recent memories and activity timeline
- mind:memory: Claude Mind - Search and manage Claude's persistent memory stored in a single portable .mv2 file
- mind:mind: Claude Mind - Search and manage Claude's persistent memory stored in a single portable .mv2 file
- superpowers:dispatching-parallel-agents: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- superpowers:test-driven-development: Use when implementing any feature or bugfix, before writing implementation code
- superpowers:systematic-debugging: Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- superpowers:executing-plans: Use when you have a written implementation plan to execute in a separate session with review checkpoints
- superpowers:using-superpowers: Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
- superpowers:using-git-worktrees: Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
- superpowers:requesting-code-review: Use when completing tasks, implementing major features, or before merging to verify work meets requirements
- superpowers:finishing-a-development-branch: Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- superpowers:brainstorming: You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- superpowers:writing-plans: Use when you have a spec or requirements for a multi-step task, before touching code
- superpowers:receiving-code-review: Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
- superpowers:verification-before-completion: Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
- superpowers:writing-skills: Use when creating new skills, editing existing skills, or verifying skills work before deployment
- superpowers:subagent-driven-development: Use when executing implementation plans with independent tasks in the current session
- update-config: Use this skill to configure the Claude Code harness via settings.json. Automated behaviors ("from now on when X", "each time X", "whenever X", "before/after X") require hooks configured in settings.json - the harness executes these, not Claude, so memory/preferences cannot fulfill them. Also use for: permissions ("allow X", "add permission", "move permission to"), env vars ("set X=Y"), hook troubleshooting, or any changes to settings.json/settings.local.json files. Examples: "allow npm commands", "add bq permission to global settings", "move permission to user settings", "set DEBUG=true", "when claude stops show X". For simple settings like theme/model, suggest the /config command.
- keybindings-help: Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify ~/.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
- verify: Verify that a code change actually does what it's supposed to by running the app and observing behavior. Use when asked to verify a PR, confirm a fix works, test a change manually, check that a feature works, or validate local changes before pushing.
- simplify: Review changed code for reuse, quality, and efficiency, then fix any issues found.
- fewer-permission-prompts: Scan your transcripts for common read-only Bash and MCP tool calls, then add a prioritized allowlist to project .claude/settings.json to reduce permission prompts.
- loop: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo). Omit the interval to let the model self-pace. - When the user wants to set up a recurring task, poll for status, or run something repeatedly on an interval (e.g. "check the deploy every 5 minutes", "keep running /babysit-prs"). Do NOT invoke for one-off tasks.
- schedule: Create, update, list, or run scheduled remote agents (routines) that execute on a cron schedule. - When the user wants to schedule a recurring remote agent, set up automated tasks, create a cron job for Claude Code, or manage their scheduled agents/routines. Also use when the user wants a one-time scheduled run ("run this once at 3pm", "remind me to check X tomorrow").
- claude-api: Build, debug, and optimize Claude API / Anthropic SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing Claude API code between Claude model versions (4.5 → 4.6, 4.6 → 4.7, retired-model replacements).
TRIGGER when: code imports `anthropic`/`@anthropic-ai/sdk`; user asks for the Claude API, Anthropic SDK, or Managed Agents; user adds/modifies/tunes a Claude feature (caching, thinking, compaction, tool use, batch, files, citations, memory) or model (Opus/Sonnet/Haiku) in a file; questions about prompt caching / cache hit rate in an Anthropic SDK project.
SKIP: file imports `openai`/other-provider SDK, filename like `*-openai.py`/`*-generic.py`, provider-neutral code, general programming/ML.
- run: Launch and drive this project's app to see a change working. Use when asked to run, start, or screenshot the app, or to confirm a change works in the real app (not just tests). First looks for a project skill that already covers launching the app; otherwise falls back to built-in patterns per project type (CLI, server, TUI, Electron, browser-driven, library).
- init: Initialize a new CLAUDE.md file with codebase documentation
- review: Review a pull request
- security-review: Complete a security review of the pending changes on the current branch

type: attachment


type: message

role: assistant

type: text

text: I'll review the output.tf file against your requirements.

service_tier: standard

attributionAgent: general-purpose

attributionPlugin: superpowers

type: assistant


Read

type: direct

speed: standard


content:
1	output "address" {
2	  value = module.database.address
3	}
4
5	output "admin_password" {
6	  sensitive = true
7	  value     = module.database.admin_password
8	}
9
10	output "admin_password_secret_arn" {
11	  value = module.database.admin_password_secret_arn
12	}
13
14	output "admin_password_secret_name" {
15	  value = module.database.admin_password_secret_name
16	}
17
18	output "admin_username" {
19	  value = module.database.admin_username
20	}
21
22	output "arn" {
23	  value = module.database.arn
24	}
25
26	output "availability_zone" {
27	  value = module.database.availability_zone
28	}
29
30	output "db_access_security_group_arn" {
31	  value = module.database.db_access_security_group_arn
32	}
33
34	output "db_access_security_group_id" {
35	  value = module.database.db_access_security_group_id
36	}
37
38	output "db_access_security_group_name" {
39	  value = module.database.db_access_security_group_name
40	}
41
42	output "endpoint" {
43	  value = module.database.endpoint
44	}
45
46	output "hosted_zone_id" {
47	  value = module.database.hosted_zone_id
48	}
49
50	output "id" {
51	  value = module.database.id
52	}
53
54	output "name" {
55	  value = module.database.name
56	}
57
58	output "port" {
59	  value = module.database.port
60	}
61
62	output "resource_id" {
63	  value = module.database.resource_id
64	}
65
66	output "status" {
67	  value = module.database.status
68	}
69
70	output "kms_arns" {
71	  value = one(module.database_kms[*].key_arns[local.kms_key_name])
72	}
73
74	output "kms_key_ids" {
75	  value = one(module.database_kms[*].key_ids[local.kms_key_name])
76	}
77
78	output "kms_replica_arn" {
79	  value = one(aws_kms_replica_key.replica_key[*].arn)
80	}
81
82	output "kms_replica_id" {
83	  value = one(aws_kms_replica_key.replica_key[*].key_id)
84	}
85
86	output "vault_secret_path" {
87	  value = vault_generic_secret.admin_credentials.path
88	}
89


text:
Perfect. Let me verify all requirements:

**Verification Results:**

1. **Required outputs present**: ✅
   - `address` - ✅ (line 1-3)
   - `admin_password` - ✅ (line 5-8)
   - `admin_password_secret_arn` - ✅ (line 10-12)
   - `admin_password_secret_name` - ✅ (line 14-16)
   - `admin_username` - ✅ (line 18-20)
   - `arn` - ✅ (line 22-24)
   - `availability_zone` - ✅ (line 26-28)
   - `db_access_security_group_arn` - ✅ (line 30-32)
   - `db_access_security_group_id` - ✅ (line 34-36)
   - `db_access_security_group_name` - ✅ (line 38-40)
   - `endpoint` - ✅ (line 42-44)
   - `hosted_zone_id` - ✅ (line 46-48)
   - `id` - ✅ (line 50-52)
   - `name` - ✅ (line 54-56)
   - `port` - ✅ (line 58-60)
   - `resource_id` - ✅ (line 62-64)
   - `status` - ✅ (line 66-68)

2. **KMS outputs with `one(...)` syntax**: ✅
   - `kms_arns` - ✅ (line 70-72) uses `one(module.database_kms[*]...)`
   - `kms_key_ids` - ✅ (line 74-76) uses `one(module.database_kms[*]...)`
   - `kms_replica_arn` - ✅ (line 78-80) uses `one(aws_kms_replica_key.replica_key[*]...)`
   - `kms_replica_id` - ✅ (line 82-84) uses `one(aws_kms_replica_key.replica_key[*]...)`

3. **Vault secret path**: ✅ (line 86-88) references `vault_generic_secret.admin_credentials.path`

4. **Admin password sensitivity**: ✅ (line 6) `sensitive = true` is set

---

**REVIEW: ✅ APPROVED**

All required outputs are present with correct configuration. KMS outputs properly use count-gated splat syntax with `one()` function. The `admin_password` output is correctly marked as sensitive. The `vault_secret_path` output correctly references the vault generic secret path.