interrogate

Clarify project goals, scope, audience, risks, and dependencies for new projects.

6|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/thensls/nsls-builder-toolkit --skill interrogate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: interrogate
Source: https://github.com/thensls/nsls-builder-toolkit/tree/main/skills/interrogate
Command: npx skills add https://github.com/thensls/nsls-builder-toolkit --skill interrogate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps builders and product owners turn vague ideas into a shared, actionable understanding by relentlessly surfacing goals, scope, audience, stakeholders, dependencies, risks, and measurable success criteria so work starts with clarity and avoids scope creep.

Core Features & Use Cases

  • Structured Discovery: Guides the user through a decision tree of focused questions covering goals, scope/stage, audience segments, stakeholders, dependencies, risks, and metrics.
  • Artifact Generation: Produces an Obsidian project home note, generates a DESIGN.md for automations with user-facing interactions, and prepares a mapped registration for the Automation Tracker.
  • Collaboration & Handoff: Useful when starting a new project or automation, documenting an undocumented build, preparing a design handoff, or registering work in the tracker for visibility and maintenance.

Quick Start

Say 'interrogate' and describe your idea in one sentence to begin a guided scoping session that outputs a project summary, optional DESIGN.md, and automation tracker registration.

Frequently Asked Questions about interrogate

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

FAQPage Schema
How do I define project scope and identify risks for a new automation?

To clarify project goals and scope for an undocumented build, walk through a structured decision tree covering audience segments, stakeholders, dependencies, and metrics. This guides you to produce a design document and a project home note for shared visibility.

What is the best way to document an undocumented automation build for handoff?

The best way to document an undocumented automation build for handoff is to generate a DESIGN.md for user-facing interactions and map fields for an automation tracker. This creates shared, actionable understanding and registers work for maintenance visibility.

Does this project scoping process work with Obsidian for generating design docs?

Yes, this project scoping process integrates with Obsidian by outputting a project home note directly into your vault. It also generates a DESIGN.md for user-facing interactions and prepares mapped fields for an Automation Tracker.

Can I use this guided discovery to register work in an Automation Tracker?

Yes, you can use guided discovery to register work in an Automation Tracker by mapping clarified project fields, dependencies, and risks. It prepares a mapped registration output during the scoping session to ensure visibility and maintenance.

When should I not use a structured discovery session for project scoping?

You should not use a structured discovery session for project scoping if your build lacks user-facing interactions, requires no stakeholder alignment, or already has comprehensive design artifacts and tracker registration mapped out.