module-completeness-audit

Blocks review-to-done transitions when module governance checklist items are missing.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill module-completeness-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: module-completeness-audit
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/module-completeness-audit
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill module-completeness-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents teams from marking a user story as done when the target module misses internal governance requirements, reducing costly production surprises and governance drift.

Core Features & Use Cases

  • Hard gate on review→done: blocks the transition to done unless the module passes an objective 8-item governance checklist.
  • On-demand module audit: runs a full-module audit when a user asks if a module is ready to close or explicitly requests a governance audit.
  • Actionable results for decision-making: summarizes approvals/rejections with evidence and recommends concrete next steps, including the option to create new US for detected gaps.

Quick Start

Run the command "/module-completeness-audit Modules/NomeDoModulo" to get an evidence-based pass/fail governance result before you close the related user story.

Frequently Asked Questions about module-completeness-audit

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

FAQPage Schema
How do I block a user story from moving to done when Laravel module governance is incomplete?▼

To block the review to done transition for incomplete Laravel modules, you need a quality gate that validates governance against an 8-dimensional checklist. This skill enforces that refusal automatically when any checklist item is missing.

What is module governance auditing and when should I run it?▼

Module governance auditing is the process of verifying repository code and memory artifacts against an 8-item checklist. You should run it on-demand when asking if a module is ready to close or automatically during the review to done task transition.

How do I audit a specific Laravel module for multi-tenant safety and Pest coverage?▼

Run the command /module-completeness-audit Modules/NomeDoModulo to execute the 8-dimensional checklist. It analyzes repository code and spec artifacts to produce an evidence-based pass or fail governance result.

Does the module governance audit provide actionable next steps when a check fails?▼

Yes, the module governance audit summarizes rejections with evidence and recommends concrete next steps. It includes the option to create new user stories specifically to address the detected governance gaps.

Can I use this quality gate for on-demand module audits without transitioning a task status?▼

Yes, you can trigger a full module audit on-demand by explicitly requesting a governance audit. The skill evaluates the 8-dimensional checklist and records the audit outcomes regardless of the current task status.

What happens if internal governance checks fail during the review to done transition?▼

If internal governance checks fail during the review to done transition, the quality gate enforces a refusal to transition. It blocks the status update and requires all 8 checklist dimensions to pass before completion is allowed.