aws-manifest

To generate an AWS infrastructure manifest, you need to document your resource requirements in a standardized format. This skill creates a structured `docs/aws-manifest.md` file by gathering project context and infrastructure details through interactive prompts, ready for Terraform.

When documenting AWS infrastructure requirements, this skill supports static-site, api, fullstack, worker, and data-pipeline application types. It determines your application type during the interactive collection process to format the output accurately.

The best way to standardize AWS infrastructure documentation is to generate a manifest file adhering to a defined specification. This skill produces a consistent `docs/aws-manifest.md` file detailing cloud resources, ensuring your infrastructure team has uniform provisioning requirements.

To create a Terraform manifest file for a new fullstack application, this skill gathers your project context and infrastructure details interactively. It formats the collected data into an AWS application manifest file for provisioning the necessary cloud resources.

You do not need to manually write AWS resource configurations before generating a manifest. The skill interacts with you to collect the necessary infrastructure details and automatically formats the output according to the specification, eliminating manual documentation efforts.

Yes, you can use this manifest generation process for data-pipeline provisioning. The skill explicitly supports data-pipeline application types, gathering the specific infrastructure details required to document resources for your data pipelines.