archflow-agent-product-strategist

Generates product vision, personas, KPIs, and stack decisions into a project-context markdown file.

28|4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AZidan/archflow --skill archflow-agent-product-strategist-azidan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archflow-agent-product-strategist
Source: https://github.com/AZidan/archflow/tree/main/adapters/generic/.agents/skills/archflow-agent-product-strategist
Command: npx skills add https://github.com/AZidan/archflow --skill archflow-agent-product-strategist-azidan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Early-stage product ideas often lack a documented strategic foundation, causing downstream design and engineering work to drift without shared goals, personas, or success metrics. ## Core Features & Use Cases - Strategic Foundation: Defines product vision, business goals, measurable KPIs, and product-market fit indicators. - User and Market Analysis: Builds detailed personas with pain points, maps user journeys, and assesses competitive positioning. - Canonical Output: Writes all decisions to .archflow/project-context.md, which later Archflow phases (feature-planner, ux-designer, api-contract-architect) read as their single source of truth. - Use Case: When starting a new product in the Archflow framework, this role runs first in Phase 1 to produce the strategy document every subsequent agent builds on. ## Quick Start Ask the agent to act as the Archflow product-strategist and define the product vision, personas, KPIs, and stack decisions for your idea into .archflow/project-context.md.

Frequently Asked Questions about archflow-agent-product-strategist

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

FAQPage Schema
How do I define a product strategy with an AI agent?

Invoke the product-strategist role with your product idea or existing context. It researches the market, defines vision, personas, KPIs, and positioning, then writes everything to .archflow/project-context.md for stakeholder review.

What does the Archflow product-strategist produce?

It produces a single markdown file, .archflow/project-context.md, containing business goals, personas with pain points, KPIs, market positioning, stack decisions, and an explicit list of assumptions to validate.

When does the product-strategist run in the Archflow workflow?

It runs once in Phase 1, before the feature-planner. Later roles such as ux-designer and api-contract-architect read its output file and never re-elicit strategy themselves.

Does the product-strategist complete Phase 1 automatically?

No. After writing the project-context document it stops and waits for approval. It does not create a backlog, cut a release, or advance the phase on its own.

What happens if product requirements are unknown or ambiguous?

Instead of blocking on questions, the strategist records unknowns under an Assumptions to validate section in the document, noting what it assumed and what would change if the assumption is wrong.