phase-audit

Audit all slices in a completed project phase against specifications.

6|Updated May 29, 2026
One-click install
npx skills add https://github.com/fusebase-dev/fusebase-flow --skill phase-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-audit
Source: https://github.com/fusebase-dev/fusebase-flow/tree/main/flow-skills/phase-audit
Command: npx skills add https://github.com/fusebase-dev/fusebase-flow --skill phase-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When teams implement multi-slice project phases, in-session per-slice reviews often miss cross-slice drift, contradictions, and gaps that only become apparent after sign-off, leading to costly rework and delayed timelines.

Core Features & Use Cases

  • Independent per-slice audit: Spawns an unbiased sub-agent to review every slice against project specifications and decisions, citing file:line evidence for gaps, scope creep, and missing tests.
  • Cross-slice consistency checks: Identifies contradictions, duplicated logic, and seams between slices to ensure the full phase works as a cohesive whole.
  • Consolidated reporting: Compiles findings into a clear report split into blockers (must fix before sign-off) and non-blockers, with escalation paths for cross-cutting design issues. Use case: For example, after implementing a 4-slice payment processing phase, run this audit to catch mismatched data shapes across slices and missing acceptance criteria coverage before marking the phase complete.

Quick Start

Use the phase-audit skill to review all slices of the completed <your-phase-name> phase against its specification and generate a consolidated audit report with blocker and non-blocker findings.

Frequently Asked Questions about phase-audit

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

FAQPage Schema
How do I detect cross-slice drift and spec compliance issues before phase sign-off?

Cross-slice drift and spec compliance issues are detected by running an independent phase audit that reviews all completed slices against project specifications, identifying gaps and inconsistencies with file:line evidence before sign-off.

What is a phase audit and how does it find inconsistencies missed by in-session reviews?

A phase audit is an independent review of all slices in a completed project phase that uses unbiased sub-agents to catch cross-slice contradictions, duplicated logic, and missing acceptance criteria that in-session reviews often miss.

How do I audit all phase slices for code consistency and scope creep?

You audit phase slices by spawning unbiased sub-agents to review every slice against specifications and decisions, checking for scope creep, missing tests, and cross-slice consistency, then compiling findings into blocker and non-blocker categories.

Can I use a phase audit for multi-slice software development workflows requiring formal sign-off?

Yes, phase audit is designed for software development workflows using phased implementation with discrete slices, providing evidence-based audit verdicts with clear blocker classification to ensure alignment with north star goals before formal sign-off.

What's the best way to generate a consolidated audit report with blocker and non-blocker findings?

The best way to generate a consolidated audit report is to run an independent phase audit that compiles cross-slice findings into clear blocker and non-blocker classifications, with escalation paths for cross-cutting design issues.

When should I not rely on in-session per-slice reviews for phase completion?

In-session per-slice reviews should not be solely relied upon for phase completion when multiple slices contain complex cross-slice dependencies, as they often miss contradictions and drift that only become apparent after sign-off.