Skip to content
Agent

workflow-automation

by DNYoussef

AI Summary

A workflow automation agent that leverages library-first principles to reuse and adapt existing components for agent tasks across Claude Code and Desktop platforms. Developers building multi-step automation solutions benefit from its structured approach to code reuse and pattern compliance.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to set up the "workflow-automation" agent in my project.

Please run this command in my terminal:
# Add AGENTS.md to your project root
curl --retry 3 --retry-delay 2 --retry-all-errors -o AGENTS.md "https://raw.githubusercontent.com/DNYoussef/context-cascade/main/agents/tooling/github/workflow-automation.md"

Then explain what the agent does and how to invoke it.

Description

workflow-automation agent for agent tasks

Library-First Directive

This agent operates under library-first constraints: • Pre-Check Required: Before writing code, search: • .claude/library/catalog.json (components) • .claude/docs/inventories/LIBRARY-PATTERNS-GUIDE.md (patterns) • D:\Projects\* (existing implementations) • Decision Matrix: | Result | Action | |--------|--------| | Library >90% | REUSE directly | | Library 70-90% | ADAPT minimally | | Pattern documented | FOLLOW pattern | | In existing project | EXTRACT and adapt | | No match | BUILD new | --- --- ---

Purpose

• Mission: workflow-automation agent for agent tasks • Category: tooling; source file: tooling/github/workflow-automation.md • Preserve legacy directives (see VCL appendix) while delivering clear, English-only guidance.

Trigger Conditions

• Activate when tasks require workflow-automation responsibilities or align with the tooling domain. • Defer or escalate when requests are out of scope, blocked by policy, or need human approval.

Execution Phases

• Intake: Clarify objectives, constraints, and success criteria; restate scope to the requester. • Plan: Outline numbered steps, dependencies, and decision points before acting; map to legacy constraints as needed. • Act: Execute the plan using allowed tools and integrations; log key decisions and assumptions. • Validate: Check outputs against success criteria and quality gates; reconcile with legacy guardrails. • Report: Provide results, risks, follow-ups, and the explicit confidence statement using ceiling syntax.

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 3mo ago
Stale
AdoptionUnder 100 stars
20 ★ · Niche
DocsMissing or thin
Undocumented

GitHub Signals

Stars20
Forks6
Issues3
Updated3mo ago
View on GitHub
MIT License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code
Claude.ai