workflow-log-bug
This skill captures a bug report and writes it to the inbox.
If there's already conversation context about something broken, synthesise it straight into the file without asking questions. If this is a cold start, ask what's broken and have a natural back-and-forth to draw out the symptoms. Recognise when it has enough detail (typically 2-4 exchanges) and wrap up.
Capture only — these are rules, not guidelines:
- Do not read code or explore the codebase
- Do not search the web or fetch external resources
- Do not attempt to reproduce or validate the bug
- Do not suggest fixes or workarounds
- Do not diagnose root causes or theorise about what's wrong
- Do not propose solutions or next steps
When ready, generate a short kebab-case slug from the core symptom (e.g., stale-cache-on-deploy, login-timeout) and write the file:
mkdir -p .workflows/.inbox/bugs
More from leeovery/claude-technical-workflows
create-output-format
Scaffold a new planning output format adapter. Creates a format directory with all required files implementing the output format contract.
34update-workflow-explorer
Audit and update workflow-explorer.html flowcharts to match the current codebase logic. Reads all command, skill, and agent source files, compares against the 4 data structures in the HTML file, reports drift, and applies updates. Use when workflow logic has changed and the explorer needs syncing.
33start-research
Start a research exploration using the technical-research skill. For early-stage ideas, feasibility checks, and broad exploration before formal discussion.
11start-feature
Start a new feature through the full pipeline. Gathers context via structured interview, creates a discussion, then bridges to continue-feature for specification, planning, and implementation.
11technical-research
Explore ideas, validate concepts, and research broadly across technical, business, and market domains. Use when: (1) User has a new idea to explore, (2) Need to research a topic deeply, (3) Validating feasibility - technical, business, or market, (4) Learning and exploration without necessarily building anything, (5) User says 'research this' or 'explore this idea', (6) Brain dumping early thoughts before formal discussion. Creates research documents in .workflows/research/ that may feed into discussion or specification.
11status
Show workflow status - what exists, where you are, and what to do next.
10