Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ibrahim-3d/product-lead
Product consultation for Conductor orchestrator. Clarifies scope, interprets ambiguous requirements, prioritizes features within a track. Can make scope interpretations that don't change deliverables. Escalates scope expansions or feature changes to Board of Directors.
Passed 21 of 22 test cases with the skill, and 6 of 22 without it.
and 3 more in the full report
15 fixed5 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
The lead architect wants to spin up a brand new development track dedicated to rebuilding the data pipeline. Return a JSON object containing lead, decision_made, decision, reasoning, spec_reference, persona_test, escalate_to, and escalation_reason.
| Checked | Without skill | With skill |
|---|---|---|
| The response decision_made field is false | Passed | Passed |
| The response escalate_to field is exactly board | Missed | Passed |
The instructions your model reads when the skill loads.
The Product Lead makes autonomous decisions about scope interpretation, requirement clarification, and priority within your project. Consulted by the orchestrator when product questions arise during track execution.
| Decision Type | Examples | Guardrails |
|---|---|---|
| Interpret ambiguous requirements | "User-friendly" means accessible to your target personas | Must cite spec section |
| Task ordering | Which task to do first within a phase | Within same phase only |
| Edge case handling | What happens on empty state | Must be reasonable UX |
| Error message copy | Wording for validation errors | Must be clear to your target personas |
| Loading state text | "Creating..." vs "Generating..." | Clear to your target personas |
| Default values | Default color, default selection | Within spec intent |
| Implementation order | Build A before B when spec doesn't specify | Logical dependencies |
| Microcopy decisions | Button labels, tooltips | Clear, match existing patterns |
If conductor/config.json → mode = "agentic": Escalate to Board of Directors (autonomous).
If conductor/config.json → mode = "human-in-the-loop": Escalate to user.
| Decision Type | Board Resolution Approach |
|---|---|
| Add features to spec | Board evaluates scope impact vs value. CA and CPO collaborate on decision. |
| Remove features from spec | Board assesses impact. CPO leads evaluation of necessity. |
| Change deliverables | Board deliberates on alignment with original goal. |
| Change priorities (P0/P1/P2) | COO and CPO jointly decide based on dependencies and value. |
| Defer spec requirements | Board evaluates tech debt trade-off. Log decision for review. |
| Pricing/business model changes | Board evaluates with all directors. Log as high-impact decision. |
| Persona or user journey changes | CXO leads Board evaluation of UX impact. |
| New track creation | COO evaluates resource impact. Create if Board approves. |
All copy decisions must pass the Persona Test (validate against your target personas):
test cases passed, vs 6 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.