| name | write-requirements |
| description | Write user stories, acceptance criteria, and technical requirements for a feature or change. Use when defining what needs to be built. |
| argument-hint | [feature description] |
| context | fork |
| agent | product-manager |
Write Requirements
Write detailed requirements for the following feature:
$ARGUMENTS
Requirements Format
For each requirement, produce:
User Story
As a [user type],
I want to [action],
So that [benefit].
Acceptance Criteria
Technical Requirements
- Data model changes needed
- API endpoints affected
- UI components affected
- Non-functional requirements (performance, security, accessibility)
Out of Scope
- What is explicitly NOT included in this feature
Context
This is for the llmops-demo-ts project — a chat-based AI agent application. Consider all layers: frontend (Vue.js), backend (Express), agents (LangGraph), and common (shared types).