kf-advisor-product

Product strategy analysis from a codebase works by examining technical context, market positioning, and competitive landscape to generate actionable reports. It relies on existing project artifacts like product.yaml, guidelines, and tech stack details to guide recommendations.

Generate a competitive analysis report by benchmarking your project's features and positioning against similar tools. Provide a topic prompt like 'competitive analysis' to produce structured recommendations highlighting market differentiation and prioritization gaps.

Yes, analyzing product strategy relies on existing project artifacts such as product.yaml, guidelines, tech stack, and track context. These files provide the necessary project context to guide accurate strategy recommendations.

Translate technical architecture into product roadmapping by analyzing the codebase to identify high-impact opportunities. This approach converts technical implementation details into structured business direction for stakeholder alignment.

Yes, you can hand off product strategy reports directly to an architecture track. The analysis produces structured handoff-ready artifacts specifically tailored for the /kf-architect track to align stakeholders around clear next steps.

Avoid automated codebase analysis for product strategy when your project lacks existing artifacts like product.yaml, guidelines, or established tech stack context. The analysis depends on these inputs to generate accurate, context-aware recommendations.