approval-workflow

Automate multi-stakeholder approval routing for marketing assets with SLA tracking.

175|26|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/jmagly/ai-writing-guide --skill approval-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: approval-workflow
Source: https://github.com/jmagly/ai-writing-guide/tree/main/.factory/skills/approval-workflow
Command: npx skills add https://github.com/jmagly/ai-writing-guide --skill approval-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manages asset approvals across teams with routing, tracking, and escalation.

Core Features & Use Cases

  • Approval chains: Configurable routing by asset type and value.
  • Status tracking: Real-time approval status.
  • Escalation: Deadlines and escalation paths.

Quick Start

Route an asset through a 3-tier approval chain with auto-escalation on delay.

Frequently Asked Questions about approval-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up approval routing for marketing assets by type and budget tier?

Approval routing configures chains based on asset type and value tier. The Skill loads tier-specific approval paths, routes submissions serially, parallel, or in stages, and assigns approvers accordingly so assets follow the right chain from submission through decision.

Can I automate escalation when approval requests exceed deadlines?

Yes. The Skill enforces SLA deadlines on approval requests and automatically escalates overdue items to the next tier or designated escalation path, ensuring bottlenecked approvals move forward without manual intervention.

How do I track approval status and maintain an audit trail?

Approval tracking records each decision, response timestamp, and approver action in real-time status views. The audit trail captures the full history of routing decisions and asset approvals for compliance and archival.

What's the difference between serial, parallel, and staged approval chains?

Serial chains route to one approver at a time sequentially. Parallel sends to multiple approvers simultaneously. Staged chains group approvers into tiers that proceed in phases. The Skill supports all three routing patterns depending on asset risk and team structure.

Do I need to reconfigure approval chains for each asset type, or can I reuse templates?

Approval chains are configurable by asset type and tier, so you define templates once and reuse them. The Skill applies the matching chain automatically based on the asset's type and risk classification at submission.