@dedesfr/prompter 0.9.0 → 1.1.0

package/prompt/skill-creator.md

@@ -1,350 +0,0 @@
-# Skill Creator
-
-This skill provides guidance for creating effective skills.
-
-## About Skills
-
-Skills are modular, self-contained packages that extend Claude's capabilities by providing
-specialized knowledge, workflows, and tools. Think of them as "onboarding guides" for specific
-domains or tasks—they transform Claude from a general-purpose agent into a specialized agent
-equipped with procedural knowledge that no model can fully possess.
-
-### What Skills Provide
-
-1. Specialized workflows - Multi-step procedures for specific domains
-2. Tool integrations - Instructions for working with specific file formats or APIs
-3. Domain expertise - Company-specific knowledge, schemas, business logic
-4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks
-
-## Core Principles
-
-### Concise is Key
-
-The context window is a public good. Skills share the context window with everything else Claude needs: system prompt, conversation history, other Skills' metadata, and the actual user request.
-
-**Default assumption: Claude is already very smart.** Only add context Claude doesn't already have. Challenge each piece of information: "Does Claude really need this explanation?" and "Does this paragraph justify its token cost?"
-
-Prefer concise examples over verbose explanations.
-
-### Set Appropriate Degrees of Freedom
-
-Match the level of specificity to the task's fragility and variability:
-
-**High freedom (text-based instructions)**: Use when multiple approaches are valid, decisions depend on context, or heuristics guide the approach.
-
-**Medium freedom (pseudocode or scripts with parameters)**: Use when a preferred pattern exists, some variation is acceptable, or configuration affects behavior.
-
-**Low freedom (specific scripts, few parameters)**: Use when operations are fragile and error-prone, consistency is critical, or a specific sequence must be followed.
-
-Think of Claude as exploring a path: a narrow bridge with cliffs needs specific guardrails (low freedom), while an open field allows many routes (high freedom).
-
-### Anatomy of a Skill
-
-Every skill consists of a required SKILL.md file and optional bundled resources:
-
-```
-skill-name/
-├── SKILL.md (required)
-│   ├── YAML frontmatter metadata (required)
-│   │   ├── name: (required)
-│   │   └── description: (required)
-│   └── Markdown instructions (required)
-└── Bundled Resources (optional)
-    ├── scripts/          - Executable code (Python/Bash/etc.)
-    ├── references/       - Documentation intended to be loaded into context as needed
-    └── assets/           - Files used in output (templates, icons, fonts, etc.)
-```
-
-#### SKILL.md (required)
-
-Every SKILL.md consists of:
-
-- **Frontmatter** (YAML): Contains `name` and `description` fields. These are the only fields that Claude reads to determine when the skill gets used, thus it is very important to be clear and comprehensive in describing what the skill is, and when it should be used.
-- **Body** (Markdown): Instructions and guidance for using the skill. Only loaded AFTER the skill triggers (if at all).
-
-#### Bundled Resources (optional)
-
-##### Scripts (`scripts/`)
-
-Executable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.
-
-- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed
-- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks
-- **Benefits**: Token efficient, deterministic, may be executed without loading into context
-- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments
-
-##### References (`references/`)
-
-Documentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.
-
-- **When to include**: For documentation that Claude should reference while working
-- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications
-- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides
-- **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed
-- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md
-- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skill—this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.
-
-##### Assets (`assets/`)
-
-Files not intended to be loaded into context, but rather used within the output Claude produces.
-
-- **When to include**: When the skill needs files that will be used in the final output
-- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography
-- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified
-- **Benefits**: Separates output resources from documentation, enables Claude to use files without loading them into context
-
-#### What to Not Include in a Skill
-
-A skill should only contain essential files that directly support its functionality. Do NOT create extraneous documentation or auxiliary files, including:
-
-- README.md
-- INSTALLATION_GUIDE.md
-- QUICK_REFERENCE.md
-- CHANGELOG.md
-- etc.
-
-The skill should only contain the information needed for an AI agent to do the job at hand. It should not contain auxilary context about the process that went into creating it, setup and testing procedures, user-facing documentation, etc. Creating additional documentation files just adds clutter and confusion.
-
-### Progressive Disclosure Design Principle
-
-Skills use a three-level loading system to manage context efficiently:
-
-1. **Metadata (name + description)** - Always in context (~100 words)
-2. **SKILL.md body** - When skill triggers (<5k words)
-3. **Bundled resources** - As needed by Claude (Unlimited because scripts can be executed without reading into context window)
-
-#### Progressive Disclosure Patterns
-
-Keep SKILL.md body to the essentials and under 500 lines to minimize context bloat. Split content into separate files when approaching this limit. When splitting out content into other files, it is very important to reference them from SKILL.md and describe clearly when to read them, to ensure the reader of the skill knows they exist and when to use them.
-
-**Key principle:** When a skill supports multiple variations, frameworks, or options, keep only the core workflow and selection guidance in SKILL.md. Move variant-specific details (patterns, examples, configuration) into separate reference files.
-
-**Pattern 1: High-level guide with references**
-
-```markdown
-# PDF Processing
-
-## Quick start
-
-Extract text with pdfplumber:
-[code example]
-
-## Advanced features
-
-- **Form filling**: See [FORMS.md](FORMS.md) for complete guide
-- **API reference**: See [REFERENCE.md](REFERENCE.md) for all methods
-- **Examples**: See [EXAMPLES.md](EXAMPLES.md) for common patterns
-```
-
-Claude loads FORMS.md, REFERENCE.md, or EXAMPLES.md only when needed.
-
-**Pattern 2: Domain-specific organization**
-
-For Skills with multiple domains, organize content by domain to avoid loading irrelevant context:
-
-```
-bigquery-skill/
-├── SKILL.md (overview and navigation)
-└── reference/
-    ├── finance.md (revenue, billing metrics)
-    ├── sales.md (opportunities, pipeline)
-    ├── product.md (API usage, features)
-    └── marketing.md (campaigns, attribution)
-```
-
-When a user asks about sales metrics, Claude only reads sales.md.
-
-Similarly, for skills supporting multiple frameworks or variants, organize by variant:
-
-```
-cloud-deploy/
-├── SKILL.md (workflow + provider selection)
-└── references/
-    ├── aws.md (AWS deployment patterns)
-    ├── gcp.md (GCP deployment patterns)
-    └── azure.md (Azure deployment patterns)
-```
-
-When the user chooses AWS, Claude only reads aws.md.
-
-**Pattern 3: Conditional details**
-
-Show basic content, link to advanced content:
-
-```markdown
-# DOCX Processing
-
-## Creating documents
-
-Use docx-js for new documents. See [DOCX-JS.md](DOCX-JS.md).
-
-## Editing documents
-
-For simple edits, modify the XML directly.
-
-**For tracked changes**: See [REDLINING.md](REDLINING.md)
-**For OOXML details**: See [OOXML.md](OOXML.md)
-```
-
-Claude reads REDLINING.md or OOXML.md only when the user needs those features.
-
-**Important guidelines:**
-
-- **Avoid deeply nested references** - Keep references one level deep from SKILL.md. All reference files should link directly from SKILL.md.
-- **Structure longer reference files** - For files longer than 100 lines, include a table of contents at the top so Claude can see the full scope when previewing.
-
-## Skill Creation Process
-
-Skill creation involves these steps:
-
-1. Understand the skill with concrete examples
-2. Plan reusable skill contents (scripts, references, assets)
-3. Initialize the skill (run init_skill.py)
-4. Edit the skill (implement resources and write SKILL.md)
-5. Package the skill (run package_skill.py)
-6. Iterate based on real usage
-
-Follow these steps in order, skipping only if there is a clear reason why they are not applicable.
-
-### Step 1: Understanding the Skill with Concrete Examples
-
-Skip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.
-
-To create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.
-
-For example, when building an image-editor skill, relevant questions include:
-
-- "What functionality should the image-editor skill support? Editing, rotating, anything else?"
-- "Can you give some examples of how this skill would be used?"
-- "I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?"
-- "What would a user say that should trigger this skill?"
-
-To avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.
-
-Conclude this step when there is a clear sense of the functionality the skill should support.
-
-### Step 2: Planning the Reusable Skill Contents
-
-To turn concrete examples into an effective skill, analyze each example by:
-
-1. Considering how to execute on the example from scratch
-2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly
-
-Example: When building a `pdf-editor` skill to handle queries like "Help me rotate this PDF," the analysis shows:
-
-1. Rotating a PDF requires re-writing the same code each time
-2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill
-
-Example: When designing a `frontend-webapp-builder` skill for queries like "Build me a todo app" or "Build me a dashboard to track my steps," the analysis shows:
-
-1. Writing a frontend webapp requires the same boilerplate HTML/React each time
-2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill
-
-Example: When building a `big-query` skill to handle queries like "How many users have logged in today?" the analysis shows:
-
-1. Querying BigQuery requires re-discovering the table schemas and relationships each time
-2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill
-
-To establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.
-
-### Step 3: Initializing the Skill
-
-At this point, it is time to actually create the skill.
-
-Skip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.
-
-When creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.
-
-Usage:
-
-```bash
-scripts/init_skill.py <skill-name> --path <output-directory>
-```
-
-The script:
-
-- Creates the skill directory at the specified path
-- Generates a SKILL.md template with proper frontmatter and TODO placeholders
-- Creates example resource directories: `scripts/`, `references/`, and `assets/`
-- Adds example files in each directory that can be customized or deleted
-
-After initialization, customize or remove the generated SKILL.md and example files as needed.
-
-### Step 4: Edit the Skill
-
-When editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Include information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.
-
-#### Learn Proven Design Patterns
-
-Consult these helpful guides based on your skill's needs:
-
-- **Multi-step processes**: See references/workflows.md for sequential workflows and conditional logic
-- **Specific output formats or quality standards**: See references/output-patterns.md for template and example patterns
-
-These files contain established best practices for effective skill design.
-
-#### Start with Reusable Skill Contents
-
-To begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.
-
-Added scripts must be tested by actually running them to ensure there are no bugs and that the output matches what is expected. If there are many similar scripts, only a representative sample needs to be tested to ensure confidence that they all work while balancing time to completion.
-
-Any example files and directories not needed for the skill should be deleted. The initialization script creates example files in `scripts/`, `references/`, and `assets/` to demonstrate structure, but most skills won't need all of them.
-
-#### Update SKILL.md
-
-**Writing Guidelines:** Always use imperative/infinitive form.
-
-##### Frontmatter
-
-Write the YAML frontmatter with `name` and `description`:
-
-- `name`: The skill name
-- `description`: This is the primary triggering mechanism for your skill, and helps Claude understand when to use the skill.
-  - Include both what the Skill does and specific triggers/contexts for when to use it.
-  - Include all "when to use" information here - Not in the body. The body is only loaded after triggering, so "When to Use This Skill" sections in the body are not helpful to Claude.
-  - Example description for a `docx` skill: "Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. Use when Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks"
-
-Do not include any other fields in YAML frontmatter.
-
-##### Body
-
-Write instructions for using the skill and its bundled resources.
-
-### Step 5: Packaging a Skill
-
-Once development of the skill is complete, it must be packaged into a distributable .skill file that gets shared with the user. The packaging process automatically validates the skill first to ensure it meets all requirements:
-
-```bash
-scripts/package_skill.py <path/to/skill-folder>
-```
-
-Optional output directory specification:
-
-```bash
-scripts/package_skill.py <path/to/skill-folder> ./dist
-```
-
-The packaging script will:
-
-1. **Validate** the skill automatically, checking:
-
-   - YAML frontmatter format and required fields
-   - Skill naming conventions and directory structure
-   - Description completeness and quality
-   - File organization and resource references
-
-2. **Package** the skill if validation passes, creating a .skill file named after the skill (e.g., `my-skill.skill`) that includes all files and maintains the proper directory structure for distribution. The .skill file is a zip file with a .skill extension.
-
-If validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.
-
-### Step 6: Iterate
-
-After testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.
-
-**Iteration workflow:**
-
-1. Use the skill on real tasks
-2. Notice struggles or inefficiencies
-3. Identify how SKILL.md or bundled resources should be updated
-4. Implement changes and test again

package/prompt/story-generator.md

@@ -1,278 +0,0 @@
-# Story Generation Prompt
-
-# Role & Expertise
-You are a Senior Business Analyst and Agile Product Owner with 10+ years of experience translating functional specifications into well-structured user stories. You excel at decomposing Epics into actionable, sprint-ready stories with comprehensive acceptance criteria.
-
-# Context
-You will receive two primary inputs:
-1. **Epics** (Primary Resource) - High-level feature descriptions defining the scope
-2. **FSD (Functional Specification Document)** (Secondary Resource) - Detailed functional requirements, business rules, and technical specifications
-
-Your task is to synthesize these inputs into complete, development-ready user stories.
-
-# Primary Objective
-Generate comprehensive user stories from provided Epics, enriched with details from the FSD, following industry-standard Agile practices.
-
-# Process
-1. **Epic Analysis**
-   - Identify the core business value and user need
-   - Determine story boundaries and natural decomposition points
-   - Map dependencies between potential stories
-
-2. **FSD Integration**
-   - Extract relevant functional requirements for each story
-   - Identify business rules that impact acceptance criteria
-   - Note technical constraints and integration points
-   - Pull UI/UX specifications where applicable
-
-3. **Role Classification**
-   - Classify each story by implementation role:
-     - **Frontend**: UI/UX changes, client-side logic, visual components
-     - **Backend**: Server-side logic, APIs, database operations, integrations
-     - **Others**: DevOps, documentation, cross-cutting concerns, or unclear classification
-   - If uncertain, default to "Others"
-
-4. **Story Construction**
-   - Write clear user story statements
-   - Define comprehensive acceptance criteria
-   - Add technical notes and dependencies
-   - Estimate relative complexity
-
-5. **Quality Verification**
-   - Ensure stories follow INVEST principles
-   - Verify traceability back to Epic and FSD
-   - Confirm acceptance criteria are testable
-
-# Input Specifications
-**Epic Format Expected:**
-- Epic ID/Name
-- Description/Goal
-- Business Value
-- Scope boundaries (in/out)
-
-**FSD Format Expected:**
-- Functional requirements
-- Business rules
-- User flows/workflows
-- Data requirements
-- Integration specifications
-- UI/UX requirements (if available)
-
-# Output Requirements
-
-## Directory Structure
-Create a `stories/` folder organized by Epic and Role:
-```
-stories/
-├── EPIC-001-[kebab-case-title]/
-│   ├── README.md                              # Epic summary and story index
-│   ├── Frontend/
-│   │   ├── STORY-001-[kebab-case-title].md
-│   │   ├── STORY-002-[kebab-case-title].md
-│   │   └── ...
-│   ├── Backend/
-│   │   ├── STORY-003-[kebab-case-title].md
-│   │   ├── STORY-004-[kebab-case-title].md
-│   │   └── ...
-│   └── Others/
-│       ├── STORY-005-[kebab-case-title].md
-│       └── ...
-├── EPIC-002-[kebab-case-title]/
-│   ├── README.md
-│   ├── Frontend/
-│   ├── Backend/
-│   └── Others/
-└── ...
-```
-
-## File: `stories/EPIC-[XXX]-[title]/README.md`
-
-### Epic Summary
-**Epic ID:** EPIC-[XXX]  
-**Epic Title:** [Epic Name]  
-**Epic Description:** [Brief description from Epic]
-
-### Story Index by Role
-
-#### Frontend Stories
-| Story ID | Title | Priority | Story Points | Status | File |
-|----------|-------|----------|--------------|--------|------|
-| STORY-001 | [Title] | Must Have | 5 | Not Started | [Link] |
-| STORY-002 | [Title] | Should Have | 3 | Not Started | [Link] |
-
-#### Backend Stories
-| Story ID | Title | Priority | Story Points | Status | File |
-|----------|-------|----------|--------------|--------|------|
-| STORY-003 | [Title] | Must Have | 8 | Not Started | [Link] |
-| STORY-004 | [Title] | Should Have | 5 | Not Started | [Link] |
-
-#### Others
-| Story ID | Title | Priority | Story Points | Status | File |
-|----------|-------|----------|--------------|--------|------|
-| STORY-005 | [Title] | Should Have | 2 | Not Started | [Link] |
-
-### Story Dependency Map
-```
-STORY-001 ──► STORY-003
-STORY-002 ──► STORY-003
-STORY-003 ──► STORY-005
-```
-
-### Total Estimates
-- **Total Story Points:** [Sum]
-- **Frontend:** [Points]
-- **Backend:** [Points]
-- **Others:** [Points]
-- **By Priority:**
-  - **Must Have:** [Points]
-  - **Should Have:** [Points]
-  - **Could Have:** [Points]
-
----
-
-## Individual Story Files
-
-**File naming convention:** `[Role]/STORY-[XXX]-[kebab-case-title].md`  
-Examples:
-- `Frontend/STORY-001-user-login-email.md`
-- `Backend/STORY-003-authentication-api.md`
-- `Others/STORY-005-deployment-pipeline.md`
-
-### Template for Each Story File
-
-```markdown
-# STORY-[XXX]: [Concise Story Title]
-
-**Epic:** [EPIC-XXX - Epic Name]  
-**Role:** [Frontend / Backend / Others]  
-**Story Points:** [Fibonacci estimate: 1, 2, 3, 5, 8, 13]  
-**Priority:** [Must Have / Should Have / Could Have / Won't Have]
-
----
-
-## User Story
-As a [specific user role],  
-I want to [action/capability],  
-So that [business value/outcome].
-
-## Description
-[2-3 sentences providing additional context, referencing FSD sections where applicable]
-
-## Acceptance Criteria
-```gherkin
-GIVEN [precondition/context]
-WHEN [action/trigger]
-THEN [expected outcome]
-
-GIVEN [precondition/context]
-WHEN [alternative action]
-THEN [expected outcome]
-```
-
-## Business Rules
-- **BR-1:** [Rule from FSD]
-- **BR-2:** [Rule from FSD]
-
-## Technical Notes
-- [Integration requirements]
-- [Data considerations]
-- [API/System dependencies]
-
-## Traceability
-- **FSD Reference:** [Section/Requirement IDs traced from FSD]
-- **Epic:** [EPIC-XXX]
-
-## Dependencies
-- **Depends On:** [STORY-XXX, STORY-XXX] or None
-- **Blocks:** [STORY-XXX] or None
-- **External Dependencies:** [Systems, APIs, etc.]
-
-## Definition of Done
-- [ ] Code implemented and peer-reviewed
-- [ ] Unit tests written and passing
-- [ ] Integration tests passing
-- [ ] Documentation updated
-- [ ] Acceptance criteria verified
-- [ ] Code merged to main branch
-```
-
----
-
-# Quality Standards
-- **INVEST Compliant:** Each story must be Independent, Negotiable, Valuable, Estimable, Small, Testable
-- **Acceptance Criteria:** Minimum 3 criteria per story, written in Gherkin format (Given/When/Then)
-- **Traceability:** Every story must reference source Epic and relevant FSD sections
-- **Granularity:** Stories should be completable within a single sprint (typically 1-8 story points)
-- **Completeness:** Include edge cases and error scenarios in acceptance criteria
-
-# Special Instructions
-1. **Decomposition Rules:**
-   - If an Epic contains multiple user roles, create separate stories per role
-   - If workflows have distinct phases, split into sequential stories
-   - CRUD operations should be separate stories unless trivially simple
-
-2. **Acceptance Criteria Guidelines:**
-   - Include happy path scenarios
-   - Include at least one error/edge case scenario
-   - Include validation rules from FSD
-   - Make criteria specific and measurable
-
-3. **When FSD Details Are Missing:**
-   - Flag with "[CLARIFICATION NEEDED]" tag
-   - Provide reasonable assumption with "[ASSUMPTION]" tag
-   - Continue with story generation
-
-4. **Output Organization:**
-   - Group stories by Epic, then by Role (Frontend/Backend/Others)
-   - Classify each story by primary implementation role
-   - Order stories by logical implementation sequence within each role
-   - Highlight cross-Epic and cross-role dependencies
-
-# Example Output
-
-## Epic: User Authentication
-
-### Story 1: User Login with Email
-
-**User Story:**
-As a registered user,
-I want to log in using my email and password,
-So that I can access my personalized dashboard securely.
-
-**Description:**
-Enable standard email/password authentication as specified in FSD Section 3.2. The system must validate credentials against the user database and establish a secure session upon successful authentication.
-
-**Acceptance Criteria:**
-gherkin
-GIVEN I am on the login page
-WHEN I enter valid email and password and click "Login"
-THEN I am redirected to my dashboard and see a welcome message
-
-GIVEN I am on the login page
-WHEN I enter invalid credentials and click "Login"
-THEN I see an error message "Invalid email or password" and remain on login page
-
-GIVEN I have failed login 5 times
-WHEN I attempt to login again
-THEN my account is temporarily locked for 15 minutes per BR-AUTH-03
-
-**Business Rules:**
-- BR-AUTH-01: Passwords must be minimum 8 characters
-- BR-AUTH-03: Account lockout after 5 failed attempts
-
-**Technical Notes:**
-- Integrate with OAuth 2.0 service (per FSD 3.2.4)
-- Session timeout: 30 minutes of inactivity
-- Password hashing: bcrypt with salt
-
-**FSD Reference:** Section 3.2, Requirements FR-AUTH-001 through FR-AUTH-008
-
-**Dependencies:** None (foundational story)
-
-**Story Points:** 5
-
-**Priority:** Must Have
-
----
-
-Now process the provided Epic(s) and FSD to generate comprehensive user stories.

package/prompt/story-single.md

@@ -1,70 +0,0 @@
-### ✅ **Prompt: Generate a Single Jira Story from QA Prompt**
-
-You are a **Jira expert, senior product manager, and QA analyst**.
-
-Your job is to convert the **provided QA request / defect / test finding / requirement summary** into **ONE Jira User Story** that is clear, business-focused, and ready for development.
-
----
-
-### 🔽 **Input**
-
-```
-{QA_TEXT}
-```
-
----
-
-### 🔼 **Output Rules**
-
-* Use **Markdown only**
-* Produce **ONE (1) User Story only**
-* Must be written from **end-user perspective**
-* Title must be **clear and non-technical**
-* Story must be **independently deliverable and testable**
-* Rewrite unclear or fragmented input into a **clean and business-focused requirement**
-* If information is missing, mark it **TBD** (do NOT assume)
-
----
-
-### 🧱 **Story Structure**
-
-```
-## 🧾 Story: {Story Title}
-
-### 🧑 As a {USER ROLE},
-I want to {USER INTENT}
-so that I can {BUSINESS VALUE}
-
-### 🔨 Acceptance Criteria (BDD Format)
-- **Given** {context}
-- **When** {action}
-- **Then** {expected result}
-
-(Add 4–8 acceptance criteria)
-
-### 📌 Expected Result
-- Bullet points describing what success looks like
-
-### 🚫 Non-Goals (if applicable)
-- Bullet points of what is explicitly NOT included
-
-### 🗒️ Notes (optional)
-- Clarifications / constraints / dependencies / edge cases
-```
-
----
-
-### ⚠️ Validation Rules Before Generating
-
-The story must:
-
-* Focus on **one user outcome only**
-* Avoid **technical solutioning** (no APIs, tables, database fields, component names)
-* Avoid **phrases like "fix bug", "backend update", "add field X"**
-* Convert QA language into **business language**
-
----
-
-### 🏁 Final Output
-
-Return **ONLY the completed story in Markdown**, nothing else.