cross-review-policy

The brainstorming skill transforms initial ideas into detailed specifications through iterative questioning and collaborative dialogue. It helps developers explore design options, evaluate trade-offs, and create shared understanding before implementation. This prevents rework by systematically refining concepts into actionable plans.

This mandatory workflow scans code for legal risks like client names or proprietary references before cross-review. It blocks the review cycle if violations are found, requiring fixes first. Use it as a pre-gate for PR creation, code porting, or any cross-review trigger.

This skill handles repository structure documentation updates after cleanup operations. It automatically updates directory trees, removes references to deleted folders, and documents architectural changes like `.claude/` folders and consolidated scripts. Use it to maintain accurate structure sections in README files following repository reorganization.

This skill identifies legacy directories and files that should be removed or consolidated during repository cleanup. It provides a specific checklist for developers, including paths like `.agent-os/` and `.drcode/` that are obsolete or have been moved to new locations. Use this reference when cleaning up a Claude Code project to ensure proper migration and deletion of outdated assets.