Skip to content

PranavNagrecha/AwesomeSalesforceSkills / skills/admin/configuration-workbook-authoring

configuration-workbook-authoring

Verified

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). More triggers: workbook row schema, recommended_agent, recommended_skills, row_id, source_req_id, RTM linkage block, not-in-scope-this-release, descope ledger, version-lock the workbook, check_workbook.py.

templates/configuration-workbook-authoring-template.md

View on GitHub
# Configuration Workbook Authoring — Work Template

Use this template to plan a workbook authoring or revision task before
starting. The actual workbook artifact is authored from
`templates/config-workbook.md` (the canonical 10-section skeleton).

## Scope

**Skill:** `configuration-workbook-authoring`

**Request summary:** (fill in what was requested — new workbook for release X,
mid-sprint change request adding rows for feature Y, etc.)

## Context Gathered

- RTM source: <path or URL>
- Approved user stories: <ids>
- Approved fit-gap rows: <ids>
- Descope / defer / escalate decisions: <req_ids and the decision for each>
- Target org alias: <alias>
- Org probe date (for `target_value` reality checks): <YYYY-MM-DD>
- Sprint / release id: <release-id>
- Existing committed workbook (if revising): <path>

## Approach

Which pattern from SKILL.md applies?

- [ ] Pattern 1 — Source-grounded row authoring
- [ ] Pattern 2 — Version-locking at sprint commit
- [ ] Pattern 3 — One row, one agent, one section

Format rules applied end to end, with a real checker run:
`references/worked-examples.md`. A full ten-section workbook for a real
solution: `skills/admin/case-management-setup/references/worked-example-case-intake.md`.

## Authoring Checklist

- [ ] Copied `templates/config-workbook.md` to `docs/workbooks/<release>/cwb.md`
- [ ] All 10 canonical sections present
- [ ] Every row has `row_id`, `source_req_id`, `source_story_id`
- [ ] Every row has exactly one `recommended_agent`, resolving to a
      non-deprecated `agents/<id>/AGENT.md` (validated against
      `agents/_shared/SKILL_MAP.md` and `agents/_shared/AGENT_DISAMBIGUATION.md`)
- [ ] Every row has at least one entry in `recommended_skills[]`, and every
      entry resolves to a file that exists on disk
- [ ] No row has placeholder status (`TBD`, `WIP`, `?`, a bare to-do marker, empty)
- [ ] No `target_value` is a Setup navigation path
- [ ] Every Section 4 row cites `sharing-selection.md` + its `Q<n>` branch
- [ ] Every Section 6 row that picks an automation engine (Flow, Apex,
      Approvals, a rule engine with an automation choice) cites
      `automation-selection.md` + its `Q<n>` branch — a Queue/Group/
      BusinessHours configuration row is exempt (Gotcha 12)
- [ ] No Section 3 row grants access through a Profile (residue only)
- [ ] No row has inline credentials in `target_value`
- [ ] The descope / defer / escalate ledger is written and no descoped
      `req_id` has a row
- [ ] `python3 scripts/check_workbook.py --workbook <path>` exits 0
- [ ] Version-locked: statuses set to `committed` **and** the file snapshotted
      at `docs/workbooks/<release>/cwb.md` and tagged
- [ ] Reviewers tagged

## Notes

(Record decisions, deviations, and links to ADRs.)
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall