Define investigation topics and initial context for bug workflows.
npx skills add https://github.com/leeovery/tick --skill start-investigation
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
Start an organized bug investigation workflow that captures topic, context, and routing for investigations.
Provide a topic and initial context to start the investigation, and let the system guide subsequent steps.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
csuzngjhCollect system logs and configuration details into structured bug reports.
maksutovicTriage bugs and guide teams through diagnosis, discussion, and specification before implementation.
zerAdaTrack tasks, decisions, and session handoff state in Obsidian vaults.
jupesFacilitates conversational bug reporting and creates durable Beads issues.
