skills.rest
Keimoshi
KeimoshiCOMMUNITY
Explore all skills by this author →
GitHub

pm-spec

Generates a one-page product spec or PRD as a styled HTML artifact.

Updated May 20, 2026
Search Tags:#html#product management#roadmap#user stories#prd#product spec#feature brief
One-click install
npx skills add https://github.com/Keimoshi/Silverloft --skill pm-spec-keimoshi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-spec
Source: https://github.com/Keimoshi/Silverloft/tree/main/open-design-port/skills/pm-spec
Command: npx skills add https://github.com/Keimoshi/Silverloft --skill pm-spec-keimoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a product spec or PRD from scratch is slow and inconsistent; this Skill turns a feature brief into a structured, presentation-ready one-page spec covering problem, goals, metrics, stories, milestones, and open questions. ## Core Features & Use Cases - Structured PRD Layout: Produces a header with status pill, three-line summary, problem panel with customer quote, goals/non-goals columns, success metrics table, user stories, milestone tracker, and open questions with assignees. - Design-System Aware: Reads the active DESIGN.md and applies color, typography, layout, and component rules with a single inline style block. - Use Case: Ask for a PRD for adding two-factor authentication to your SaaS app and receive a complete HTML spec with phases, targets, and assigned open questions ready for review. ## Quick Start Write me a PRD for adding two-factor auth to our SaaS app with problem, scope, milestones, and open questions.

Frequently Asked Questions about pm-spec

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

FAQPage Schema
How do I generate a PRD from a feature brief?▼

Provide a brief describing the feature and audience, and the Skill produces a one-page HTML spec with problem statement, goals and non-goals, success metrics, user stories, rollout milestones, and open questions. Trigger it with terms like PRD, spec, or feature brief.

What sections does a generated product spec include?▼

The spec includes a header with status pill and owner, a three-line summary, a problem panel with a customer quote, goals and non-goals columns, a success metrics table, as-a/I-want/so-that user stories, a 3-4 phase milestone tracker, and open questions with assignee chips.

What output format does the pm-spec skill produce?▼

It outputs a single text/html artifact containing a complete HTML document with one inline style block and semantic markup. The preview entry point is index.html in desktop prototype mode.

Does the spec generator require a design system file?▼

Yes, the workflow reads the active DESIGN.md before layout and requires design system sections for color, typography, layout, and components. The accent color is used at most twice in the rendered page.

When should I not use a one-page HTML spec?▼

Avoid it for multi-document programs, API technical specifications, or specs needing collaborative editing and versioning. It is designed for single-feature PRDs presented as a static one-page artifact, not living documents.

Related Skills

Explore More Product & Management Skills→
hulusi-tunchulusi-tunc
3

design-brief

Generates design briefs with problem statements, target audience, and success criteria.

Community
Intermediate
sd0xdevsd0xdev
189

project-brief

Convert technical specifications into PM/CTO-readable executive summaries.

Community
Intermediate
phoenicisfphoenicisf

business-analyst

Guide product discovery and create comprehensive product briefs.

Community
Advanced
Permit-JunctionPermit-Junction

da-content-authoring

Guide users through creating and editing pages, blocks, sections, and media in the DA web-based editor for AEM Edge Delivery Services.

Official
Intermediate