module-conformance-loop

Audits SaaS modules across nine dimensions and synchronizes design documents with requirements.

10|3|Updated Mar 7, 2026
One-click install
npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill module-conformance-loop-cynthia1070711
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: module-conformance-loop
Source: https://github.com/Cynthia1070711/PHYCOOL_Tools/tree/main/config-templates/claude/skills/module-conformance-loop
Command: npx skills add https://github.com/Cynthia1070711/PHYCOOL_Tools --skill module-conformance-loop-cynthia1070711

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? During brownfield SaaS development, design documents (PRD, SDD, ADR, IDD, Skills) drift away from production code and actual requirements, causing implementation agents to build against stale or buggy specifications. This Skill enforces a disciplined, module-by-module conformance loop that realigns all specification documents with correct requirements before development handoff. ## Core Features & Use Cases - Nine-Dimension Audit: Compares production code, Skills, PRD, IDD, SDD/UIUX specs, Memory/Story DB, DB schema, OOP decoupling, and cross-document SSoT consistency, classifying findings as drift, missing, incomplete, lost, or new feature. - User-Gated Review Loop: Generates HTML review reports via ui-ux-pro-max and iterates until the user explicitly approves, with major findings (architecture changes, new features, breaking changes) requiring user adjudication. - Nine-Document Delegation Matrix: Routes each document correction through its designated skill or workflow (create-prd, sdd-spec-generator, phycool-intentional-decisions, testarch-atdd), then hands off corrected Stories to BMAD Phase 4 dev-story and code-review. - Use Case: A team mid-development on a 10-module editor platform discovers specs have drifted from code; the Skill walks each module through inventory gating, baseline audit, user review, document sync, and Story enrichment before development resumes. ## Quick Start Ask the agent to start a module conformance audit for a specific module, beginning with the exhaustive sub-feature inventory gate before any diffing.

Frequently Asked Questions about module-conformance-loop

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

FAQPage Schema
How do I audit a SaaS module for specification drift mid-development?

Run the conformance loop per module: freeze a baseline commit, exhaustively inventory sub-features from five sources with user confirmation, then diff nine dimensions (code, Skills, PRD, IDD, SDD, Memory, DB schema, OOP, SSoT) and classify each finding as drift, missing, incomplete, lost, or new feature.

What is the difference between module-conformance-loop and BMAD correct-course?

Module-conformance-loop systematically corrects all nine document dimensions module-by-module across an entire brownfield project, while BMAD correct-course handles a single change impact during a sprint. Major findings like new features can be delegated to correct-course for a sprint change proposal.

Can I use subagents to parallelize the module audit steps?

No. Steps 0-4 must run inline in the main window because delegation across subagent boundaries loses context and causes information gaps, and subagents cannot invoke gating Skills past guard hooks. Only Step 5 development handoff may use a separate pipeline window.

When should I not use the module conformance loop?

Skip it for single ad-hoc bug fixes (use quick-dev or dev-story), epic-level refactoring (use architecture review plus create-epics-and-stories), and pure UI polish (use ui-ux-pro-max directly). It targets systematic multi-module document realignment, not isolated fixes.

Why does the audit treat production code as a baseline but not as truth?

The baseline freeze is a time dimension only, preventing mid-correction code changes from invalidating the audit. The truth anchor is the correct requirement: if code contains bugs or anti-patterns, documents record the correct requirement and log a drift finding for Phase D fixing, never codifying the bug as design.