Create or update SOP target mappings — route work classifications to Asana boards, projects, and sections
From opspal-corenpx claudepluginhub revpalsfdc/opspal-commercial --plugin opspal-core[classification] [--update] [--dry-run]Create or update the classification-to-Asana-target routing used by SOP policies. Supports one-to-many routing: a single work event can update multiple boards/projects.
Verify config/sop/sop-config.yaml exists. If not, advise: "Run /sop-init first."
If --update flag is present, load existing config/sop/mappings/ and show current state before modifications.
Step 1 — Discover workspaces:
Call mcp__asana__asana_list_workspaces and present the list.
Ask: "Which workspace contains your SOP tracking projects?"
Step 2 — Select classifications:
Present the 7 classification types: audit, report, build, migration, configuration, consultation, support.
Ask: "Which classifications do you want to configure targets for?" (multi-select)
Step 3 — For each selected classification:
mcp__asana__asana_search_projects in the selected workspace{classification} work:" — user selects from list or provides GID manuallymcp__asana__asana_get_project_sections for the selected projectStep 4 — Preview:
Show the YAML mapping that would be written. If --dry-run, stop here.
Step 5 — Write:
Write to config/sop/mappings/standard-client-boards.yaml (or a new mapping file if user specifies a custom name).
id: standard-client-boards
schema_version: "1.0.0"
version: "1.0.0"
workspace_gid: "<selected workspace>"
description: "Client delivery board routing"
targets:
- asana_project_gid: "<selected>"
asana_section_gid: "<selected>"
board_name: "<project name>"
match_criteria:
classification: [audit]
- asana_project_gid: "<selected>"
asana_section_gid: "<selected>"
board_name: "<project name>"
match_criteria:
classification: [build]
Print: "Mapping saved. Run /sop-review to see the full effective configuration."