doc-confirm

Preview and confirm document generation before creating project documentation.

1|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/tygwan/ultra-codex-init --skill doc-confirm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: doc-confirm
Source: https://github.com/tygwan/ultra-codex-init/tree/main/.codex/skills/doc-confirm
Command: npx skills add https://github.com/tygwan/ultra-codex-init --skill doc-confirm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This flow prevents unintentional document generation by requiring a visible confirmation step before creating new project docs.

Core Features & Use Cases

  • Preview the documents to be generated (PRD.md, TECH-SPEC.md, PROGRESS.md, CONTEXT.md) and verify content before proceeding.
  • Choice-driven workflow with Submit to proceed, Edit to refine DISCOVERY.md, and Cancel to save discovery without generating documents.
  • Seamless integration with /init and brainstorming processes to guard the document creation stage.

Quick Start

Run /doc-confirm after the discovery is prepared to preview and confirm document generation.

Frequently Asked Questions about doc-confirm

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

FAQPage Schema
How do I preview project documentation before it is generated?

To preview project documentation before generation, you can run a confirmation flow that displays the proposed PRD.md, TECH-SPEC.md, PROGRESS.md, and CONTEXT.md files, allowing you to verify content and submit, edit, or cancel.

Can I edit discovery details before generating PRD and tech spec files?

Yes, you can edit discovery details before generating PRD and tech spec files by selecting the Edit option in the confirmation workflow, which allows you to refine your DISCOVERY.md content before proceeding with document creation.

What is the best way to prevent unintentional document generation during workflow initialization?

The best way to prevent unintentional document generation during workflow initialization is to use a deterministic confirmation step that requires explicit submission before triggering the dev-docs-writer to create your project documentation.

Does the brainstorming workflow support document preview and cancellation?

Yes, the brainstorming workflow supports document preview and cancellation by integrating a choice-driven flow where you can Submit to generate files, Edit to refine discovery, or Cancel to save findings without creating documentation.

What happens if I cancel document generation after previewing the files?

If you cancel document generation after previewing the files, the workflow saves your discovery session without triggering the dev-docs-writer to generate the PRD.md, TECH-SPEC.md, PROGRESS.md, and CONTEXT.md project documents.

Do I need a prepared discovery file to run a document confirmation workflow?

Yes, you need a prepared discovery file to run a document confirmation workflow, as the preview and validation process applies the discovery findings to draft the PRD, technical specification, progress, and context files for your review.