skills.rest
pnewsam
pnewsamCOMMUNITY
Explore all skills by this author →
Website𝕏@paultakumaGitHub

plan-bug-bash

Convert unstructured bug bash observations into a prioritized docs/epics bug-bash epic.

1|Updated Apr 15, 2026
Search Tags:#prioritization#epic planning#feedback processing#bug triage#issue deduplication#bug bash#docs/epics
One-click install
npx skills add https://github.com/pnewsam/skills --skill plan-bug-bash-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-bug-bash
Source: https://github.com/pnewsam/skills/tree/main/archive/plan-bug-bash
Command: npx skills add https://github.com/pnewsam/skills --skill plan-bug-bash-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Stream-of-consciousness bug reports and app feedback are messy, duplicated, and hard to act on. This Skill parses dictated or rough observations into a structured bug-bash epic under docs/epics/ with categorized, prioritized child features ready for planning. ## Core Features & Use Cases - Observation Parsing: Extracts distinct issues from conversational dictation, text files, or rough bullet lists while preserving raw context. - Deduplication and Categorization: Merges repeated complaints and tags each issue with category, severity, effort, and confidence. - Epic Generation: Groups issues into coherent child features and writes a standard docs/epics/NNN-<slug>.md epic with an issue inventory and raw notes. - Use Case: After a team clicks through an app and dictates twenty minutes of feedback, paste the transcript and receive a prioritized bug-bash epic whose child features can be planned with plan-feature or shipped with ship-epic. ## Quick Start Turn these dictated bug bash notes into a bug-bash epic under docs/epics with prioritized child features.

Frequently Asked Questions about plan-bug-bash

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

FAQPage Schema
How do I turn bug bash notes into an actionable plan?▼

Paste the raw dictated notes or bullet list and the Skill parses distinct issues, deduplicates them, categorizes by severity and effort, and writes a bug-bash epic under docs/epics/ with grouped child features ready for planning.

How are duplicate bug reports handled during triage?▼

Repeated observations describing the same underlying problem are merged into a single issue while preserving useful raw phrases. Each distinct issue is kept, even minor ones, so no feedback is silently discarded.

Does this create a separate bug tracker outside the epic workflow?▼

No. A bug bash is treated as a normal epic under docs/epics/ with child features, not a separate tracker. Execution flows through plan-feature, advance-epic, execute-feature, or ship-epic like any other epic.

What happens if docs/CHARTER.md is missing?▼

The Skill stops and recommends running create-charter before creating the epic. The bug bash must be framed as quality, reliability, or usability work aligned with the project charter.

When should I not use bug bash epic planning?▼

Avoid it when input is already a single well-defined bug or feature, which fits plan-feature directly. It is designed for batches of messy, mixed observations that need deduplication, categorization, and grouping.

Related Skills

Explore More Product & Management Skills→
ArthTech-AIArthTech-AI

engagement-charter

Generate an engagement charter defining scope, metrics, stakeholders, timeline, and governance.

Official
Advanced
WASD6570WASD6570
1

program-refining

Refine epic plans into dependency-aware child feature seeds with durable artifacts.

Community
Advanced
langadventurellclangadventurellc

issue-creation-review

Assess Trellis issues against original requirements for completeness and scope alignment.

Official
Advanced
paulinghampaulingham
1

batch-pipeline

Run multiple batch tasks in parallel with state, scratchpad, and observation tracking.

Community
Advanced