mcpField
P
product-lifecycle-architect

product-lifecycle-architect

github.com/sylphxaiProductivity153 installsUpdated today
Repository

About product-lifecycle-architect

product-lifecycle-architect is a skill for turning product ideas into operating blueprints, intended for product builders. It combines product positioning, required systems, edge cases, and a phased roadmap.

Key features

  1. 01Product type classification
  2. 02Lifecycle matrix selection
  3. 03Product and business definition
  4. 04Operating system mapping
  5. 05States, edge cases, and metrics
  6. 06Phased P0/P1/P2 roadmap

Use cases

  1. 01Structuring an early product idea
  2. 02Mapping operational needs before launch
  3. 03Finding missing states and support flows

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill product-lifecycle-architect

After installing, type/product-lifecycle-architectin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/product-lifecycle-matrix.md

Details

From the project README

Product Lifecycle Architect

Use this skill to turn a product idea into a complete operating blueprint rather than a pile of features.

Workflow

  1. Classify the product type: mobile app, game, web app, SaaS, desktop utility, developer tool, marketplace, or hybrid.
  2. Read references/product-lifecycle-matrix.md and select the relevant lifecycle rows.
  3. Define the product promise, target user, wedge, business model, and distribution path.
  4. Map all required systems: onboarding, account, payment, entitlement, notification, backup, support, analytics, promotion, and operations.
  5. Identify missing state machines, edge cases, metrics, and support flows.
  6. Produce a phased roadmap with P0/P1/P2, but ensure every P0 item is production-shaped.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not treat a feature list as an operating system; every P0 system needs states, owners, and metrics.
  • Do not invent market proof, revenue, or compliance claims without evidence boundaries.
  • Do not optimize launch speed by skipping payments, support, entitlement, or trust surfaces.

Output format

Product type:
Wedge:
Business model:
Distribution channels:

P0 product operating system:
- <system> — user promise, states, edge cases, metrics

P1/P2 roadmap:
- <system> — why later, dependency, proof needed

Risks:
- <risk and mitigation>

Comments

Markdown supported