req-nf-inf-cloud-services

Creates and updates AWS service design documents with roles, responsibilities, and operational workflows.

Updated May 18, 2026
One-click install
npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill req-nf-inf-cloud-services
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: req-nf-inf-cloud-services
Source: https://github.com/ABLER-Digital-Services/ai-guild/tree/main/skills/req-nf-inf-cloud-services
Command: npx skills add https://github.com/ABLER-Digital-Services/ai-guild --skill req-nf-inf-cloud-services

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps you create and maintain a cloud services design document that specifies AWS account design, service selections, and resource configurations so teams can align on a secure, reusable foundation.

Core Features & Use Cases

  • Cloud services design document authoring: Produces a structured “基盤概要設計_クラウドサービス編” covering design policy, AWS account strategy, and the full set of AWS services used.
  • Consistent AWS service & resource definition: Defines each AWS service section (e.g., VPC, EC2/Auto Scaling, ECS/Fargate, RDS, S3, CloudFront, Route 53, WAF, IAM, Secrets Manager, CloudWatch, SES, SQS, ECR, AWS Backup) with clear “概要” and system-specific “用途.”
  • Review-oriented output: Includes an explicit review checklist to confirm alignment across design policy, account design, security-related services, and system configuration diagrams.

Quick Start

Use this skill when you are asked to create or update “基盤概要設計_クラウドサービス編(クラウドサービス編)” and to organize and define the AWS services and resources for the target system.

Frequently Asked Questions about req-nf-inf-cloud-services

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a cloud services design document for AWS?▼

To create an AWS cloud services design document, define design policy, account strategy, service scope, and resource configuration, then generate structured per-service sections and a security review checklist.

What should be included in AWS account design and service scope documentation?▼

AWS account design documentation should include design policy, account strategy, per-service sections detailing usage, resource inventory, and a review checklist confirming security alignment and consistency.

How do I organize existing AWS service and resource configurations into a structured document?▼

Organize existing AWS service configurations by compiling a resource inventory, defining per-service usage, and structuring them into a cloud services design document with a review checklist.

Can I define detailed configurations for specific AWS services like VPC, ECS, and RDS in one document?▼

Yes, you can define detailed configurations for AWS services like VPC, EC2, ECS, RDS, S3, IAM, and CloudWatch in one document by generating structured per-service sections with clear usage definitions.

Does the AWS cloud services design document include a security and consistency review checklist?▼

Yes, the AWS cloud services design document includes an explicit review checklist to confirm alignment across design policy, account design, security-related services, and system configuration diagrams.

What is the best way to define AWS service usage for a new system foundation?▼

The best way to define AWS service usage is to generate a structured design document covering design policy, account strategy, and per-service sections with system-specific usage and resource inventory.