workflow-automation
Workflow Automation
Use this skill when the main question is "what is the smallest repeatable automation layer this repo needs, and how should it wrap the tools we already have?"
The job is not to dump a giant Makefile, ten shell scripts, and a random GitHub Actions example. The job is to:
- classify the recurring workflow,
- choose the right automation surface,
- keep repo-local glue separate from environment provisioning and deployment,
- make automation idempotent and non-interactive,
- return a workflow packet another engineer or agent can apply immediately.
Read references/automation-modes.md before designing or refactoring a workflow layer.
Read references/handoff-boundaries.md when deciding whether workflow-automation, system-environment-setup, deployment-automation, git-workflow, testing-strategies, or monitoring-observability should own the next step.
More from akillness/skills-template
backend-testing
>
71data-analysis
>
54plannotator
>
35task-planning
Plan and organize software development tasks effectively. Use when breaking down features, creating user stories, or planning sprints. Handles task breakdown, user stories, acceptance criteria, and backlog management.
35omc
Use when you need Teams-first multi-agent orchestration in Claude Code. Triggers on: omc, autopilot, ralph, ulw, ccg, team. 29+ specialized agents, smart model routing (Haiku→Opus), persistent execution loops, skill layers, real-time HUD.
33vibe-kanban
Manage AI coding agents on a visual Kanban board. Run parallel agents through a To Do→In Progress→Review→Done flow with automatic git worktree isolation and GitHub PR creation.
32