phase-gate1

Generates investigation summaries and manages the human approval gate before report drafting.

43|8|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/buriedsignals/spotlight --skill phase-gate1-buriedsignals
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-gate1
Source: https://github.com/buriedsignals/spotlight/tree/main/skills/phase-gate1
Command: npx skills add https://github.com/buriedsignals/spotlight --skill phase-gate1-buriedsignals

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? OSINT investigations need a formal checkpoint where findings are summarized, presented to a human, and explicitly approved before any report drafting or knowledge ingestion occurs. This Skill automates that Gate 1 review step in the Spotlight investigation pipeline. ## Core Features & Use Cases - Summary Generation: Writes both a human-readable summary.md and a machine-readable data/summary.json contract capturing findings, confidence levels, verdicts, and limitations. - Human Approval Gate: Presents findings, methods, and confidence assessments to the user, persists an attributable approval receipt, and ends the turn until resumed. - Provenance & Review Finalization: Builds a provenance manifest with artifact hashes, optionally signs it via a C2PA endpoint, and produces a self-contained review.html artifact for inspecting findings. - Use Case: After three research cycles on an investigation, invoke this Skill to compile verified findings into a summary, obtain the journalist's sign-off, and seal the gate before report generation. ## Quick Start Ask the orchestrator to run Gate 1 for the current case directory so it generates the summary artifacts and presents the findings for your approval.

Frequently Asked Questions about phase-gate1

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

FAQPage Schema
How do I approve an OSINT investigation before report drafting?

Run the Gate 1 phase, which generates summary.md and data/summary.json from execution outputs, then presents findings, methods, and limitations for review. Your explicit approval is persisted as an attributable receipt via spotlight_transition before any downstream work.

What artifacts does the Gate 1 summary step generate?

It writes two artifacts: summary.md, a human-readable markdown overview with findings tables and limitations, and data/summary.json, a machine-readable contract with schema_version, findings, confidence levels, and fact-check verdicts used by review, report, and ingest stages.

Can I request a follow-up research cycle instead of approving?

Yes. Instead of approving, request a follow-up and the Skill persists a requestFollowUp transition with your targeted gap instructions, then returns control to the execution owner for another bounded research cycle.

Does provenance signing failure block the review process?

No. If the optional C2PA signing endpoint fails, the unsigned provenance manifest is preserved and the failure is reported clearly. The workflow continues to the review step without blocking.

What happens if a dependency changes after Gate 1 approval?

The approval is bound to a dependency digest owned by the provenance builder. If a dependency changes, the next resolution returns to Gate 1 approval, requiring validators to re-run and a new human approval before report or ingestion.