General design
AuraScore 81/100

Process Mapping and Workflow Diagramming Standards Specification

Define standardized visual notation, iconography, and spatial rules for operational process architecture.

Use this template when establishing unified visual diagramming standards across operations, engineering, and HR workflows. It produces an unambiguous specification covering syntax, color signaling, and responsive zoom levels.

Template

Role: Lead Systems Designer & Process Visualization Architect

Context

  • Operational Domain: {{team_domain}}
  • Target Diagramming Stack: {{tooling_ecosystem}}
  • Process Complexity: {{complexity_tier}}
  • Governance Ownership: {{governance_model}}
  • Primary Diagram Archetypes: {{primary_diagram_archetypes}}
  • Audience Personas: {{stakeholder_consumers}}

Task

Formulate a rigorous visual mapping and notation specification for {{team_domain}} to standardize the visual structure, node syntax, connector semantics, and layout flow of all workflow diagrams produced in {{tooling_ecosystem}}.

Method

  1. Define directional flow rules, swimlane proportions, milestone markers, and canvas grid alignment standards.
  2. Standardize geometric node primitives (shapes, corner radii, stroke widths) to map strictly to operational actions (events, activities, gateways, artifacts).
  3. Establish connector semantics detailing line styles (solid, dashed, dotted), arrowheads, routing angles (orthogonal vs straight), and crossing conventions.
  4. Design a semantic color token system for status signaling (active, blocked, automated, manual, external dependency) adapted for {{complexity_tier}}.
  5. Specify typographic labeling rules inside nodes, along connector paths, and on boundary containers.
  6. Detail iconography integration guidelines, defining scale, positioning, and approved icon sets within nodes.
  7. Create abstraction rules for progressive disclosure across different viewing zoom levels for {{stakeholder_consumers}}.
  8. Establish metadata annotation standards, including version tags, owner attribution, and system integration badges.

Constraints

  • MUST define explicit geometric parameters (width, height, radius, stroke px) for every standard node shape.
  • MUST NOT permit non-standardized flowchart shapes outside the approved notation registry.
  • Connectors MUST use orthogonal routing by default with explicit rules for handling line intersections.
  • The design system MUST remain natively constructible within {{tooling_ecosystem}} without third-party plugins.

Output format

Deliver an end-to-end diagramming specification organized into these mandatory sections:

  1. Canvas Setup, Swimlanes & Spatial Layout Standards
  2. Shape & Node Component Registry (with geometry rules)
  3. Connector Taxonomy & Line Routing Rules
  4. Status Signaling & Semantic Color Palettes
  5. Typography, Labeling & Iconography Rules
  6. Governance, Lifecycle & Maintenance Protocols (aligned with {{governance_model}}) Target word count is 700 to 1050 words.

Self-review

  • Verify that each diagram archetype specified in {{primary_diagram_archetypes}} is supported by the notation rules.
  • Ensure connector crossing rules prevent visual ambiguity in dense multi-system flows.
  • Check that node dimension and text truncation standards account for varied screen sizes.
AuraScore breakdown
81/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering12/12 · Strong

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

design-visual
design-general
research-productivity-operations
diagramming
workflow
systems-design