writing-specs-designs

Generate spec and design doc packs with diagrams, user flows, and acceptance criteria.

5|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/oldwinter/skills --skill writing-specs-designs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-specs-designs
Source: https://github.com/oldwinter/skills/tree/main/lenny-skills/product-skills/writing-specs-designs
Command: npx skills add https://github.com/oldwinter/skills --skill writing-specs-designs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of translating ideas into actionable specifications and design documents, ensuring clarity and alignment between product, design, and engineering teams.

Core Features & Use Cases

  • Spec & Design Doc Generation: Produces comprehensive documentation including diagrams, user flows, acceptance criteria, and measurement plans.
  • Artifact Creation: Generates low-fidelity diagrams, user flows, prototype briefs, and testable acceptance criteria.
  • Use Case: When tasked with "Write a spec for a new feature," this Skill will generate a detailed document pack that engineering can use to start building, including a diagram of the moving pieces, user flows, and clear acceptance criteria.

Quick Start

Use the writing-specs-designs skill to create a spec and design doc for a new user profile editing feature.

Frequently Asked Questions about writing-specs-designs

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

FAQPage Schema
How do I write a build-ready product spec and design doc for a new feature?

To write a build-ready product spec and design doc, generate a comprehensive pack including low-fi diagrams, user flows, prototype briefs, and acceptance criteria. This translates insights into concrete artifacts for product, design, and engineering alignment.

What is included in a comprehensive feature design document?

A comprehensive feature design document includes low-fidelity diagrams of moving pieces, detailed user flows, prototype briefs, testable acceptance criteria, and measurement plans to ensure full team alignment before engineering begins.

How do I define acceptance criteria and user flows for a UX change?

Define acceptance criteria and user flows for a UX change by converting product insights into testable requirements and low-fi diagrams. This process ensures the generated design doc facilitates clear alignment between design and engineering teams.

Can I generate mobile-specific interaction design and tap economy considerations?

Yes, you can generate mobile-specific interaction design considerations. The spec and design doc pack supports tap economy analysis and interaction cost optimization to ensure mobile UX changes are efficient and actionable for engineering.

What is the best way to align product, design, and engineering teams on a feature?

The best way to align product, design, and engineering teams is to generate a single spec and design doc pack. This provides shared, concrete artifacts like user flows and acceptance criteria, replacing ambiguous insights with actionable documentation.