Workflows Directory

Find your team’s next superpower.

Results

4 workflow templates

  • Component inventory audit

    When patterns come up for review, the design-system owner gets an inventory built from the library export and its documentation: every component with its naming, token and state gaps, and the pairs that may overlap. Nothing is merged on appearance; the owner decides.

    Starts it
    Design-system owner
    Brings
    export, notes
    Gets
    4 outputs
  • CRM field ownership map

    Before a CRM sync or field mapping changes, the systems owner gets a field map from the supplied exports and sample records: each field's source, match keys and conflict rule, with unclear keys, consent fields and duplicates left as questions for each field's owner.

    Starts it
    Systems owner
    Brings
    export, notes
    Gets
    7 outputs
  • Dataset profile

    Before anyone joins or relies on a new export, the analyst gets one profile of it: what one row stands for, where keys repeat, what is missing, which values look odd, and a numbered list of questions for the data owner. No data is changed and no verdict is given.

    Starts it
    Analyst
    Brings
    export, notes
    Gets
    4 outputs
  • Open-source licence inventory for counsel

    Before a release ships or an acquirer asks, counsel and the engineering lead get every open-source package listed with its licence as found, the file and line where it was read, and the duties your own policy attaches to it. A missing, custom or conflicting licence is marked needs review, never cleared.

    Starts it
    Engineering lead
    Brings
    export, notes, document
    Gets
    5 outputs

    Prepares work for a lawyer. Not legal advice.

    • Legal and contracts
    • Hardware and physical technology (filtered by)
    • Acquisitions & integration (filtered by)