devlyn:product-spec

Generate or update a build-ready product specification with YAML frontmatter.

4|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/fysoul17/ian-on-v1 --skill devlyn-product-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: devlyn:product-spec
Source: https://github.com/fysoul17/ian-on-v1/tree/main/ian-on/.claude/skills/devlyn%3Aproduct-spec
Command: npx skills add https://github.com/fysoul17/ian-on-v1 --skill devlyn-product-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill converts vague product direction into a structured, build-ready Product Spec so downstream agents can reliably generate feature specs, plans, and implementation work without ambiguity.

Core Features & Use Cases

  • Create a complete Product Spec from a template when no existing spec is present.
  • Update an existing Product Spec incrementally by applying targeted changes while preserving other sections.
  • Separate product intent from implementation details by keeping domain and decisions while filtering out low-level tech syntax, environment variables, and API boilerplate.
  • Enforce quality and completeness with required fields, consistent entity/behavior coverage, permissions, limits, integrations, views, and validation guidance.
  • Scope work across phases (MVP vs later enhancements) to ensure the first release supports the core value loop end-to-end.

Quick Start

Ask the Skill to create or update a Product Spec by providing your product description or the specific changes you want applied to the existing spec.

Frequently Asked Questions about devlyn:product-spec

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

FAQPage Schema
How do I turn a vague product idea into a build-ready product spec?

To turn a vague product idea into a build-ready spec, provide your product description to generate a structured document at docs/product-spec.md. It enforces required fields, entity coverage, and MVP scoping while filtering out low-level implementation details.

Can I incrementally update an existing PRD without rewriting the entire document?

Yes, you can incrementally update an existing PRD by applying targeted changes while preserving other sections. This human-in-the-loop approach modifies specific product spec sections without rewriting the entire document.

What is the difference between product intent and implementation details in a feature spec?

Product intent in a feature spec captures domain rules and decisions, while implementation details include low-level tech syntax, environment variables, and API boilerplate. A proper product spec preserves intent and filters out implementation details.

How do I scope MVP features versus later enhancements in product planning?

Scoping MVP features versus later enhancements involves defining work across phases to ensure the first release supports the core value loop end-to-end. The product spec separates MVP requirements from future enhancements during feature planning.

Does generating a product spec require technical configuration or API setup?

Generating a product spec does not require technical configuration or API setup. It filters out environment variables and API boilerplate, focusing purely on product domain rules, permissions, limits, and validation guidance.