start-investigation

Define investigation topics and initial context for bug workflows.

2|Updated Jan 19, 2026

Search Tags:#workflow #collaboration #context #investigation #routing #discovery #bugfix

Ready to run

npx skills add https://github.com/leeovery/tick --skill start-investigation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: start-investigation
Source: https://github.com/leeovery/tick/tree/main/.claude/skills/start-investigation
Command: npx skills add https://github.com/leeovery/tick --skill start-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Start an organized bug investigation workflow that captures topic, context, and routing for investigations.

Core Features & Use Cases

Structured discovery of investigations and defined topics to keep teams aligned.
Guided routing between fresh and ongoing investigations, with state-aware decisions.
Reusable templates for initial bug context and handoff to deeper specification workflows.

Quick Start

Provide a topic and initial context to start the investigation, and let the system guide subsequent steps.

Frequently Asked Questions about start-investigation

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

FAQPage Schema

How do I start a structured bug investigation and capture initial context?▼

Starting a structured bug investigation requires providing a topic and initial context to the workflow. It then applies state-aware routing to determine next steps, generating discovery output and frontmatter that captures the topic, status, and work type for team alignment.

What is the best way to route an ongoing bugfix investigation versus a fresh one?▼

The best way to route bugfix investigations is to use state-aware discovery to evaluate the current status. The workflow applies guided routing decisions to distinguish between fresh investigations needing initial context and ongoing ones requiring deeper specification handoffs.

Can I use this workflow to hand off bug context to a deeper specification process?▼

Yes, you can use this workflow to hand off bug context to deeper specification workflows. It provides reusable templates for initial context and generates discovery output with frontmatter, ensuring the topic, status, and work type are defined for downstream processes.

Do I need specific input data to define the investigation topic and frontmatter?▼

You need to provide a defined topic and initial context to define the investigation topic and frontmatter. The workflow uses these inputs to establish the discovery output, applying state-aware decisions to ensure the status and work type are accurately captured.

Why does my bug investigation workflow require discovery output and frontmatter metadata?▼

Your bug investigation workflow requires discovery output and frontmatter metadata to drive state-aware routing and team alignment. This metadata ensures the topic, status, and work type are consistently captured, guiding handoffs to deeper specification workflows.