from lola-opencode20
Generate clear, actionable Product Requirements Documents (PRDs) with user stories and acceptance criteria, saved to the repo's tasks/ directory for autonomous
This skill turns a short feature brief into a structured Product Requirements Document (PRD) suitable for autonomous agents or developer handoff. It prompts for 3–5 clarifying questions with lettered options, produces measurable goals, a set of small user stories (each with ID, title, description, and acceptance criteria), functional requirements, non-goals, and optional technical notes. The output is saved to tasks/prd-[feature-name].md for traceability.
Use when you need to convert an informal feature request into a developer-ready specification: planning new features, scoping work for agent-based task runners, or preparing small, shippable user stories that fit a single context window. Ideal for product managers, developer-automation flows, and CI-driven task creators.
Likely compatible with general-purpose agent runners and autonomous authoring agents (e.g., Codex-based or Claude-like agents) that can write files and run simple shell commands.
This skill has not been reviewed by our automated audit pipeline yet.
