pm-business-flow

Creating a business flow diagram from vague requirements involves defining purpose, scope, terminology, start/end points, swimlanes, and risks. This skill processes high-level objectives to generate standardized end-to-end process visualizations and documentation artifacts like overview.md and flow.md.

Visualizing cross-team workflows for product management requires mapping roles and systems into swimlanes. This skill generates clear process representations from high-level objectives, reducing ambiguity and ensuring all roles are captured in a standardized business flow draft.

Standardizing process discovery documentation involves outputting templated artifacts like overview.md, flow.md, and issues.md. This skill structures your business flow discovery into these standard formats to align stakeholders and streamline the review process.

Yes, you can use this workflow visualization skill for scope alignment on a new onboarding process. It captures all roles and systems within defined swimlanes, ensuring shared understanding and reducing misalignment across project stakeholders.

To generate a swimlane flow draft, you need to provide a high-level business objective and identify stakeholders. The skill then applies a six-step workflow to define scope, terminology, and start/end points to output the visualization.

Yes, this business flow visualization tool tracks project risks and issues. It incorporates risk and issue identification as a core step in its workflow, outputting a dedicated issues.md artifact to document these factors alongside the process overview.