bundles/infrastructure/skills/workflow-automation/SKILL.md
This skill should be used when users need help designing content workflows, creating process documentation, implementing automation rules, designing approval processes, or optimizing content pipelines. It activates when users ask about workflow design, process documentation, automation, approval workflows, or content pipeline optimization.
npx skillsauth add shipshitdev/library workflow-automationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
This skill helps design and implement content workflows, create process documentation, suggest automation rules, document approval processes, and optimize content pipelines for efficiency and quality.
This skill activates automatically when users:
To design effective content workflows:
Understand Current Process
Design Optimal Workflow
Document Workflow
Example User Request: "Design a content workflow for my team that includes approval steps"
Integration (discover from project):
To create comprehensive process documentation:
Document Content Processes
Create Visual Flowcharts
Maintain Documentation
Example User Request: "Create a flowchart for my content creation process"
Integration (discover from project):
To suggest and implement automation rules:
Identify Automation Opportunities
Design Automation Rules
Implement Automation
Example User Request: "What parts of my content workflow can be automated?"
Integration (discover from project):
To design content approval workflows:
Define Approval Requirements
Design Approval Workflow
Implement Approval System
Example User Request: "Design an approval workflow where content needs manager approval before publishing"
Integration (discover from project):
To optimize content pipelines for efficiency:
Analyze Current Pipeline
Optimize Pipeline
Monitor and Improve
Example User Request: "Help me optimize my content pipeline to reduce time from ideation to publishing"
Integration (discover from project):
Before designing workflows, discover the project's context:
Scan Project Documentation:
.agents/memory/ for workflow architecture and existing process documentationIdentify Workflow Components:
Common Content Workflow:
Trend Detection (Extension) → Content Generation (Creation Tools) →
Distribution (Publishing Platform) → Analytics (Analytics Platform) → Optimization
Workflow Components:
Automation Opportunities:
workflow-design-guide.md: Best practices for workflow designautomation-patterns.md: Common automation patterns and examplesapproval-workflow-examples.md: Approval workflow templates and examplesworkflow-template.md: Template for documenting workflowsprocess-flowchart-template.md: Template for creating process flowchartsautomation-rule-template.md: Template for defining automation rulesdevelopment
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
development
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
development
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
tools
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.