| name | configuration-workbook-authoring |
| description | Author the Salesforce Configuration Workbook — the structured, reviewable handoff document an admin uses to execute a feature across Objects/Fields, Page Layouts, Profiles/PSGs, Sharing, Validation, Automation, List Views, Reports, Integrations, and Data. Triggers: 'salesforce configuration workbook', 'admin handoff document', 'implementation workbook'. NOT for object design itself (use admin/custom-field-creation, admin/lookup-and-relationship-design, agents/object-designer/AGENT.md), NOT for permission set design (use admin/permission-set-architecture, agents/permission-set-architect/AGENT.md), NOT for Flow construction (use skills/flow/* and agents/flow-builder/AGENT.md), and NOT for the deployment manifest (use skills/devops/metadata-api-retrieve-deploy). |
| category | admin |
| salesforce-version | Spring '25+ |
| well-architected-pillars | ["Operational Excellence","Reliability","Security"] |
| triggers | ["salesforce configuration workbook","admin handoff document","implementation workbook","how do I structure the build sheet for a new feature","we need a single document that drives object designer, perm set architect, and flow builder","convert user stories and fit-gap rows into actionable rows for admins","version-lock the configuration spec at sprint commit"] |
| tags | ["configuration-workbook-authoring","admin-handoff","implementation-spec","rtm-traceability","agent-routing"] |
| inputs | ["Approved user stories with story_id and acceptance criteria","Fit-gap analysis rows with req_id","Target org alias for naming-collision and existing-metadata reality check","Sprint or release identifier the workbook is being committed against"] |
| outputs | ["Configuration Workbook (markdown + JSON envelope + CSV) covering 10 canonical sections, every row tagged with owner, source_req_id, source_story_id, status, recommended_agent, and recommended_skills","RTM linkage block mapping each row_id back to a source_req_id and forward to a downstream runtime agent","Stdlib checker (check_workbook.py) that validates row schema, agent membership against the runtime roster, and absence of placeholder rows"] |
| dependencies | [] |
| version | 1.0.0 |
| author | Pranav Nagrecha |
| updated | 2026-04-28T00:00:00.000Z |
Configuration Workbook Authoring
This skill activates when a Salesforce delivery team needs to convert approved
user stories and fit-gap rows into the Configuration Workbook — the
structured, reviewable handoff document that drives admin execution and routes
each row to a single downstream runtime agent. The workbook is the canonical
artifact between requirements (RTM) and metadata (deployment manifest).
It is NOT the object designer, NOT the permission-set designer, NOT the Flow
builder, and NOT the deployment manifest. It is the handoff document those
agents consume.
Before Starting
Gather this context before authoring or revising a workbook:
- Approved user stories — every workbook row must carry
source_story_id.
Rows without an upstream story are orphaned and cannot be reviewed.
- Approved fit-gap rows — every workbook row must carry
source_req_id so
the workbook traces back to the RTM.
- Target org alias — the workbook is grounded in the live org. API names,
existing record types, and existing PSGs must reflect reality, not wishlist.
- Sprint / release identifier — the workbook is version-locked at sprint
commit. Mid-sprint change requests open new rows; they never edit existing
rows in place.
- Downstream agent roster — every row's
recommended_agent must resolve
to a real agents/<name>/AGENT.md from the runtime tier (see
agents/_shared/SKILL_MAP.md for the authoritative list).
Core Concepts
Concept 1: One row per addressable change
The workbook's atomic unit is a row. A row describes a single configurable
artifact (one field, one validation rule, one PSG composition step, one Flow
trigger, one report folder permission, one named credential). Rows are never
"epics" — if a row would require multiple agents to execute, it must be split.
The row schema is:
| Field | Required | Notes |
|---|
row_id | yes | Stable, unique within the workbook (e.g. CWB-FIELDS-014). Survives section reorder. |
section | yes | One of the 10 canonical sections. Must match exactly. |
target_value |
