persona-routing

Routes DoR sign-off notifications to GitHUb issues via configurable channels.

1|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/heymishy/skills-repo --skill persona-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: persona-routing
Source: https://github.com/heymishy/skills-repo/tree/main/.github/skills/persona-routing
Command: npx skills add https://github.com/heymishy/skills-repo --skill persona-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DoR sign-offs require non-engineers to access engineering tools or channel contexts. This skill routes DoR sign-off notifications to approved non-engineer channels configured in context.yml to streamline approvals and maintain governance traces.

Core Features & Use Cases

  • Routes DoR sign-off notifications to configured non-engineer approval channels.
  • Phase 2 supports the github-issue channel: a designated approver posts /approve-dor on the linked issue, triggering a GitHub Actions workflow that writes dorStatus: "signed-off" to pipeline-state.json.
  • Channel targets are read from context.yml — no hardcoded values (ADR-004).
  • Use Case: Product managers, risk leads, or compliance reviewers can sign off without VS Code access by interacting with the configured channel.

Quick Start

Configure context.yml with an approval channel (e.g., github-issue) and then trigger a DoR sign-off to route the notification.

Frequently Asked Questions about persona-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I route DoR sign-offs to non-engineer approval channels?

DoR sign-off routing sends notifications to designated non-engineer channels. You define channel targets in context.yml, allowing approvers to interact directly without accessing engineering tools like VS Code.

How does the github-issue channel handle DoR sign-off approvals?

The github-issue channel lets a designated approver post /approve-dor on a linked issue. This triggers a GitHub Actions workflow that writes dorStatus: signed-off to pipeline-state.json to record the approval.

Can I use GitHub Actions to automate DoR compliance sign-offs for product managers?

Yes, GitHub Actions automates DoR compliance sign-offs. When an approver posts /approve-dor on the linked github-issue, the workflow updates pipeline-state.json, streamlining approvals and maintaining governance traces for non-engineers.

Do I need to hardcode approval channel targets for DoR sign-off routing?

No, you do not need to hardcode approval channel targets. Channel targets are read dynamically from context.yml, adhering to ADR-004, ensuring flexible routing of DoR sign-off notifications without hardcoded values.

What is the best way to configure DoR sign-off notifications in context.yml?

Configuring DoR sign-off notifications in context.yml involves defining an approval channel like github-issue. Once configured, triggering a DoR sign-off automatically routes the notification to the specified non-engineer channel.