visionary

To turn a raw business vision into a structured EPIC document, the Skill convenes specialized analysis lenses to validate product strategy, producing a multi-domain architecture, integration contracts, and board briefs.

Validating technical feasibility and business viability for a product strategy requires convening a multi-perspective analysis panel, such as a Board of Directors, to assess go-to-market planning and user needs before generating foundational documentation.

Generating user journey maps and board briefs from a high-level product idea involves clarifying the business vision through structured prompts, which then automatically produces foundational documentation including an EPIC.md file.

Yes, you can use this approach to define monetization models and user personas, as the strategic planning process guides users through clarifying product vision and identifying specific business viability metrics.

Yes, the EPIC strategy generation process requires user input for clarification, ensuring the resulting multi-domain architecture, prioritized PRD roadmap, and integration contracts accurately reflect the initial business vision.

You should avoid using multi-perspective analysis lenses for product roadmap prioritization if you lack a defined business vision, as the process depends on clarifying an initial idea to convene specialized analysis roles effectively.