speckit-bounded-investigation

Collect bounded evidence for blocked software issues with scoped repository search and stop conditions.

95|39|Updated Dec 15, 2025
One-click install
npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-bounded-investigation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-bounded-investigation
Source: https://github.com/liuminxin45/auto-podcast/tree/main/.agents/spec-kit/skills/speckit-bounded-investigation
Command: npx skills add https://github.com/liuminxin45/auto-podcast --skill speckit-bounded-investigation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you safely investigate a blocked issue when the root cause, source behavior, or validation evidence is missing, so you can gather the minimum facts needed before implementing a change.

Core Features & Use Cases

  • Bounded Investigation Planning: Defines a precise question, affected repository, search scope, command budget, and stop conditions before you start digging.
  • Evidence Collection: Captures source facts, blockers, unknowns, and hints in a structured investigation note for later handoff or resumption.
  • UI Runtime Troubleshooting: Guides targeted runtime checks for layout, host embedding, DOM ancestry, computed styles, box metrics, and scrollbar behavior when frontend parity issues are suspected.
  • Routing Decision Support: Recommends whether the work should proceed as a micro-fix, standard bugfix, full SDD, validation-only pass, or remain blocked.
  • Use Case: You are debugging a broken feature, but the failing condition is unclear and the current fix attempt did not help; use this Skill to collect proof and decide the safest next stage.

Quick Start

Use this skill to investigate the blocked feature, record the evidence in the required investigation file, and recommend the next stage before making another implementation change.

Frequently Asked Questions about speckit-bounded-investigation

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

FAQPage Schema
How do I collect evidence for a blocked debugging issue when the root cause is unclear?

To collect evidence for a blocked debugging issue, define a precise question, affected repository, search scope, command budget, and stop conditions. This captures source facts and unknowns in a structured note for routing decisions and next-stage handoff.

What is a bounded investigation in software debugging?

A bounded investigation in software debugging is a staged process that scopes repository searches and defines stop conditions before implementation. It captures minimum facts and validation proof needed to unblock a feature safely without excessive digging.

How do I troubleshoot UI runtime parity issues with computed styles and DOM ancestry?

To troubleshoot UI runtime parity issues, guide targeted runtime checks for layout, host embedding, DOM ancestry, computed styles, box metrics, and scrollbar behavior. This captures frontend runtime facts needed to validate suspected layout problems.

When should I stop investigating a bug and route it to a standard bugfix or full SDD?

You should stop investigating a bug and route it once bounded evidence is collected and documented. Use routing decision support to determine if the work proceeds as a micro-fix, standard bugfix, full SDD, validation-only pass, or remains blocked.

Can I document investigation notes and handoff requirements for spec-driven debugging workflows?

Yes, you can document investigation notes and handoff requirements for spec-driven debugging workflows. The process captures source facts, blockers, unknowns, and hints in a structured file to support resumption and next-stage routing decisions.