spec-writer
Transforms ambiguous user requests into rigorous Product Requirements Documents (PRDs). Use when requirements are vague or high-level.
CMS, document processing, and media generation.
Transforms ambiguous user requests into rigorous Product Requirements Documents (PRDs). Use when requirements are vague or high-level.
Writes marketing content (landing pages, tweets, emails) for product features with a casual, direct brand voice. Use when the user ships a feature, needs marketing copy, mentions "marketing content", "landing page", "tweet about", "launch email", "announce", or requests help promoting/explaining product features. Automatically analyzes the codebase to understand the product context before writing.
Create and manage diagrams, illustrations, tables, and visual components for the textbook. Use when adding architecture diagrams, flowcharts, hardware schematics, or data tables.
Translate user stories and informal requirements into EARS (Easy Approach to Requirements Syntax) format. Use when Claude needs to (1) convert user stories to formal requirements, (2) transform informal requirements into structured EARS format, (3) review and improve existing requirements using EARS patterns, (4) create testable, unambiguous system requirements. Triggers on requests like "convert to EARS", "write requirements", "formalize these user stories", "EARS format".
Generate a Product Requirements Document (PRD) for a new feature or major refactoring. Use when planning a feature, large refactoring, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
Guidelines for creating and managing standardized proposal templates and content libraries
Generate professional forensic reports and documentation. Use when creating investigation reports, expert witness documentation, executive summaries, or technical findings. Supports multiple report formats and compliance requirements.
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.
This skill should be used when the user asks to "create a PRD", "write requirements", "define an MVP", "spec out a feature", "plan a demo", "document product requirements", or needs to turn a rough idea into a structured product requirements document. Converts vague ideas into demo-grade PRDs with decision clarity.
This skill should be used when creating, editing, or debugging Mermaid diagrams. It provides comprehensive syntax references for all 20+ Mermaid diagram types including flowcharts, sequence diagrams, class diagrams, ER diagrams, Gantt charts, and more. Use this skill when users ask for diagrams, visualizations, flowcharts, or any Mermaid-related assistance.
Generates a research-grade Product Requirements Document (PRD) defining problems, goals, scope, constraints, and success criteria. Use when creating or updating a PRD for a product or major initiative.
Produces the Messaging & Direction Summary covering product pitch, features/benefits, use cases, audiences, value props, objections, brand pitch, competitive notes, USP, desired emotions.
Enterprise Mermaid diagramming solution with 21 diagram types
Mermaid diagram generation expert. Activate when: - User asks to create flowcharts, sequence diagrams, or architecture diagrams - User mentions "mermaid", "diagram", "visualize flow", "sequence diagram" - Need to document system architecture or data flows - Creating documentation that benefits from visual representation
Generates a research-grade Product Requirements Document (PRD) defining problems, goals, scope, constraints, and success criteria. Use when creating or updating a PRD for a product or major initiative.