product-lead

Interpret ambiguous product requirements and prioritize track scope decisions.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill product-lead
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-lead
Source: https://github.com/AhmedElhadarey/Gilfoyle/tree/main/skills/leads/product-lead
Command: npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill product-lead

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Product Lead automates interpretation of ambiguous product requirements and prioritization decisions to prevent drift and ensure alignment with track objectives.

Core Features & Use Cases

  • Interpret ambiguous requirements to derive actionable scope and constraints for tracks.
  • Prioritize features and tasks within a track, respecting spec intent and guardrails.
  • Escalate scope or deliverables changes to users when necessary, maintaining clear accountability and traceability.

Quick Start

Consult the product lead whenever you need scope interpretation or priority decisions during track execution.

Frequently Asked Questions about product-lead

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve ambiguous product requirements during project execution?

Resolve ambiguous product requirements by applying autonomous product interpretation and prioritization decisions to prevent scope drift and align deliverables with track objectives. It evaluates vague inputs, derives actionable constraints, and returns standardized decisions referencing spec guidelines for accountability.

What is the best way to prioritize features and tasks respecting spec intent?

Prioritize features and tasks by evaluating spec intent and project guardrails to determine execution order. The product consultation protocol analyzes proposed scope changes, ranks tasks based on track objectives, and returns standardized decisions to guide orchestrator governance.

How do I interpret vague project scopes to derive actionable constraints?

Interpret vague project scopes through autonomous product analysis that translates ambiguous requirements into specific actionable constraints. The process follows a consultation protocol to evaluate scope changes, returning standardized decision formats that maintain traceability and prevent drift.

When should I escalate scope changes during track execution?

Escalate scope changes during track execution whenever proposed deliverables exceed defined guardrails or require user accountability. The product consultation protocol identifies when scope shifts impact track objectives, automatically escalating decisions to users while maintaining clear traceability of the prioritization logic.

Does this product consultation approach work without external dependencies?

This product consultation approach works entirely without external dependencies, using internal spec guidelines and orchestrator governance to resolve scope ambiguity. It autonomously processes vague requirements and returns standardized decisions formatted for direct integration into track execution workflows.

Why does product scope drift occur in track execution and how to prevent it?

Product scope drift occurs when ambiguous requirements are misinterpreted without standardized prioritization decisions. Prevent drift by applying autonomous product interpretation to evaluate scope changes against spec intent, returning structured decisions that enforce accountability and maintain alignment with track objectives.