Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion skills/agent-browser/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: agent-browser
description: Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
description: "Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when navigating websites, interacting with web pages, filling forms, taking screenshots, testing web applications, or extracting information from web pages."
---

# Browser Automation with agent-browser
Expand Down
69 changes: 5 additions & 64 deletions skills/bugs-to-stories/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
name: bugs-to-stories
description: "Convert bug reports into prd.json user stories for autonomous fixing. Use after running test-and-break skill. Triggers on: convert bugs to stories, fix these bugs, add bugs to prd, create fix stories."
description: "Parses bug reports from test-and-break, extracts reproduction steps, generates acceptance criteria, and creates structured prd.json user stories for autonomous fixing. Use when converting bug reports to user stories, triaging bugs into a backlog, adding bugs to a PRD, or preparing bug-fix stories for Ralph."
---

# Bugs to Stories Converter
Expand All @@ -20,7 +20,7 @@ Takes bug reports from the test-and-break skill and converts them into properly

## Conversion Rules

### Bug β†’ User Story Mapping
### Bug to User Story Mapping

| Bug Field | Story Field |
|-----------|-------------|
Expand Down Expand Up @@ -102,10 +102,9 @@ Ask user which approach if unclear.

### Step 4: Generate Stories

For each bug in the report:
For each bug in the report, apply the mapping tables above to produce a story. Example conversion for one bug:

```javascript
// Example conversion
const bugToStory = (bug, priorityOffset) => ({
id: bug.id.replace('BUG', 'FIX'),
title: `Fix: ${bug.title}`,
Expand Down Expand Up @@ -137,9 +136,7 @@ cp prd.json prd.json.backup
"project": "[Original Project] - Bug Fixes",
"branchName": "ralph/bugfix-2024-01-15",
"description": "Bug fixes from automated testing",
"userStories": [
// converted bug stories here
]
"userStories": []
}
```

Expand All @@ -157,62 +154,6 @@ cat prd.json | jq '{

---

## Example Conversion

**Input Bug:**
```markdown
## BUG-003: Form submits with empty required fields

**Severity:** High
**Type:** Functional

**Steps to Reproduce:**
1. Go to /signup
2. Leave all fields empty
3. Click "Create Account"

**Expected Behavior:**
Form should show validation errors and prevent submission

**Actual Behavior:**
Form submits and shows server error
```

**Output Story:**
```json
{
"id": "FIX-003",
"title": "Fix: Form submits with empty required fields",
"description": "As a user, I expect the signup form to show validation errors when I leave required fields empty, but currently it submits and shows a server error.",
"acceptanceCriteria": [
"Add client-side validation for all required fields",
"Show inline error messages for empty required fields",
"Disable submit button until required fields are filled",
"Regression test: Going to /signup β†’ leaving fields empty β†’ clicking Create Account shows validation errors instead of submitting",
"Typecheck passes"
],
"priority": 4,
"passes": false,
"notes": "Original bug steps: Go to /signup; Leave all fields empty; Click Create Account"
}
```

---

## After Conversion

Once bugs are converted to stories:

1. Tell the user how many bug fix stories were added
2. Show the priority distribution
3. Ask if they want to start Ralph to fix them:

> "I've added X bug fix stories to prd.json:
> - Critical fixes: X (priority 1-3)
> - High priority: X (priority 4-7)
> - Medium priority: X (priority 8-12)
> - Low priority: X (priority 13+)
>
> Ready to run Ralph to fix these bugs automatically?"

If yes, they can run `./ralph.sh` to start fixing.
Once bugs are converted to stories, report the count of added stories and the priority distribution to the user. They can then run `./ralph.sh` to start autonomous fixing.
Loading