Identify ambiguities in specs or plans and produce an auditable report.
npx skills add https://github.com/fall-out-bug/sdp_lab --skill spec-interrogate
Please help me install this Agent Skill. Skill: spec-interrogate Source: https://github.com/fall-out-bug/sdp_lab/tree/main/.agents/skills/spec-interrogate Command: npx skills add https://github.com/fall-out-bug/sdp_lab --skill spec-interrogate
Interrogate a spec or plan to surface ambiguities before planning or implementation.
Provide a fresh, context-stripped interrogation of a document to reveal gaps and questions.
High-intent search queries and answers about installing and using this skill.
To find ambiguities in a design doc, you interrogate the spec to expose undefined terms, missing error paths, and scope leaks. This process yields an auditable report and an evidence file documenting questions and next actions.
Spec interrogation is the process of questioning a plan to surface gaps before execution. You need it for non-trivial discovery outputs, risky architectures, or API designs to prevent implementation errors.
Yes, you can apply spec interrogation to review API designs and architecture decisions. It provides a fresh, context-stripped analysis to reveal hidden questions and scope leaks.
You start interrogating a spec by providing a fresh, context-stripped document for analysis. The tool identifies missing error paths and outputs an evidence file for traceability.
The best way to audit ambiguities in a project plan is to interrogate the document to identify undefined terms and scope leaks. This generates an auditable report and an evidence file for traceability.
yknothingPlan high-level architecture and component boundaries from reviewed requirements.
rkumar261Analyze architectural plans to identify risks and produce actionable next steps.
xloxn69Generate Architecture Decision Records with context, decision, and consequences.
ryan-mahoneyIdentify gaps between analysis and implementation specs and patch the implementation.
