savepoint-audit

Review completed technical epics against acceptance criteria and capture drift.

1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/anipatke/savepoint --skill savepoint-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: savepoint-audit
Source: https://github.com/anipatke/savepoint/tree/main/agent-skills/savepoint-audit
Command: npx skills add https://github.com/anipatke/savepoint --skill savepoint-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the review process for completed user epics by verifying that implementation aligns with acceptance criteria and documentation, reducing manual audit effort.

Core Features & Use Cases

  • Epic Review: Assess the consistency of code and documentation against specified acceptance criteria.
  • Drift Identification: Capture deviations and undocumented changes during audits.
  • Handoff Preparation: Generate structured audit reports for stakeholder review and handoff.
  • Use Case: For teams deploying iterative features, perform regular audits to ensure quality before release, relying on this Skill to document findings comprehensively.

Quick Start

Use the savepoint-audit skill to review a completed epic by providing the relevant epic details and review context as specified in the workflow instructions.

Frequently Asked Questions about savepoint-audit

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

FAQPage Schema
How do I audit completed epics against acceptance criteria?

Auditing completed epics against acceptance criteria involves systematically verifying code quality, style, and implementation consistency to capture drift and undocumented changes. This approach ensures technical implementation aligns with documented requirements before release.

What is epic verification and when do I need it?

Epic verification is the post-implementation review process validating that deployed features match acceptance criteria and documentation. You need it during iterative feature releases to identify drift and ensure compliance before stakeholder handoff.

How do I identify code drift during a post-implementation review?

Identifying code drift during a post-implementation review requires comparing completed technical epics against their original acceptance criteria and documentation. This systematic audit captures deviations and undocumented changes that occurred during the development cycle.

Can I generate structured audit reports for stakeholder handoff?

Generating structured audit reports for stakeholder handoff is a core outcome of verifying completed epics. The process captures consistency issues, drift findings, and compliance documentation into comprehensive reports designed for stakeholder communication.

What's the best way to ensure implementation accuracy before release?

Ensuring implementation accuracy before release is best achieved through systematic post-implementation audits that verify code quality and style compliance. This comprehensive process assesses consistency against specified acceptance criteria and documents findings for stakeholders.

Does this epic review process require specific dependencies or environments?

This epic review process requires no external dependencies, operating independently to facilitate thorough technical audits. You provide the relevant epic details and review context to validate implementation accuracy and capture drift.