docfactory-audit

Audit DocFactory pipeline artifacts for inconsistencies and generate patches.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/burakdirin/skills --skill docfactory-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docfactory-audit
Source: https://github.com/burakdirin/skills/tree/main/skills/docfactory-audit
Command: npx skills add https://github.com/burakdirin/skills --skill docfactory-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Inconsistent DocFactory artifacts can drift from one another across project briefs, decisions, PRDs, UI/UX specs, architecture notes, and backlog entries, leading to misaligned development. This Skill identifies these inconsistencies and proposes precise patches to restore coherence and alignment before coding begins.

Core Features & Use Cases

  • Cross-document consistency checks across the DocFactory pipeline (00-project-brief, 00-decisions, 00-glossary, 02-prd, 03-ui-ux-spec, 04-tech-architecture, 06-backlog).
  • Patch generation with exact text proposals to fix drift and improve traceability.
  • Use Case: Run after backlog preparation to guarantee that all artifacts reflect the same MVP scope and design decisions.

Quick Start

Run the docfactory-audit skill after backlog is prepared to generate 09-consistency-audit.md

Frequently Asked Questions about docfactory-audit

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

FAQPage Schema
How do I audit project documentation for consistency before development starts?

You can audit project documentation by running a cross-document consistency check across your project artifacts. This identifies inconsistencies and proposes concrete patches to restore alignment before coding begins.

What is the best way to fix drift between PRDs, UI/UX specs, and backlog entries?

The best way to fix drift is to validate inputs across these artifacts, generate a structured Findings Table, and apply proposed text patches to ensure requirements and design reflect the same MVP scope.

Can I check if my architecture notes and project brief are in sync?

Yes, you can check if architecture notes and project briefs are in sync by validating them against the same pipeline. This identifies misaligned development artifacts and outputs exact text proposals to restore coherence.

How do I generate documentation patches for misaligned MVP scope?

You generate documentation patches by validating your backlog and related references against upstream artifacts. This produces a structured audit with exact text proposals to fix drift and improve traceability.

Why does my backlog preparation produce inconsistent requirements?

Backlog preparation produces inconsistent requirements when upstream artifacts like project briefs and PRDs drift. Running a consistency audit after backlog preparation validates all inputs and proposes patches to restore alignment.

When should I run a cross-document consistency audit in my pipeline?

You should run a cross-document consistency audit immediately after your backlog is prepared. This guarantees all artifacts, from project brief to backlog, reflect the same scope and decisions before development starts.