product-interviewer-revisor

Validate product-context files against interview-log.md for completeness and fidelity.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/joleques/northstar-ai --skill product-interviewer-revisor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-interviewer-revisor
Source: https://github.com/joleques/northstar-ai/tree/main/.codex/skills/product-interviewer-revisor
Command: npx skills add https://github.com/joleques/northstar-ai --skill product-interviewer-revisor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The product-interviewer-revisor acts as a Devil's Advocate, validating the context extracted by the product-interviewer to ensure it's complete, faithful, and free from invented information.

Core Features & Use Cases

  • Completeness analysis — checks that every thematic axis is covered with sufficient depth.
  • Fidelity analysis — cross-checks thematic files against the interview-log.md to detect hallucinations or mismatches.
  • Depth analysis — ensures the extracted context would support confident decision-making by an AI agent.
  • Coherence analysis — detects contradictions between files and ensures consistency of entities.
  • Report generation — produces a structured verdict and clarifying questions when gaps exist.

Quick Start

Run the revisor against /documentacao/{titulo}/contexto/ to validate completeness, fidelity, depth and coherence of the extracted product-context.

Frequently Asked Questions about product-interviewer-revisor

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

FAQPage Schema
How do I validate product context completeness and fidelity after an interview?

Product context validation detects hallucinations by cross-checking extracted thematic files against the original interview log. It verifies that no invented information was introduced and flags mismatches between the documented context and the source interview data.

How do I check for hallucinations or invented information in extracted product documentation?

Product context validation detects hallucinations by cross-checking extracted thematic files against the original interview log. It verifies that no invented information was introduced and flags mismatches between the documented context and the source interview data.

What is the best way to ensure product context depth and coherence before AI agent decision-making?

The best way to ensure context depth and coherence is to run a Devil's Advocate review on the documentation directory. This detects contradictions between files, verifies entity consistency, and ensures the depth supports confident AI decision-making.

Can I generate a structured report with follow-up questions for gaps in product context?

Yes, you can generate a structured report with follow-up questions by applying a completeness analysis to the product context directory. The report provides a final verdict and highlights specific gaps requiring further clarification.

Does the product context review process require the interview-log.md file?

Yes, the review process requires the interview-log.md file as a reference baseline. It uses this log to verify coverage and alignment across all thematic files extracted within the documentation directory.