generate-vf-prompt

Generate structured verification prompts with falsifiable assertions from plans, design docs, or code diffs.

1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/n0rvyn/indie-toolkit --skill generate-vf-prompt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generate-vf-prompt
Source: https://github.com/n0rvyn/indie-toolkit/tree/main/dev-workflow/skills/generate-vf-prompt
Command: npx skills add https://github.com/n0rvyn/indie-toolkit --skill generate-vf-prompt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps generate structured verification prompts to challenge plans, design documents, or code changes, enabling rigorous backward reasoning and validation without performing execution.

Core Features & Use Cases

  • Generate VF/DF prompts from a target plan, design doc, or code diff.
  • Produce 3-5 falsifiable assertions per selected strategy, all anchored to exact file paths and line numbers.
  • Output a single, paste-ready prompt that guides reviewers through verification steps across architectures, UI changes, and behavioral updates.

Quick Start

Paste the target plan, design doc, or diff and request a VF prompt to begin.

Frequently Asked Questions about generate-vf-prompt

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

FAQPage Schema
How do I generate falsifiable assertions for code review from a design document?

You can generate verification prompts by pasting a plan, design doc, or code diff; the skill analyzes the content to auto-select applicable verification strategies and produces falsifiable assertions with exact file:line citations.

What is a verification prompt and how does it validate design faithfulness?

A verification prompt validates design faithfulness by providing structured, falsifiable assertions that challenge a plan or code diff, enabling rigorous backward reasoning and validation without executing the code.

Can I use this to generate verification strategies for a code diff?

Yes, you can use this to generate verification strategies for a code diff by pasting the diff, which triggers automatic strategy selection and outputs a single paste-ready prompt grouping all assertions.

What's the best way to structure plan analysis for backward reasoning validation?

The best way to structure plan analysis for backward reasoning is to generate a single copy-paste prompt that groups assertions across architectures, UI changes, and behavioral updates, guiding reviewers through verification steps.

How many falsifiable assertions are produced per selected verification strategy?

The skill produces 3-5 falsifiable assertions per selected verification strategy, ensuring each assertion is anchored to exact file paths and line numbers for rigorous validation.

Does the generated verification prompt require execution to validate the plan?

No, the generated verification prompt does not require execution; it enables rigorous backward reasoning and validation by challenging plans, design documents, or code changes purely through structured assertions.