Process & SOP Architect
When to activate this skill
Activate when the user asks to document, map, redesign, standardize, or improve a business process. Typical triggers include: "turn these notes into an SOP", "map our onboarding process", "create a RACI", "document the current state", "identify process gaps", or "create a future-state workflow".
Do NOT activate when:
- The user wants a software architecture diagram rather than a business process.
- The request is only to summarize a meeting without building an operating procedure.
- The user has not supplied enough information to identify the process scope and actors.
How this skill runs
- Review the user's source material and build a process specification using
references/process_spec_schema.md.
- Ask targeted questions for missing trigger, scope, roles, decisions, exceptions, controls, or outputs. Ask one question at a time.
- From the skill's root directory (the folder that contains
scripts/ and references/), save the specification as process_spec.json, and run the commands below from that same directory so the scripts/ paths resolve. Use this directory rather than /tmp, which is not reliably writable in the sandbox.
- Validate it:
python scripts/validate_process_spec.py --input process_spec.json
- Generate the process pack, including the polished executive PowerPoint briefing:
python scripts/generate_process_pack.py \
--input process_spec.json \
--output-dir process_pack
- Return the generated SOP, process map, RACI workbook, improvement backlog, executive summary, and PowerPoint briefing.
Requirements
python-docx (Word SOP)
openpyxl (Excel RACI and control register)
python-pptx (PowerPoint executive briefing)
These packages are present in the Copilot Studio sandbox — no pip install is required. The generators import them at startup and fail fast with a clear error if a dependency is missing, so a partial pack is never reported as complete.
Required outputs
- Editable Word SOP
- SVG process flow that can be opened in a browser or inserted into Office
- Excel RACI and control register
- CSV improvement backlog
- Markdown executive summary and unresolved-question log
- Editable PowerPoint executive briefing with title slide, snapshot, process flow, role handoffs, controls, risks, roadmap, chart, and next steps
Workflow the agent must follow
- Establish whether the user wants current state, future state, or both.
- Define the process boundary: trigger, start, end, inputs, outputs, and exclusions.
- Identify roles, systems, decisions, handoffs, exceptions, controls, and evidence.
- Separate observed facts from assumptions and recommendations.
- Build a complete process specification.
- Run validation and resolve errors before generation.
- Review generated deliverables for traceability and usability.
- Ensure the PowerPoint uses assertion-style slide titles, separates facts from recommendations, and does not introduce unsupported claims.
Quality rules
- Use verb-object wording for process steps, such as
Validate request or Approve payment.
- Every step must have an owner.
- Every decision must define both yes and no paths.
- Every control must identify purpose, owner, frequency, and evidence.
- Do not invent policy, legal, regulatory, service-level, or approval requirements.
- Label missing information as
TBD and include it in the unresolved-question log.
- Distinguish current-state problems from future-state recommendations.
- Do not automate a process merely because automation is possible.
- The presentation must summarize the SOP; it must not replace the SOP or invent new process facts.
- PowerPoint slides should be leadership-ready, concise, and editable.
Activation examples
- "Create an SOP from this onboarding workshop transcript."
- "Map the complaint-management process and identify control gaps."
- "Turn these process notes into a RACI and future-state improvement plan."
- "Document our invoice exception process for training and audit."
Run example
python scripts/validate_process_spec.py --input assets/example_process_spec.json
python scripts/generate_process_pack.py \
--input assets/example_process_spec.json \
--output-dir vendor_onboarding_pack
# Generate only the PowerPoint briefing
python scripts/generate_presentation.py \
--input assets/example_process_spec.json \
--output-dir vendor_onboarding_pack
1---2name: process-sop-architect3description: Use this skill whenever the user asks to document, map, standardize, redesign, or improve a business process from notes, transcripts, interviews, or requirements, especially when they need an editable SOP, process map, RACI, controls, improvement backlog, or polished PowerPoint briefing.4---56# Process & SOP Architect78## When to activate this skill9Activate when the user asks to document, map, redesign, standardize, or improve a business process. Typical triggers include: "turn these notes into an SOP", "map our onboarding process", "create a RACI", "document the current state", "identify process gaps", or "create a future-state workflow".1011Do NOT activate when:12- The user wants a software architecture diagram rather than a business process.13- The request is only to summarize a meeting without building an operating procedure.14- The user has not supplied enough information to identify the process scope and actors.1516## How this skill runs171. Review the user's source material and build a process specification using `references/process_spec_schema.md`.182. Ask targeted questions for missing trigger, scope, roles, decisions, exceptions, controls, or outputs. Ask one question at a time.193. From the skill's root directory (the folder that contains `scripts/` and `references/`), save the specification as `process_spec.json`, and run the commands below from that same directory so the `scripts/` paths resolve. Use this directory rather than `/tmp`, which is not reliably writable in the sandbox.204. Validate it:21 ```bash22 python scripts/validate_process_spec.py --input process_spec.json23 ```245. Generate the process pack, including the polished executive PowerPoint briefing:25 ```bash26 python scripts/generate_process_pack.py \27 --input process_spec.json \28 --output-dir process_pack29 ```306. Return the generated SOP, process map, RACI workbook, improvement backlog, executive summary, and PowerPoint briefing.3132## Requirements33- `python-docx` (Word SOP)34- `openpyxl` (Excel RACI and control register)35- `python-pptx` (PowerPoint executive briefing)3637These packages are present in the Copilot Studio sandbox — no `pip install` is required. The generators import them at startup and fail fast with a clear error if a dependency is missing, so a partial pack is never reported as complete.3839## Required outputs40- Editable Word SOP41- SVG process flow that can be opened in a browser or inserted into Office42- Excel RACI and control register43- CSV improvement backlog44- Markdown executive summary and unresolved-question log45- Editable PowerPoint executive briefing with title slide, snapshot, process flow, role handoffs, controls, risks, roadmap, chart, and next steps4647## Workflow the agent must follow481. Establish whether the user wants current state, future state, or both.492. Define the process boundary: trigger, start, end, inputs, outputs, and exclusions.503. Identify roles, systems, decisions, handoffs, exceptions, controls, and evidence.514. Separate observed facts from assumptions and recommendations.525. Build a complete process specification.536. Run validation and resolve errors before generation.547. Review generated deliverables for traceability and usability.558. Ensure the PowerPoint uses assertion-style slide titles, separates facts from recommendations, and does not introduce unsupported claims.5657## Quality rules58- Use verb-object wording for process steps, such as `Validate request` or `Approve payment`.59- Every step must have an owner.60- Every decision must define both yes and no paths.61- Every control must identify purpose, owner, frequency, and evidence.62- Do not invent policy, legal, regulatory, service-level, or approval requirements.63- Label missing information as `TBD` and include it in the unresolved-question log.64- Distinguish current-state problems from future-state recommendations.65- Do not automate a process merely because automation is possible.66- The presentation must summarize the SOP; it must not replace the SOP or invent new process facts.67- PowerPoint slides should be leadership-ready, concise, and editable.6869## Activation examples70- "Create an SOP from this onboarding workshop transcript."71- "Map the complaint-management process and identify control gaps."72- "Turn these process notes into a RACI and future-state improvement plan."73- "Document our invoice exception process for training and audit."7475## Run example76```bash77python scripts/validate_process_spec.py --input assets/example_process_spec.json78python scripts/generate_process_pack.py \79 --input assets/example_process_spec.json \80 --output-dir vendor_onboarding_pack8182# Generate only the PowerPoint briefing83python scripts/generate_presentation.py \84 --input assets/example_process_spec.json \85 --output-dir vendor_onboarding_pack86```