Feedback-to-Action Portfolio Briefing Orchestrator

The Prompt

You are a portfolio operations analyst. Transform feedback and research inputs into a governance-ready action queue that can be routed across tools with review checkpoints.

PREFERRED LLM / FAMILY:
{{preferred_llm}}

BRIEFING SCOPE:
{{briefing_scope}}

FEEDBACK INPUTS:
{{feedback_inputs}}

EVALUATION RUBRIC:
{{evaluation_rubric}}

AUTOMATION RULES:
{{automation_rules}}

ACTION DESTINATION:
{{action_destination}}

COMMUNICATION RHYTHM:
{{communication_rhythm}}

Return exactly these sections:

1) Signal Consolidation
- Consolidated themes across channels.
- Confidence and freshness scoring.

2) Action Prioritization Matrix
- Priority class by impact, effort, and confidence.
- Owner and owner-context assignment.

3) Draft Routing Blueprint
- Which actions are draft proposals vs high-risk actions.
- Required approvals by class.

4) Cross-Tool Execution Map
- Routes from feedback source to issue/action systems.
- MCP write targets and safety controls.

5) Portfolio Briefing Package
- Executive-facing summary.
- Team-facing backlog and near-term execution plan.

6) Health and Controls
- Review cadence.
- Quality drift checks.
- Escalation triggers and rollback criteria.

Rules:
- Keep recommendations explicit and evidence-linked.
- Include at least one "manual handling" path for ambiguous or low-confidence findings.
- Do not produce final action as executed state; mark as proposed where applicable.

When to Use

Use this when customer feedback and research outputs are plentiful but operationally disconnected, and you want one consistent bridge from narrative signals to a prioritized, reviewable action plan.

Variables

Variable	Description	Example
preferred_llm	LLM family for synthesis and prioritization	gpt, o3
briefing_scope	Product areas and period to include	”Mobile + web feedback from last 30 days.”
feedback_inputs	Raw feedback sources	”Support threads, surveys, bug triage notes, usability research.”
evaluation_rubric	Scoring method and thresholds	”Impact x effort x confidence, minimum 3 evidence points.”
automation_rules	What can be auto-routed vs manual	”Auto-create low-risk tasks; flag high-risk for manager review.”
action_destination	Target tools and boards	”Jira, Notion, Slack, project tracker.”
communication_rhythm	Cadence and audience for summaries	”Weekly executive + bi-weekly ops sync.”

Tips & Variations

• Add one section for “policy and reputational risk” to prevent rushed action.
• Ask for a “counterargument” field for each high-priority action.
• Separate bug-quality and product-quality tracks before merging.
• Request a second model pass on final priority ordering.

Example Output

• Prioritization matrix with high/medium/low action buckets.
• Action routing map showing draft writes to issue and comms systems with approval gates.
• Briefing package tuned for leaders and operational owners.

Related site references

• AI Use Case: Customer feedback intelligence loop
• AI Use Case: Bug triage and fix planning
• Tool: Zapier
• Tool: Pipedream
• Tool: OpenClaw
• Model: GPT
• Model: o3
• Concept: Tool use and function calling