head-of-product-engineering

Orchestrates nine product workflows invoking ten specialist skills to produce PRDs and sprint issues.

1|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill head-of-product-engineering-alexyedi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: head-of-product-engineering
Source: https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3/tree/main/.claude/skills/head-of-product-engineering
Command: npx skills add https://github.com/AlexYedi/Empire_State_Events_Pipeline_Take_3 --skill head-of-product-engineering-alexyedi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Running a full product lifecycle — discovery, vision, metrics, prioritization, PRD, shipping, launch, and risk — requires coordinating many specialist skills in the right order while preserving state across iterations. This orchestrator drives that sequence end-to-end and delivers a reviewable package (PRD, Orchestration Log, Future-State Register, Linear-ready sprint issues) every run. ## Core Features & Use Cases - Sequential specialist orchestration: Hard-invokes 10 product specialists across 9 workflows in dependency order, capturing each output in a persistent Orchestration Log. - Persistent Future-State Register: Maintains a per-project register (Notion DB row plus local mirror) enabling n+1 iteration turns with an Evolution Log that records what changed and why. - Multi-surface delivery: Writes the PRD and artifacts to Notion, files one Linear issue per user story with blockedBy dependency wiring, persists the PRD to ChatPRD, and always emits a text fallback. - Use Case: Ask to "build out the full plan for SkillSync" and receive a complete PRD, prioritized roadmap, launch plan, risk register, and sprint-ready Linear issues; later say "iterate on SkillSync" to get a cycle-2 update with an Evolution Log delta. ## Quick Start Ask the assistant to build out the full product plan for your project name and let it run all nine workflows end to end.

Frequently Asked Questions about head-of-product-engineering

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

FAQPage Schema
How do I run a full product planning cycle from discovery to launch?

Invoke this orchestrator with a project name and it runs nine workflows in order: discovery, vision, metrics, prioritization, PRD authoring, shipping, launch planning, risk, and an evolution log on repeat turns. Each workflow hard-invokes its specialist skills and logs outputs.

How does the orchestrator handle iterating on an existing product?

It looks up the project in the Future-State Register (Notion DB or local mirror). If found, the run is an n+1 turn: prior state loads into context and Workflow 9 writes an Evolution Log entry documenting what changed and why.

Can I skip specific workflows in a planning pass?

Yes. During pre-flight the orchestrator lists all workflows and asks which to skip. Skipped workflows are marked in the Orchestration Log, and dependent downstream workflows must explicitly cite the gap.

Does it create Linear issues automatically from the PRD?

Yes, when the Linear MCP is available it files one issue per PRD user story, resolves the target project by fuzzy match, applies cycle and project labels, and wires blockedBy dependencies from the PRD's dependency lines.

What happens if Notion or Linear MCPs are unavailable?

The orchestrator always emits all artifacts as markdown text in chat: the Orchestration Log, Future-State Register entry, Evolution Log entry, and Linear-ready sprint issues. MCP failures never block delivery.

When should I not use this orchestrator?

Do not use it for narrow single-specialist requests like writing only a PRD — invoke the specialist skill directly instead. It is also not intended for content or event workflows, which have their own orchestrators.