workflow/request-approval

To create an auditable approval request, provide the required inputs: context, session_id, approval_id, and summary. The skill validates these fields, prevents duplicate approvals, and writes a pending record to the runtime/contexts directory for human review.

When recording a human review request, you can include optional fields such as details, due_by, artifacts, notes, requested_by, and approver_role to provide additional context and guide the pending approval validation process.

Yes, the workflow approval skill supports U.Work integration by emitting a telemetry log via telemetry/log-work when available, ensuring that your structured approval requests maintain a persistent audit trail for governance review.

Pending approval records are stored deterministically as markdown files at runtime/contexts/<context>/approvals/<session_id>.<approval_id>.approval.md. This bounded context path structure enforces duplicate-checking and ensures auditable output.

Yes, you can use bounded contexts and session-based IDs to structure your approval requests. By defining specific context and session_id values, the skill scopes pending records accurately within the runtime directory for targeted human review.

The best way to manage approval requests requiring human review is to submit structured inputs with bounded contexts and session IDs. This creates deterministic, auditable pending records that prevent duplicates and integrate with telemetry logs.