frappe-impl-workflow

Design and validate Frappe document workflows with approval chains and state transitions.

Updated May 31, 2026
One-click install
npx skills add https://github.com/anonymousminati/Res-POS --skill frappe-impl-workflow-anonymousminati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frappe-impl-workflow
Source: https://github.com/anonymousminati/Res-POS/tree/main/.claude/skills/impl/frappe-impl-workflow
Command: npx skills add https://github.com/anonymousminati/Res-POS --skill frappe-impl-workflow-anonymousminati

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Implementing a Frappe workflow by hand often leads to missing transitions, broken approval chains, stuck documents, and permission errors during state changes.

Core Features & Use Cases

  • Workflow design guidance: Plan states, transitions, roles, conditions, and doc_status values before building.
  • Approval-chain validation: Prevent dead ends, self-approval mistakes, overlapping conditions, and invalid state mappings.
  • Implementation and testing support: Cover Workflow State, Workflow Action Master, workflow creation, update_field behavior, and transition testing.
  • Use case: Set up a leave, purchase, or document-review approval flow that routes through the right approvers and recovers cleanly from rejection.

Quick Start

Ask this skill to design a Frappe workflow for your DocType, then provide the states, approvers, rejection path, and any routing rules you need.

Frequently Asked Questions about frappe-impl-workflow

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

FAQPage Schema
How do I design a Frappe workflow with approval chains and rejection loops?

Frappe workflow approval chains require mapping transition roles, workflow states, and doc_status values to prevent dead ends. You validate conditional routing and rejection loops so documents recover cleanly after a denial.

Why does my Frappe document get stuck during state transitions?

Frappe documents get stuck during state transitions due to missing transitions, overlapping conditions, or invalid state mappings. Validating workflow state handling and transition roles prevents these broken approval chains and permission errors.

How do I prevent self-approval mistakes in a Frappe workflow?

To prevent self-approval mistakes in a Frappe workflow, you must validate the allow_self_approval setting and transition roles. Correctly mapping these permissions stops users from approving their own documents and breaking the approval chain.

Does Frappe workflow support conditional routing for submittable DocTypes?

Frappe workflows support conditional routing for both submittable and non-submittable DocTypes. You achieve this by mapping correct doc_status values, workflow states, and transition conditions to route documents to the appropriate approvers.

How do I test Frappe workflow transitions and update_field behavior?

To test Frappe workflow transitions, you need testable apply_workflow coverage that validates state changes, update_field behavior, and Workflow Action Master. This ensures transition testing catches permission errors and broken approval chains.

What's the best way to migrate Frappe workflows without breaking existing documents?

The best way to migrate Frappe workflows is to validate doc_status mapping and workflow state handling beforehand. This prevents permission errors, overlapping conditions, and stuck documents when applying new state transitions to existing records.