write-product

To generate a product.md document, provide your domain or product context to automatically produce a complete file with valid frontmatter and a structured body matching the official template. This ensures correct wiring of referenced artefacts and owner details without manual stitching.

A standardized product.md template includes sections for Problem, Appetite, Sketch, Rabbit holes, No-gos, Target users, Outcome metrics, Product principles, and Stakeholders. These sections align with project context to capture the structured narrative required for product initiatives.

Yes, a product.md scaffold supports portfolio, product, and domain scopes, including parent-child relationships when applicable. It validates mandatory frontmatter fields like type, scope, name, and owner to ensure alignment across different organizational levels.

The best way to document a product pitch is to supply minimal context to an automated product.md generator. It applies the frontmatter and section structure to produce a consistent, ready-to-use artifact, reducing manual drafting time and ensuring organizational template alignment.

Validating frontmatter fields like type, scope, name, and owner is handled automatically during product.md generation. The process checks these mandatory fields against the provided context to ensure the document meets organizational template standards before output.

You need a frontmatter-driven product.md file when onboarding new initiatives, creating domain strategies, or documenting product pitches. It captures the scope, owner, related artefacts, and structured narrative required to align stakeholders and standardize documentation.