requirements-engineering
Use when "requirements document", "acceptance criteria", "user stories", "EARS format", "specification", "feature spec", "product requirements"
Discover business sales marketing skills, compare source repositories and read the instructions for each workflow.
Use when "requirements document", "acceptance criteria", "user stories", "EARS format", "specification", "feature spec", "product requirements"
This skill should be used when the user asks to "plan team structure", "determine hiring needs", "design org chart", "calculate compensation", "plan equity allocation", or requests organizational design and hea...
Transform raw research into polished newsletter articles for Edmund Bogen's luxury real estate audience. Use when Edmund provides research, data, or topics and needs a complete newsletter article created. Follo...
This skill should be used when the user asks to "create a workflow diagram", "visualize a workflow", "generate a process flow", "make a flowchart", "diagram these steps", or provides workflow steps that need vi...
Development workflow emphasizing test-first development, task classification, and appropriate tracking. Use when starting implementation, planning changes, or structuring development work.
Interviews users to clarify their thinking instead of writing for them. Use when asked to help with writing, content ideas, exploring topics, or reviewing drafts. Reads existing notes to identify themes, asks p...
Comprehensive UI/UX design principles for web applications based on Sociomedia Human Interface Guidelines (SHIG). Use when Claude needs to design or review web application interfaces, evaluate UI/UX decisions a...
Storybook expert for Angular 21+ component development, visual testing, and design system documentation
UX design expert for user research, personas, journey mapping, information architecture, wireframing, prototyping, usability testing, and accessibility. Creates user-centered designs with WCAG 2.1 AA/AAA compli...
Create user stories and epic design documents. Use when defining new features, writing Given-When-Then criteria, creating story logs, or designing larger features.
Règles métier et KPIs pour société de service IT. Use when "business rules", "kpi", "taux occupation", "marge", "staffing", "intercontrat", "forecast", "utilization".
Conducts structured requirements interviews for spec documents. Use when gathering requirements, writing specs, planning features, creating PRDs, or when user mentions "interview", "requirements", "spec", "PRD"...
Fix implementation plans through iterative gap analysis. Use when user wants to verify a plan, fix a plan, check for gaps, validate an implementation plan, or ensure a plan is complete.
Understand and apply psychological concepts to create superior user experiences (UX) in frontend design.
Guidelines for creating task-oriented how-to guide documentation. Use when writing content that helps users accomplish specific goals.
Guidelines for creating learning-oriented tutorial documentation. Use when writing step-by-step content that helps users learn by doing.
Guidelines for creating architecture overview and system explanation documentation. Use when writing content that clarifies system design, data flow, and architectural concepts.
Guidelines for creating technical specification and API reference documentation. Use when writing factual, complete content about data models, API contracts, and configuration options.
Guidelines for developing the MHS small business automation tool
Generate quarterly sales reports with executive summary, regional breakdown, and trend analysis. Use for formal business reporting.
Provides detailed guidance on how to implement a single plan step while adhering to architecture and quality standards.
Breaks high-level goals into an incremental, prioritised plan using the plan template.
Guides the creation and review of Architectural Decision Records (ADRs). Use this skill when a significant architectural change is proposed, a new technology is introduced, or a trade-off needs to be documented...
Extracts structured requirements, acceptance criteria and risks from user requests and existing product documentation.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.