メニュー
Map application-layer AWS resources (ECS, Lambda, ALB, API Gateway) and write a topology to AWS_STATE_DIR.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | aws-scan-apps |
| description | Map application-layer AWS resources (ECS, Lambda, ALB, API Gateway) and write a topology to AWS_STATE_DIR. |
| model | sonnet |
| effort | medium |
| context | fork |
ASA-1. Verify prerequisites.
ASA-2. Enumerate (pass --profile $AWS_PROFILE --region $AWS_DEFAULT_REGION):
aws lambda list-functionsaws elbv2 describe-load-balancersaws apigateway get-rest-apisaws apigatewayv2 get-apisaws cloudfront list-distributions
ASA-3. Build topology: entry points (ALB/API GW/CloudFront) → compute (ECS/Lambda).
ASA-4. Write raw data to $AWS_STATE_DIR/apps-<YYYYMMDD>.json.
ASA-5. Write human-readable summary to $AWS_STATE_DIR/apps-<YYYYMMDD>.md:Skip if $AWS_STATE_DIR/apps-<YYYYMMDD>.json exists and is less than 4 hours old.
Conduct a decision-tree interview with the user to lock in requirements, motivation, scope, and non-goals before planning.
Stage 3 of three-stage planning pipeline. Produce a file-level implementation plan via detail-planner/detail-reviewer loop, then get user approval. Inputs are confirmed intent (<session-id>-intent.md) and outline (<session-id>-outline.md) from prior stages.
Edit source code for the current task. Delegates editing and lint/typecheck/self-repair to a subagent.
Plan and write test cases with high reasoning effort. Test iteration runs in a subagent to minimize confirmations.
Explore the codebase to understand existing patterns, constraints, and relevant files before planning.
Investigate git history, docs/history.md, and GitHub issue/PR timeline since the relevant issue opened, to surface changes that may invalidate the issue's premises.