Agent skill · magnus919
product-lifecycle
Route a product through its full lifecycle — discovery, strategy, portfolio choice, roadmap, UX and requirements, experimentation, delivery handoff, adoption, success, and lifecycle review — by composing existing specialist product skills with phase-entry evidence, handoff artifacts, and escalation rules. Use when evaluating a new product idea, managing a product through its lifecycle, or connecting product phases that currently operate in isolation. Do not use for a single product task that is already owned by a specialist skill (load that skill directly); do not use for software delivery lifecycle work (route to neckbeard); do not use to duplicate product discovery, strategy, UX, experimentation, analytics, release, or delivery methods.
What it needs
About 6k tokens when loaded.
What this skill does
Product Lifecycle A thin orchestration bundle that routes a product through nine lifecycle phases by composing existing specialist product skills. It provides cross-skill routing and evidence handoff — it does NOT duplicate any specialist's step-by-step methodology. Load this umbrella when you need to navigate a product across multiple lifecycle phases; load individual specialist skills directly when you only need one phase's capability. Phase routing table Each phase routes to one or more specialist skills. Entry evidence must exist before the phase starts. Output artifacts are handed off to the next phase through the lifecycle evidence ledger. Every phase has explicit escalation behavior and completion criteria. Full phase contracts are in references/phases.md. # Phase Primary specialist(s) Entry evidence Output artifacts Escalation behavior Completion criteria --- --- --- --- --- --- --- 1 Discovery product-discovery Product idea, market signal, or stakeholder request Problem statement, stakeholder map, discovery log, product type classification Stop if: problem cannot be articulated in user terms; no stakeholder describes a real need; problem is already solved; out of organizational remit Problem statement exists that a stakeholder recognizes; product type classified; proceed/pause/stop decision recorded 2 Strategy and portfolio choice product-strategy, strategy-frameworks Problem statement and discovery log from Phase 1 Strategic assessment, market sizing, portfolio recommendation, investment thesis Stop if: opportunity conflicts with strategy; market evidence contradicts thesis; resource constraints are infeasible; strategic direction is ambiguous Strategic assessment with fit/no-fit reasoning; portfolio decision recorded; resource estimate recorded 3 Roadmap product-roadmapping-and-portfolio Strategic assessment and portfolio decision from Phase 2 Outcome roadmap entry, Now/Next/Later placement, strategic bet record, dependency map, capacity allocation Stop i …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills magnus919/product-lifecycle