team-shinchan-devops

name	team-shinchan:devops
description	Use when you need DevOps work like CI/CD, Docker, deployment, or pipelines.
user-invocable	false

EXECUTE IMMEDIATELY

Step 1: Validate Input

If args is empty or only whitespace:
  Ask user: "What DevOps/infrastructure work would you like me to do?"
  STOP and wait for user response

If args length > 2000 characters:
  Truncate to 2000 characters
  Warn user: "Request was truncated to 2000 characters"

Step 1.5: Linear Sync — START (In Progress)

Before dispatching, run the START → In Progress transition per agents/_shared/linear-sync.md: detect a Linear issue in args/branch, confirm it with get_issue, and if real move it to In Progress. No-op if no Linear issue / Linear MCP unavailable — never block the work.

Step 2: Execute Task

Do not read further. Execute this Task NOW:

Task(
  subagent_type="team-shinchan:masao",
  model="sonnet",
  prompt=`/team-shinchan:devops has been invoked.

## DevOps/Infrastructure Request

Handle infrastructure tasks including:

| Area | Capabilities |
|------|-------------|
| CI/CD | GitHub Actions, Jenkins, GitLab CI |
| Containers | Docker, Kubernetes, docker-compose |
| Cloud | AWS, GCP, Azure configuration |
| Monitoring | Logging, metrics, alerting setup |
| Environments | Dev, staging, production configs |

## Implementation Requirements

- Follow Infrastructure as Code principles
- Include automated testing in pipelines
- Use proper secret management
- Document configuration changes
- Test locally before deploying
- Implement blue-green or canary deployments where appropriate

User request: ${args || '(Please describe the DevOps task)'}
`
)

After the Task returns successfully, run the FINISH → In Review transition per agents/_shared/linear-sync.md for the same issue (no-op if not Linear-based), then STOP.

STOP HERE. The above Task handles everything.