skills.rest
leeovery
leeoveryCOMMUNITY
Explore all skills by this author →
𝕏@leeoveryGitHub

workflow-investigation-entry

Coordinate bug investigations with a stepwise intake protocol and structured handoffs.

27|1|Updated Nov 23, 2025
Search Tags:#workflow#investigation#handoff#process#instructions#bug
One-click install
npx skills add https://github.com/leeovery/agentic-workflows --skill workflow-investigation-entry
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow-investigation-entry
Source: https://github.com/leeovery/agentic-workflows/tree/main/skills/workflow-investigation-entry
Command: npx skills add https://github.com/leeovery/agentic-workflows --skill workflow-investigation-entry

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Achieve consistent intake for bug investigations by enforcing a strict, stepwise process, preventing premature actions and ensuring all necessary context is captured.

Core Features & Use Cases

  • Enforces Step 1-4 discipline for bug investigations, including context gathering, validation, and handoffs.
  • Maintains a STOP-and-wait flow, ensuring no processing occurs until required triggers are met.
  • Provides standardized handoffs to the next skill (workflow-investigation-process) with clearly defined outputs.

Quick Start

Initialize a new investigation by providing the work unit and topic, then let the skill enforce each step exactly as written.

Frequently Asked Questions about workflow-investigation-entry

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

FAQPage Schema
How do I coordinate a bug investigation process with strict stepwise intake?▼

To coordinate a bug investigation, you initialize the workflow by providing a work unit and topic, then follow the enforced 1-4 step protocol for context gathering, validation, and structured handoff to the next process skill.

Why does the bug investigation workflow stop and wait before processing?▼

The workflow stops and waits to prevent premature actions, ensuring all required inputs and manifest-derived status checks are fully validated before the investigation proceeds to the next phase.

What inputs are required to start a Phase 1 bug investigation?▼

A Phase 1 bug investigation requires a work unit and a topic as mandatory inputs. Without these, the stepwise protocol will not proceed, ensuring consistent intake and complete context capture.

How do I hand off a completed bug investigation to the next workflow?▼

Handing off a completed bug investigation is handled by the skill itself, which generates structured handoff instructions with clearly defined outputs to seamlessly transfer context to the next workflow skill.

Can I skip validation steps if I already know the root cause of the bug?▼

No, you cannot skip steps because the skill enforces strict Step 1-4 discipline for bug investigations. This stepwise protocol ensures consistent intake and prevents premature actions even if the root cause seems known.

Related Skills

Explore More Software Engineering Skills→
leeoveryleeovery
2

start-investigation

Define investigation topics and initial context for bug workflows.

Community
Intermediate
alffeialffei
69

systematic-debugging

Diagnose software bugs through a four-phase root cause investigation process.

Community
Advanced
xg-gh-25xg-gh-25
36

health-check

Execute deterministic health checks on SwarmAI subsystems and summarize pass/fail results for CI workflows.

Community
Advanced
ViindooViindoo
7

odoo-qa-suite

Automate QA test plans, deployment checklists, and bug severity classification for Odoo modules.

Official
Advanced