prd-from-grill-me

Interview users, explore the repository, and generate a PRD as a GitLab issue.

Updated Mar 24, 2026

Search Tags:#requirements #prd #product-management #user-interviews #module-design #gitlab-issues

Ready to run

npx skills add https://github.com/stevenengland/sten-agent-skills --skill prd-from-grill-me

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: prd-from-grill-me
Source: https://github.com/stevenengland/sten-agent-skills/tree/main/skills/prd-from-grill-me
Command: npx skills add https://github.com/stevenengland/sten-agent-skills --skill prd-from-grill-me

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps product teams convert user interviews, repo context, and design insights into a complete PRD and automatically submit it as a GitLab issue.

Core Features & Use Cases

Guided interview synthesis to capture user needs and constraints.
Codebase and module exploration to surface dependencies and scope.
PRD generation using a structured template aligned with GitLab issues.
One-click submission to GitLab with tracking and versioning.

Quick Start

Describe the problem you want solved in detail and I will generate a PRD and submit it as a GitLab issue.

Frequently Asked Questions about prd-from-grill-me

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

FAQPage Schema

How do I generate a PRD from user interviews?▼

Generating a PRD from user interviews requires synthesizing user needs, exploring the codebase for scope, and outlining module designs. This skill automates capturing problem statements, detailing user stories, and formatting the output into a structured GitLab issue template.

Can I automatically submit a product requirement document as a GitLab issue?▼

Yes, submitting a product requirement document as a GitLab issue is supported. The skill formats the finalized PRD into a GitLab issue template and handles the submission, providing tracking and versioning for the product initiative.

What is the best way to align stakeholders before feature development?▼

Aligning stakeholders before feature development is best achieved by creating a formal PRD. This process captures problem statements, proposes solutions, and documents implementation decisions to guide module design and track requirements.

How do I capture user stories and implementation decisions for a new module?▼

Capturing user stories and implementation decisions involves guided interview synthesis and module exploration. This skill automates detailing user stories and documenting technical constraints directly into a structured PRD format.

Does this PRD generation process require existing repository context?▼

Yes, the PRD generation process uses existing repository context. It explores the codebase and module dependencies to surface constraints and accurately scope the proposed solutions before outlining the final requirement document.

What limitations exist when automating PRD creation from interviews?▼

Automating PRD creation from interviews is limited by the depth of the initial problem description and the available codebase context. Without sufficient user input or repository access, the generated problem statements and module designs may lack necessary technical detail.