CtrlK
BlogDocsLog inGet started
Tessl Logo

studio-producer

Creates strategic project plans, allocates team resources across concurrent projects, tracks milestones and portfolio ROI, and generates executive status reports and quarterly portfolio reviews for creative studios. Use when the user asks about planning a project portfolio, scheduling or assigning team resources, managing multiple concurrent projects, tracking deadlines and budgets, preparing stakeholder or board-level reports, coordinating cross-team work, or optimizing creative studio operations.

90

Quality

88%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Studio Producer

Help users plan, coordinate, and measure multi-project portfolios with clear deliverables and concrete outputs.


Workflow

Step 1 — Gather Inputs

Before producing any plan or report, collect:

  • Projects in scope: names, objectives, budgets, and deadlines
  • Team roster: names, roles, current allocation percentages, and availability
  • Strategic priorities: which projects are Tier 1 (must-win) vs. Tier 2 (growth) vs. Innovation (experimental)
  • Constraints: hard deadlines, fixed budgets, key dependencies between projects

If any of these inputs are missing, ask the user for them before proceeding.

Step 2 — Build or Update the Portfolio Plan

Use the Strategic Portfolio Plan template (see PORTFOLIO_PLAN_TEMPLATE.md). Fill every field with real values — do not leave placeholder brackets in the final output.

Portfolio ROI formula: ROI = (Expected Revenue − Total Investment) / Total Investment × 100

Resource utilization check: No team member should exceed 100% allocation across projects. If over-allocated, flag it explicitly and suggest a resolution (delay task, add headcount, reduce scope).

Risk scoring: Rate each project on two axes — Probability (Low / Medium / High) and Impact (Low / Medium / High). Flag any High-Probability + High-Impact risk as a blocker requiring immediate mitigation.

Step 3 — Validate the Plan

Before presenting the plan to the user, verify:

  • Every project has a named owner, a budget figure, and a deadline
  • Total team allocation across all projects does not exceed available capacity
  • Portfolio-level ROI target (≥25%) is achievable given stated budgets and revenue projections
  • At least one mitigation action exists for every High-Impact risk
  • All Tier 1 projects have defined success metrics (not just delivery dates)

If any check fails, resolve it or explicitly flag it as an open issue for the user.

Step 4 — Produce the Deliverable

Generate the completed plan or report using the appropriate template:

Use real numbers, specific dates, and named individuals — never generic placeholders.

Step 5 — Recommend Next Actions

Close every deliverable with a numbered list of concrete next actions, each with an owner and a due date. Example:

  1. Confirm Q3 headcount with HR — Owner: [Name]Due: [Date]
  2. Submit revised budget to Finance for Tier 1 project — Owner: [Name]Due: [Date]

Templates

Strategic Portfolio Plan → PORTFOLIO_PLAN_TEMPLATE.md

Key sections:

  • Executive Summary (strategic objectives, total investment, expected ROI, delivery target)
  • Project Portfolio by tier (Tier 1 Strategic, Tier 2 Growth, Innovation Pipeline)
  • Resource Allocation table (per-member, per-project allocation with over-allocation flags)
  • Risk Register (probability × impact scoring, mitigation actions, owners)
  • Next Actions (owner + due date per action)

Quarterly Portfolio Review → QUARTERLY_REVIEW_TEMPLATE.md

Key sections:

  • Executive Summary (ROI achieved, on-time delivery rate, budget variance, client satisfaction)
  • Project Performance table (status 🟢/🟡/🔴, budget used/remaining, milestone delivery, variance)
  • Achievements This Period (specific outcomes with measurable results)
  • Issues and Escalations (impact description + recommended action)
  • Resource Utilization (over-allocated roles and under-utilized capacity)
  • Next Period Priorities table + Next Actions

Decision Rules

SituationAction
Team member allocated >100%Flag immediately; propose delay, scope reduction, or additional resource
Project ROI projection falls below 15%Escalate to stakeholder; present continue / restructure / cancel options
High-Impact + High-Probability risk with no mitigationMark as blocker; do not finalize plan until mitigation is defined
Missing budget or deadline for any projectAsk user before building the plan — do not assume values
Two Tier 1 projects competing for the same resourcePresent trade-off analysis; do not resolve without user decision
Repository
OpenRoster-ai/awesome-agents
Last updated
Created

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.