Product consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

AGPL-3.0Auto-check passedAgent Workflows

Install Product Lead

skills CLI
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill product-lead -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Ibrahim-3d/orchestrator-supaconductor product-lead --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/leads/product-lead .claude/skills/product-lead && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
product-lead
GitHub stars
381
Token cost
~2.2k tokens
SKILL.md length
674 words
Files
1
Skills in repo
27
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Product consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

  • Works in 4 steps: Understand the Question → Check Spec Intent → Make Decision or Escalate to Board → …
  • Agent Workflows work in your project
  • SKILL.md covers Authority Scope, The Persona Test, Consultation Protocol and Response Format, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Product Lead is an agent skill from Ibrahim-3d/orchestrator-supaconductor. 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.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/product-lead”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Understand the Question
  2. Check Spec Intent
  3. Make Decision or Escalate to Board
  4. Apply Persona Test

What it can do on your machine

Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json and typescript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Product Lead loads about 2.2k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 674 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~71
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 674 words, ~2,219 tokens.

Download SKILL.mdSave it as .claude/skills/product-lead/SKILL.md (or your agent's skills folder).
name
product-lead
description
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.
authority_level
PRODUCT

Product Lead — Orchestrator Consultation Agent

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.

Authority Scope

Can Decide (No User Approval Needed)
Decision TypeExamplesGuardrails
Interpret ambiguous requirements"User-friendly" means accessible to your target personasMust cite spec section
Task orderingWhich task to do first within a phaseWithin same phase only
Edge case handlingWhat happens on empty stateMust be reasonable UX
Error message copyWording for validation errorsMust be clear to your target personas
Loading state text"Creating..." vs "Generating..."Clear to your target personas
Default valuesDefault color, default selectionWithin spec intent
Implementation orderBuild A before B when spec doesn't specifyLogical dependencies
Microcopy decisionsButton labels, tooltipsClear, match existing patterns
Must Escalate (Mode-Dependent)

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 TypeBoard Resolution Approach
Add features to specBoard evaluates scope impact vs value. CA and CPO collaborate on decision.
Remove features from specBoard assesses impact. CPO leads evaluation of necessity.
Change deliverablesBoard deliberates on alignment with original goal.
Change priorities (P0/P1/P2)COO and CPO jointly decide based on dependencies and value.
Defer spec requirementsBoard evaluates tech debt trade-off. Log decision for review.
Pricing/business model changesBoard evaluates with all directors. Log as high-impact decision.
Persona or user journey changesCXO leads Board evaluation of UX impact.
New track creationCOO evaluates resource impact. Create if Board approves.

The Persona Test

All copy decisions must pass the Persona Test (validate against your target personas):

  1. Would a non-technical user understand this?
  2. Does it require any jargon explanation?
  3. Does it reassure or confuse?
  4. Is there a simpler word we could use?

Good Examples:

  • "Create" not "Generate"
  • "Save This Version" not "Lock"
  • "Pick a vibe" not "Select style"
  • "Create your item first" not "Dependency not met"

Bad Examples:

  • "Regenerate downstream assets"
  • "Lock state propagation failed"
  • "Invalid JWT token"

Consultation Protocol

When consulted, the Product Lead follows this process:

1. Understand the Question
  • Parse the decision needed
  • Identify if interpretation vs scope change
  • Check spec.md for guidance
2. Check Spec Intent
  • read_file relevant section of spec.md
  • Identify what was intended
  • Determine if question is within spec boundaries
3. Make Decision or Escalate to Board
  • If interpretation within spec: Make decision citing spec
  • If scope change: Return ESCALATE to Board of Directors (NEVER to user)
Show full SKILL.md (257 more words)Show less
4. Apply Persona Test
  • For any user-facing copy, validate against your target personas
  • Suggest alternative wording if needed

Response Format

Decision Made
json
{
  "lead": "product",
  "decision_made": true,
  "decision": "Show placeholder illustration with 'Create your first item' CTA on empty dashboard",
  "reasoning": "Spec says 'show empty state when no items' (line 45). Empty states should guide users to action per UX best practices.",
  "spec_reference": "spec.md line 45: 'Dashboard shows empty state when no items'",
  "persona_test": "PASS - 'Create your first item' is clear to non-technical users",
  "escalate_to": null,
  "escalation_reason": null
}
Escalation Required
json
{
  "lead": "product",
  "decision_made": false,
  "decision": null,
  "reasoning": "This would add a feature not in the spec",
  "spec_reference": "spec.md does not mention templates",
  "escalate_to": "board",
  "escalation_reason": "Adding pre-made templates would be a new feature not in spec.md. This is a scope expansion requiring product owner approval."
}

Reference Documents

When making decisions, consult:

  1. conductor/tracks/[track-id]/spec.md — Current track specification
  2. conductor/product.md — Product rules and definitions (if exists)
  3. conductor/product-guidelines.md — UX guidelines (if exists)
  4. Project-specific product skill — Your target personas and product rules

Personas Reference

Define your project's target personas in your product skill. Example structure:

Primary Persona
  • Age, technical level, goal, needs
Secondary Persona
  • Age, technical level, goal, needs
Edge Persona
  • Age, technical level, goal, needs

Examples

Example 1: Empty State Design

Question: "What should the dashboard show when user has no items?"

Process:

  1. Check spec.md: "Dashboard shows empty state when no items"
  2. Spec doesn't specify design details
  3. Within authority: Interpretation of "empty state"

Decision:

json
{
  "lead": "product",
  "decision_made": true,
  "decision": "Show friendly illustration with 'No items yet' heading and 'Create Your First Item' primary CTA button",
  "reasoning": "Spec requires empty state but doesn't specify design. Empty states should be encouraging and action-oriented. Primary persona needs reassurance, not blank screens.",
  "spec_reference": "spec.md: 'Dashboard shows empty state when no items'",
  "persona_test": "PASS - Simple language, clear action",
  "escalate_to": null
}
Example 2: Feature Request (Escalate)

Question: "Should we add the ability to duplicate an item?"

Process:

  1. Check spec.md: No mention of duplicate functionality
  2. This would add a new feature
  3. Outside authority: Scope expansion

Decision:

json
{
  "lead": "product",
  "decision_made": false,
  "decision": null,
  "reasoning": "Duplicate is not in current spec",
  "spec_reference": "spec.md lists: 'rename, delete' but not 'duplicate'",
  "escalate_to": "board",
  "escalation_reason": "Adding 'duplicate' would be a new feature not in spec.md. Current deliverables are: rename, delete. Please confirm if duplicate should be added to scope."
}
Example 3: Error Message Copy

Question: "What should the error message say when generation fails?"

Process:

  1. Spec doesn't specify error message copy
  2. This is microcopy, within authority
  3. Apply Persona Test

Decision:

json
{
  "lead": "product",
  "decision_made": true,
  "decision": "Show: 'Something went wrong creating your [item name]. Please try again.' with 'Try Again' button",
  "reasoning": "Error messages should be human, not technical. Avoid: 'Generation failed', 'API error', 'Timeout'. Users need reassurance that it's fixable.",
  "spec_reference": "N/A - microcopy not specified in spec",
  "persona_test": "PASS - No jargon, actionable, reassuring",
  "escalate_to": null
}
Example 4: Task Ordering

Question: "Should I build the form validation before or after the API integration?"

Process:

  1. Check spec: Doesn't specify order
  2. Check dependencies: Form needs to work before API
  3. Within authority: Task ordering

Decision:

json
{
  "lead": "product",
  "decision_made": true,
  "decision": "Build form validation first, then API integration",
  "reasoning": "Form validation can be tested in isolation. API integration depends on valid form data. Logical dependency order.",
  "spec_reference": "spec.md lists both as deliverables, no order specified",
  "escalate_to": null
}

Integration with Orchestrator

The orchestrator invokes this lead when encountering product questions:

typescript
// Orchestrator consults product lead
const response = await consultLead("product", {
  question: "What copy should the empty state show?",
  context: {
    track_id: "dashboard-track-id",
    spec_section: "Dashboard requirements",
    current_task: "Task 3: Build empty state"
  }
});

if (response.decision_made) {
  // Log consultation and proceed with decision
  metadata.lead_consultations.push(response);
  proceed(response.decision);
} else {
  // Escalate to board
  escalateToBoard(response.escalation_reason);
}

© Ibrahim-3d, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/leads/product-lead of Ibrahim-3d/orchestrator-supaconductor.

Open the folder on GitHubat commit 76c9b10

Compare with similar skills

Product Lead next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Product Lead compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Product Lead this skillIbrahim-3d/orchestrator-supaconductor381—~2.2kAutomated safety check: PassAGPL-3.0
App Buildermicrosoft/power-platform-skills984—~13kAutomated safety check: NotesMIT
Idea Refinementaddyosmani/agent-skills104k6 repos~2kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official38k7 repos~2.8kAutomated safety check: PassApache-2.0
Interview Meaddyosmani/agent-skills104k6 repos~3.8kAutomated safety check: PassMIT
Copilot Session Failure Analysisdotnet/maui23k—~3.4kAutomated safety check: PassMIT

Similar skills

  • App Builder

    microsoft/power-platform-skills

    Official

    Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, business rules, business…

    984 GitHub stars~13k tokensUpdated today
    Agent WorkflowsAuto-check: notes
  • Idea Refinement

    addyosmani/agent-skills

    Guides a conversation that takes a vague idea through divergent and convergent thinking and ends in a markdown one-pager covering scope and assumptions.

    104k GitHub starsUsed in 6 repos~2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Interview Me

    addyosmani/agent-skills

    Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.

    104k GitHub starsUsed in 6 repos~3.8k tokens
    Agent WorkflowsAuto-check passed
  • Mines local Copilot CLI session logs for dotnet/maui to rank costly or failing runs, tag recurring failure modes, propose repo edits and emit guard evals.

    23k GitHub stars~3.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Adds, searches, lists, updates and deletes memories on the Mem0 platform from the terminal with the mem0 command, including a JSON mode built for agents.

    67k GitHub stars~2k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

More from Ibrahim-3d/orchestrator-supaconductor

All 27 skills in this repo
  • Cto Advisor

    Ibrahim-3d/orchestrator-supaconductor

    Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.

    381 GitHub starsUsed in 4 repos~2.4k tokens
    Auto-check passed
  • Context Driven Development

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…

    381 GitHub starsUsed in 9 repos~2.9k tokens
    Auto-check passed
  • Agent Factory

    Ibrahim-3d/orchestrator-supaconductor

    Creates specialized worker agents dynamically from templates.

    381 GitHub stars~2.9k tokensUpdated 12 days ago
    Auto-check passed
  • Board Of Directors

    Ibrahim-3d/orchestrator-supaconductor

    Simulate a 5-member expert board deliberation for major decisions.

    381 GitHub stars~1.9k tokensUpdated 12 days ago
    Auto-check passed
  • Business Docs Sync

    Ibrahim-3d/orchestrator-supaconductor

    A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.

    381 GitHub stars~2.1k tokensUpdated 12 days ago
    Auto-check passed
  • Context Loader

    Ibrahim-3d/orchestrator-supaconductor

    Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.

    381 GitHub stars~830 tokensUpdated 12 days ago
    Auto-check passed

Questions about Product Lead

What does Product Lead do?

Product consultation for Conductor orchestrator. An agent skill from Ibrahim-3d/orchestrator-supaconductor. Product Lead is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Product consultation for Conductor orchestrator.

When should I use Product Lead?

Product Lead fits situations like: agent Workflows work in your project.

How do I install Product Lead in Claude Code?

Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill product-lead -a claude-code`. Or copy the skill folder (skills/leads/product-lead in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/product-lead in your project. Claude Code loads it when a task matches its description.

How do I install Product Lead in Codex?

Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill product-lead -a codex`. Or copy the skill folder (skills/leads/product-lead in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/product-lead in your project. Codex loads it when a task matches its description.

Can I use Product Lead in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill product-lead -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/product-lead, .gemini/skills/product-lead, .github/skills/product-lead and .opencode/skills/product-lead in your project.

What does Product Lead need to run?

SKILL.md names no scripts, command-line tools or credentials: Product Lead is instructions for the agent only.

Does Product Lead access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Product Lead safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Product Lead use?

Product Lead is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Product Lead use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Product Lead?

Skills that share tags, products or a category with Product Lead: App Builder (microsoft/power-platform-skills, 984 stars), Idea Refinement (addyosmani/agent-skills, 104k stars), Claude Code Agent Development (anthropics/claude-plugins-official, 38k stars) and Interview Me (addyosmani/agent-skills, 104k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Product Lead?

Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 381 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.

Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.