pre-build-interrogator

Interrogate features and screens to generate spike documents with affordance tables.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/cmbays/mokumo --skill pre-build-interrogator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-build-interrogator
Source: https://github.com/cmbays/mokumo/tree/main/.claude/skills/pre-build-interrogator
Command: npx skills add https://github.com/cmbays/mokumo --skill pre-build-interrogator

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill ruthlessly interrogates features before development, surfacing assumptions, edge cases, and ambiguities to produce a comprehensive spike document.

Core Features & Use Cases

  • Exhaustive Questioning: Asks detailed questions across user journey, data, interactions, edge cases, cross-links, and visual design.
  • Affordance Decomposition: Creates a table mapping UI elements to their technical mechanisms and wiring.
  • Spike Document Generation: Produces a detailed spike document outlining findings and recommendations.
  • Use Case: Before building a complex new screen in your application, use this skill to ensure all potential issues and requirements are identified and documented, preventing costly rework later.

Quick Start

Use the pre-build-interrogator skill to interrogate the new user profile screen.

Frequently Asked Questions about pre-build-interrogator

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

FAQPage Schema
How do I identify edge cases and ambiguities before building a new application screen?

To identify edge cases before development, you can interrogate features by asking exhaustive questions across user journeys, data, interactions, and visual design. This process surfaces hidden assumptions and produces a spike document detailing the findings.

Can I generate a spike document for requirements gathering without manually writing all the questions?

Yes, automated pre-build interrogation generates a spike document by systematically questioning features across user journeys, data, interactions, and edge cases. This replaces manual question writing with an exhaustive, structured analysis of potential issues.

What is an affordance table and how does it help with pre-build analysis?

An affordance table maps UI elements to their technical mechanisms and wiring. It is generated during pre-build interrogation to decompose visual design into technical requirements, ensuring all interactions are documented before development begins.

What context do I need to provide for a thorough feature interrogation?

Comprehensive feature interrogation requires context from engineering architecture, acceptance criteria, data models, and progress reports. Providing this background ensures the analysis accurately identifies ambiguities and edge cases across the application.

When should I use pre-build interrogation instead of just starting development?

Use pre-build interrogation before building complex new screens to prevent costly rework. It ruthlessly examines features to identify assumptions and edge cases early, ensuring all potential issues and requirements are documented prior to writing code.