festina-define-product

Guide Socratic Q&A to define products and generate structured documentation.

1|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/mattfletcher94/festinalente --skill festina-define-product
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: festina-define-product
Source: https://github.com/mattfletcher94/festinalente/tree/main/apps/festinalente/src/content/skills/festina-define-product
Command: npx skills add https://github.com/mattfletcher94/festinalente --skill festina-define-product

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the early-stage product definition process by guiding teams through a Socratic Q&A and automatically generating structured product documentation.

Core Features & Use Cases

  • Guided Q&A to surface product name, purpose, target users, feature groupings, and domain structure.
  • Automatic generation of domain-based docs and templates, including an overview and feature/concept docs.
  • Incremental, user-validated documentation workflow that preserves context for later sessions.

Quick Start

Launch the define-product workflow and answer the guided questions to generate the product documentation.

Frequently Asked Questions about festina-define-product

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

FAQPage Schema
What is Socratic Q&A for product definition and how does it help create product documentation?

Socratic Q&A for product definition is a guided questioning process that surfaces product naming, purpose, users, and domain structure to automatically generate structured product documentation with validated frontmatter.

How do I define a new product and generate domain-based docs from scratch?

To define a new product, launch the guided workflow and answer questions about the product name, purpose, target users, and feature groupings to automatically generate domain folders, overview docs, and feature templates.

Can I incrementally validate product documentation and preserve context for later sessions?

Yes, you can incrementally validate product documentation through a user-validated workflow that preserves context for later sessions, ensuring structured frontmatter and domain folders are maintained across updates.

What's the best way to structure domain folders and frontmatter for early-stage product discovery?

The best way to structure domain folders and frontmatter during early product discovery is by enforcing structured metadata fields including id, type, title, summary, keywords, and updated dates within your generated documentation templates.

Does this guided product definition workflow require any prior templates or dependencies?

No prior templates or dependencies are required to run the product definition workflow, as it automatically generates the necessary domain-based docs, feature templates, and concept docs from your Q&A responses.