Add "Change V5.2.0: Plugin Enhancements Proposal"

2026-01-27 21:42:34 +00:00
parent faebbe8e92
commit a13c34ec7c

@@ -0,0 +1,133 @@
> **Type:** Change Proposal
> **Version:** V5.2.0
> **Status:** In Progress
> **Date:** 2026-01-27
> **Scope:** Multi-plugin enhancement initiative
# V5.2.0 Plugin Enhancements
This proposal covers 26 enhancement items across 10 plugins, organized into 3 implementation sprints.
## Overview
| Sprint | Focus | Items | Status |
|--------|-------|-------|--------|
| Sprint 3 | Hooks (enforcement, validation, detection) | 6 | Planning |
| Sprint 4 | Commands (new user-facing features) | 16 | Backlog |
| Sprint 5 | Documentation (guides, best practices) | 4 | Backlog |
## Implementations
- [Sprint 3: Hooks](Change-V5.2.0%3A-Plugin-Enhancements-Proposal-%28Sprint-3-Hooks%29) - Current
---
## Sprint 3: Hooks (6 items)
Foundational enforcement and detection hooks that other features may depend on.
### git-flow (2 items)
1. **Commit enforcement hook** - Validate conventional commit format on all commits (not just `/commit` command). Hook type: `PreToolUse` on Bash (git commit detection)
2. **Branch name validation hook** - Validate branch naming on creation (format: `type/description`, lowercase, max 50 chars). Hook type: `PreToolUse` on Bash (git checkout -b detection)
### clarity-assist (1 item)
3. **Auto-suggest hook** - `UserPromptSubmit` hook with vagueness detection, suggests `/clarity-assist` when needed
### data-platform (1 item)
4. **Schema diff detection** - Hook to warn on breaking schema changes. Hook type: `PostToolUse` on file edits to schema files
### contract-validator (2 items)
5. **SessionStart auto-validate hook** - Smart mode (only runs when plugin files changed since last check)
6. **Breaking change detection** - Warn when interface changes break consumers. Works with auto-validate hook.
---
## Sprint 4: Commands (16 items)
New user-facing commands and features.
### projman (1 item)
7. **Dynamic sprint diagram** - Mermaid diagram showing current sprint's issues, dependencies, and flow. Integrate with `/sprint-status` or new `/sprint-diagram` command.
### pr-review (2 items)
8. **Confidence threshold config** - Env var `PR_REVIEW_CONFIDENCE_THRESHOLD` to filter low-confidence warnings
9. **pr-diff command** - Formatted diff with annotations (review comments + inline agent analysis)
### data-platform (3 items)
10. **data-quality command** - Run quality checks on dataframes (nulls, duplicates, types, outliers)
11. **lineage-viz command** - Mermaid wrapper around `dbt_lineage` for visual output
12. **dbt-test command** - User-friendly wrapper for `dbt_test`
### viz-platform (3 items)
13. **chart-export command** - Export to PNG, SVG, PDF
14. **Color blind validation** - Theme accessibility check for color blind users
15. **Responsive breakpoint config** - Mobile-first layout configuration
### contract-validator (1 item)
16. **dependency-graph command** - Mermaid visualization of plugin dependencies
### doc-guardian (3 items)
17. **changelog-gen command** - Generate changelog from commit history
18. **Doc coverage metrics** - Measure and report documentation coverage
19. **Stale doc warnings** - Flag docs older than X commits behind related code
### claude-config-maintainer (2 items)
20. **config-diff command** - Track CLAUDE.md changes over time
21. **Linting best practices** - Warn on anti-patterns in CLAUDE.md
### cmdb-assistant (3 items)
22. **cmdb-topology command** - Visualize network/rack topology with Mermaid
23. **Change audit trail** - Track CMDB modifications (wrapper around existing object_changes tools)
24. **IP conflict detection** - Warn on overlapping IP allocations
---
## Sprint 5: Documentation (4 items)
Guides and documentation improvements.
### git-flow (1 item)
25. **Branching strategy documentation** - Document `development -> staging -> main` promotion flow
### clarity-assist (1 item)
26. **ND support documentation** - Document how the plugin supports neurodivergent users
### Additional docs
- Any documentation updates discovered during Sprint 3/4 implementation
---
## Parked Items (Future Sprints)
These items were discussed but deferred:
- Plugin branding / visual output overhaul
- CODEOWNERS integration
- Template library (clarity-assist + claude-config-maintainer)
---
## Technical Notes
### Hook Implementation Pattern
**CRITICAL:** All hooks must be defined in `hooks/hooks.json`, NOT inline in plugin.json.
```
plugins/{name}/
hooks/
hooks.json <-- Hook definitions go here
*.sh <-- Shell scripts for command-type hooks
```
Reference: [Lesson - Plugin Hooks Must Be in Separate File](lessons%2Fpatterns%2Fplugin-hooks-must-be-in-separate-file-not-inline.-)
### Valid Hook Events
- `PreToolUse` - Before tool execution (can block)
- `PostToolUse` - After tool execution
- `UserPromptSubmit` - When user submits prompt
- `SessionStart` - When session begins
- `SessionEnd` - When session ends
### Hook Types
- `command` - Execute shell script (recommended for complex logic)
- `prompt` - Inject prompt text (lightweight, no execution)