← All skill packs

Cloud & DevOps Workflows

Skill pack
3 skills0 selected
craigspatersonSkills in this pack

Uploads a drafted User Story or Technical Story to Azure DevOps as a work item, populating Title, Description, Acceptance Criteria, Story Points, Priority, and optionally linking a parent feature. Also supports creating a full Epic → Feature → Story hierarchy from a structured backlog, and updating existing work items in bulk. Use when the user says "push to ADO", "create in ADO", "upload to ADO", "add to ADO", "update ADO items", or similar after stories have been drafted in conversation.

English

Draft Jira-formatted Technical Stories (Infrastructure and Application sub-types) with Acceptance Criteria, for backlog items that describe a system or engineering concern rather than a user experience. Use this skill whenever the user wants to write, create, draft, refine, or improve a technical story, enabler story, engineering story, infra story, or any PBI describing IaC provisioning, GitHub Actions / CI-CD workflows, Cloud Run or other cloud resource deployment, IAM / service-account configuration, Artifact Registry publishing, or backend service/function logic. Trigger even for casual phrasing like "write a story for provisioning a Cloud Run service", "create a ticket for the OpenTofu apply workflow", "story for the IAM bindings", or "turn this infra task into a story". Use the user-story skill instead when the PBI describes a human-facing feature, UI, or classic user experience. If unsure which kind of story applies, this skill includes guidance to decide.

English

Generate Terraform docs and inject them into terraform/README.md using terraform-docs markdown table output-mode inject. Use when the user asks to refresh, regenerate, or update Terraform documentation or README.

English

Includes Push to Ado, Technical Story, and Terraform Docs Inject.

Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI

Supported by the Atlas install prompt. Skill-specific requirements vary.

Pack stats

Skills3CategoryengineeringStars0

What’s included

Push to Ado

Uploads a drafted User Story or Technical Story to Azure DevOps as a work item, populating Title, Description, Acceptance Criteria, Story Points, Priority, and optionally linking a parent feature. Also supports creating a full Epic → Feature → Story hierarchy from a structured backlog, and updating existing work items in bulk. Use when the user says "push to ADO", "create in ADO", "upload to ADO", "add to ADO", "update ADO items", or similar after stories have been drafted in conversation.

Technical Story

Draft Jira-formatted Technical Stories (Infrastructure and Application sub-types) with Acceptance Criteria, for backlog items that describe a system or engineering concern rather than a user experience. Use this skill whenever the user wants to write, create, draft, refine, or improve a technical story, enabler story, engineering story, infra story, or any PBI describing IaC provisioning, GitHub Actions / CI-CD workflows, Cloud Run or other cloud resource deployment, IAM / service-account configuration, Artifact Registry publishing, or backend service/function logic. Trigger even for casual phrasing like "write a story for provisioning a Cloud Run service", "create a ticket for the OpenTofu apply workflow", "story for the IAM bindings", or "turn this infra task into a story". Use the user-story skill instead when the PBI describes a human-facing feature, UI, or classic user experience. If unsure which kind of story applies, this skill includes guidance to decide.

Terraform Docs Inject

Generate Terraform docs and inject them into terraform/README.md using terraform-docs markdown table output-mode inject. Use when the user asks to refresh, regenerate, or update Terraform documentation or README.

Quick start

  1. Choose your skills. Select individual skills above, or choose the entire pack.
  2. Copy the install prompt. Use Copy install prompt above the list.
  3. Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.

Try it with your agent

After installation, start with a request like:

Example request
Use the Push to Ado skill to help with my task.
Ask me for the context you need before getting started.

Requirements & license

  • A coding agent that can access your project files and install skills.
  • Your agent checks each skill’s instructions, dependencies, and permissions during setup.
  • Reported license for the skills shown: MIT. The author’s terms apply.