Agent skill
adinsights-persona-router
Simulate ADinsights owner personas for planning and review workflows. Use when asked for persona simulation, workstream review, owner-style planning, backlog gap review, dependency analysis, or cross-stream escalation guidance tied to ADinsights docs.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/adinsights-persona-router
SKILL.md
ADinsights Persona Router
Overview
Route ADinsights planning and review requests to the right persona profile, then generate a structured report using repo-defined ownership, tests, and escalation rules. Keep source-of-truth in repo docs and avoid inventing personas, scopes, or contracts.
Recontext Load Order
- Open
AGENTS.md. - Open
docs/ops/doc-index.md. - Open
docs/workstreams.md. - Open
docs/project/phase0-backlog-validation.md. - Open
docs/project/phase0-simulated-reviews.md. - Open
docs/project/feature-ownership-map.md. - Open
docs/project/phase1-execution-backlog.mdwhen task status matters.
Persona Catalog
Load references/persona-catalog.yaml and use it as the canonical list of:
- Persona identity and role.
- Scope ownership and review focus.
- Required tests and doc links.
- Escalation behavior.
Router Resolution Rules
Resolve persona in this exact order:
- Explicit persona mention by name (
Maya,Lina,Raj, etc.). - Explicit stream/workstream ID (
S1,Stream 4, etc.). - Folder path hint (
backend/analytics,frontend/src,dbt/, etc.). - Domain keyword hint (
airbyte,dbt,snapshot,frontend, etc.). - Ask a clarification question only if unresolved after steps 1-4.
If a request spans multiple top-level folders, route to cross-stream behavior and apply Raj/Mira escalation guidance.
Confidence and Conflict Handling
- Base scores: explicit persona
1.00, explicit stream0.90, folder0.80, keyword0.60. - Penalties:
-0.20per strong conflict,-0.15for cross-stream ambiguity. - Use
confidence_policyfromreferences/persona-catalog.yaml:auto_resolve_min: 0.75clarify_min: 0.55
- Return
action=clarifywhen confidence is low and risk is high (conflicts/cross-stream).
Operating Mode
- Default mode: planning/review simulation.
- Do not default to code-writing roleplay.
- Simulate owner reasoning, then return action-ready findings tied to real docs/tests.
- CLI entrypoint:
scripts/persona_router.py.--mode resolve|preflight--format json|markdown--path <path>(repeatable)--changed-file <path>(repeatable)--changed-files-from-git(optional)
Output Contract
Default output is a decision packet with:
schema_version(2.1.0)selected_personabackup_personaresolved_byconfidenceconflict_flagstouched_streamsrequired_testsdocs_to_openescalation_decisionrecommended_report_templateclarifying_question(only when needed)downstream_recommendationsinvoke_scope_gatekeeper(truewhen cross-stream or low confidence)invoke_contract_guard(truewhen contract-sensitive prompt/path hints are present)invoke_release_readiness(trueonly when release/go-live intent is explicit)
evidenceentries (type,value,strength,source)decision_traceexplainability string
For backward compatibility, the top-level invoke_scope_gatekeeper mirrors downstream_recommendations.invoke_scope_gatekeeper.
Handoff Policy
- Persona router remains advisory-only and never hard-blocks.
- Scope concerns are delegated to
adinsights-scope-gatekeeper. - Contract validation is delegated to
adinsights-contract-guard. - Final go/no-go advisory is delegated to
adinsights-release-readiness.
Use the templates in references/report-templates.md:
- Phase 0 backlog simulation template.
- Implementation planning template.
- Cross-stream escalation template.
Guardrails
- Preserve tenant isolation and RLS assumptions from
AGENTS.md. - Never expose user-level PII; keep analytics aggregated.
- Never log or suggest logging secrets/tokens.
- Keep changes scoped to one top-level folder unless Raj/Mira escalation path is explicit.
- Use the canonical per-folder tests from
docs/workstreams.mdanddocs/ops/testing-cheat-sheet.md.
Maintenance
- Keep persona records in
references/persona-catalog.yamlsynchronized withdocs/workstreams.md. - Run
scripts/validate_persona_catalog.pyafter catalog edits. - Use
scripts/run_router_golden_tests.pyto verify routing behavior against golden cases. - Use
scripts/smoke_resolve_persona.py "your prompt"for backward-compatible smoke checks. - Run
scripts/sync_to_codex_home.shto sync this repo source-of-truth to$HOME/.codex/skills/adinsights-persona-router/.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?