audit

Audit sprint artefacts for methodology drift and generate structured reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/tjisousa/gensem --skill audit-tjisousa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: audit
Source: https://github.com/tjisousa/gensem/tree/main/gse-one/plugin/skills/audit
Command: npx skills add https://github.com/tjisousa/gensem --skill audit-tjisousa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit the project for methodology drift by detecting format inconsistencies, missing evidence, and skipped steps across sprint artefacts. It highlights deviations from the canonical workflow and surfaces drift signals that could impact delivery quality and traceability.

Core Features & Use Cases

  • Detects format irregularities, missing evidence, and out-of-sequence steps across docs, plans, and backlog items.
  • Generates a structured audit report that summarizes findings by severity and category, and proposes corrective actions.
  • Supports manual invocations (/gse:audit) as well as automatic triggering by the orchestrator when drift signals accumulate in Phase 3, enabling proactive governance.

Quick Start

Run the /gse:audit command to start a deterministic methodology audit against the current sprint artefacts and state.

Frequently Asked Questions about audit

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

FAQPage Schema
How do I detect methodology drift in my active sprint?

Detect methodology drift by running a deterministic audit against sprint artefacts to identify format inconsistencies, missing evidence, and skipped steps. It analyzes state files and generates a structured report with corrective guidance stored under .gse/audits.

What is project methodology drift and when should I audit for it?

Project methodology drift occurs when sprint artefacts deviate from the canonical workflow through format irregularities or skipped steps. You should audit when drift signals accumulate during Phase 3, or manually trigger an audit to proactively govern delivery quality and traceability.

How do I generate an audit report for missing evidence and format inconsistencies?

Generate an audit report by invoking the audit engine against current sprint artefacts and state files. The report summarizes findings by severity and category, highlighting out-of-sequence steps and proposing corrective actions to restore methodology compliance.

Can I automate methodology audits instead of triggering them manually?

Yes, audits can be auto-triggered by the orchestrator when drift signals accumulate in Phase 3, enabling proactive governance. You can also manually invoke the audit command anytime to perform a deterministic check against active sprint artefacts.

Does the audit engine work without external dependencies?

The audit engine relies on the local GSE-One registry and access to sprint artefacts and state files to function. It requires no external dependencies, operating deterministically to produce formal findings and store them under .gse/audits.

What corrective actions does a methodology audit report provide?

The audit report proposes corrective actions for format inconsistencies, missing evidence, and out-of-sequence steps detected across docs, plans, and backlog items. Findings are categorized by severity to help prioritize remediation and restore canonical workflow compliance.