Agent skill · product strategy · nexu-io
pm-spec
Product spec / PRD as a single page — problem, success metrics, scope, user stories, design notes, rollout plan, open questions. Use when the brief mentions "PRD", "spec", "product spec", "feature brief", or "需求文档".
Why this skill is useful
Provides a structured template for creating product specs that standardizes the format and content, which the AI may not generate consistently on its own.
What it needs
About 1k tokens when loaded. Last updated 2026-08-07. 84,236 stars on the source repository.
What this skill does
Product Spec Skill Produce a one-page product spec / PRD. Workflow 1. Read the active DESIGN.md. 2. Identify the feature + audience from the brief. 3. Layout: Header strip: title, status pill (Draft / Review / Approved), date, owner. Three-line summary at the top — what, who, why now. "Problem" panel with one paragraph and a quote from a customer or internal partner. "Goals & non-goals" two-column block. "Success metrics" table with metric / target / measurement. "User stories" list with as-a / I-want / so-that format. "Scope" milestone tracker (3–4 phases). "Open questions" with assignee chips. 4. One inline <style>, semantic HTML, accent used twice max. Output contract
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nexu-io/pm-spec--e56206