hs-requirement-change

Create Hot Sheet requirement change tickets from natural language requests.

1|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/brianwestphal/apple-fm --skill hs-requirement-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hs-requirement-change
Source: https://github.com/brianwestphal/apple-fm/tree/main/.claude/skills/hs-requirement-change
Command: npx skills add https://github.com/brianwestphal/apple-fm --skill hs-requirement-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of Hot Sheet requirement change tickets by converting user requests into properly categorized tickets without manual entry.

Core Features & Use Cases

  • Requirement Change Ticket Creation: Creates Hot Sheet tickets with the correct requirement_change category and title handling.
  • Up Next Parsing: Detects requests marked as next, up next, or do next and assigns the appropriate priority flag.
  • Use Case: A product team member can quickly submit a change request and have it recorded in Hot Sheet with consistent metadata and routing.

Quick Start

Create a Hot Sheet requirement change ticket for updating the checkout flow.

Frequently Asked Questions about hs-requirement-change

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

FAQPage Schema
How do I automate requirement change ticket creation for product management?

You can create requirement change tickets by submitting natural language requests, which are automatically parsed to assign the correct category, title, and priority flags for Hot Sheet tracking.

What is the best way to track requirement changes in a product management workflow?

The best way to track requirement changes is by generating structured tickets from natural language requests, ensuring consistent categorization and priority handling across all product management updates.

How do I set priority flags when submitting a requirement update request?

Priority flags for requirement updates are set by detecting specific keywords like 'next', 'up next', or 'do next' in the request, which automatically assigns the appropriate priority level to the ticket.

Do I need a specific interface to submit requirement change records?

Yes, submitting validated requirement change records requires access to the Hot Sheet ticket creation interface or a fallback API endpoint to properly process and record the categorized tickets.

Can I create a Hot Sheet ticket from a natural language product request?

Yes, natural language product requests can be converted into Hot Sheet tickets by automatically parsing the input to apply the correct requirement change category, title formatting, and priority handling.

Why does manual requirement change entry cause workflow issues?

Manual requirement change entry causes workflow issues because it lacks consistent metadata, proper categorization, and standardized priority handling, leading to misrouted tickets and tracking inconsistencies across the product team.