create-menu

Generate a structured Product Requirement Document from a free-form project brief.

1|Updated Mar 27, 2026

Search Tags:#workflow #planning #documentation #requirements #prd #product-management

Ready to run

npx skills add https://github.com/steve-piece/bytheslice --skill create-menu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-menu
Source: https://github.com/steve-piece/bytheslice/tree/main/skills/create-menu
Command: npx skills add https://github.com/steve-piece/bytheslice --skill create-menu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates the ambiguity and structural gaps common in early-stage project planning by transforming free-form briefs into comprehensive, standardized Product Requirement Documents.

Core Features & Use Cases

Structured PRD Generation: Maps project requirements into an 8-section template including functional and non-functional requirements.
Ambiguity Resolution: Uses a mandatory plan-mode question gate to clarify scope, target users, and monetization before writing.
Quality Assurance: Integrates an automated review loop to ensure consistency and alignment with project defaults.

Quick Start

Use the create-menu skill to generate a PRD for the project described in the attached brief.

Frequently Asked Questions about create-menu

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

FAQPage Schema

How do I turn a project brief into a structured PRD?▼

To turn a project brief into a structured PRD, you provide the free-form brief, and the system resolves ambiguities through a mandatory question gate before generating an 8-section document mapping all functional and non-functional requirements.

What is the best way to resolve ambiguities when writing product requirements documentation?▼

The best way to resolve ambiguities in product requirements documentation is using a structured plan-mode question gate that clarifies scope, target users, and monetization details before the PRD generation process begins.

How does an automated review loop ensure PRD consistency?▼

An automated review loop ensures PRD consistency by validating the generated document against predefined technical architecture and project defaults, checking that all mapped functional requirements align before downstream implementation.

Do I need a fully defined scope to generate product management documentation?▼

No, you do not need a fully defined scope to generate product management documentation; the system accepts free-form project briefs and actively resolves missing target user, scope, and monetization details during processing.

What sections are included in a canonical Product Requirement Document?▼

A canonical Product Requirement Document includes an 8-section template that comprehensively maps both functional and non-functional requirements to ensure complete project planning alignment.

When should I use an automated PRD generator instead of manual documentation?▼

You should use an automated PRD generator instead of manual documentation during early-stage project planning to eliminate structural gaps, standardize requirement mapping, and validate technical architecture before development begins.