Analyze Template System Gaps

Audit Clipper template system against use case for gaps and improvements

Template design audit when a use case must drive new module/role creation and composition must be validated as gracefully-optimistic.

• · Use case description (from $ARGUMENTS or user input)
• · Existing presets, modules, roles, skills, docs

• · Covered: what templates handle well
• · Gaps: module/role/skill/goal/preset/task missing items
• · Recommendations: prioritized improvements ordered by impact

• · Read (template.meta.json files, CLAUDE.md)
• · Grep (find reusable skills and modules)

• · Clipper template structure (presets/, modules/, roles/, templates/docs/)
• · Use case is well-specified (roles, workflows, outputs clear)
• · CLAUDE.md exists with composition rules

• · Use case too broad = too many gaps identified, prioritization unclear
• · Template files missing = incomplete audit surface
• · No gracefully-optimistic path = recommendations require all roles (not modular)
• · Duplicate capabilities in multiple modules = reuse not detected

• · Checks for graceful-optimism (works with minimal roles, improves with optional roles)
• · Identifies module-vs-role-vs-skill gaps with precision
• · Proposes preset only when it would be one-click value
• · Enforces markdown-first skills (not code)