external-plan-audit

Audits external documents against the ValueOS codebase to validate sprint claims.

Updated Nov 17, 2025
One-click install
npx skills add https://github.com/Valynt/ValueOS --skill external-plan-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: external-plan-audit
Source: https://github.com/Valynt/ValueOS/tree/main/.windsurf/skills/external-plan-audit
Command: npx skills add https://github.com/Valynt/ValueOS --skill external-plan-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

External plans and assessments often promise sprint work that may not align with the actual codebase, risking wasted velocity and misprioritized tasks. This skill provides a rigorous, defensible audit workflow that compares claims against the ValueOS repository to determine what is already satisfied, what is partially valid, and what remains open.

Core Features & Use Cases

  • Two-part outputs: a claim-by-claim accuracy table and a corrected sprint plan.
  • Stepwise verification against the codebase, traceability, and ADRs to ensure alignment with established architecture and governance.
  • Use case: an external consultant provides a sprint plan with task IDs; apply the audit to confirm which items require work and how to schedule them.

Quick Start

Paste or attach the external plan document and trigger the audit to receive an accuracy table and a corrected sprint plan.

Frequently Asked Questions about external-plan-audit

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

FAQPage Schema
How do I audit an external sprint plan against my codebase?

Auditing external consultant reports involves stepwise verification against your codebase, traceability, and ADRs to determine which proposed sprint tasks are already satisfied, partially valid, or remain open.

How do I verify consultant sprint claims against actual codebase architecture?

Auditing external consultant reports involves stepwise verification against your codebase, traceability, and ADRs to determine which proposed sprint tasks are already satisfied, partially valid, or remain open.

What is a codebase audit for external sprint planning?

An external plan audit outputs a claim-by-claim accuracy table detailing what is already satisfied, partially valid, or open, alongside a corrected sprint plan to guide task prioritization.

What outputs do I get from validating an external plan against a repository?

An external plan audit outputs a claim-by-claim accuracy table detailing what is already satisfied, partially valid, or open, alongside a corrected sprint plan to guide task prioritization.

Can I use sprint plan audits for AI-generated codebase gap reports?

Yes, sprint plan audits apply to AI audits, external reviewers, or any document proposing sprint tasks to validate claims against your codebase before scheduling work.

When should I not rely on external sprint plans for codebase tasks?

You should audit external plans when they promise sprint work that may not align with the actual codebase, risking wasted velocity and misprioritized tasks due to unverified claims.