asset-placement-gate

# asset-placement-gate Routes new skills, agents, and plugins to the correct location when proposed. ## Triggers - "Should I make this an FH skill?" - "Where should I put this agent?" - When a new FH asset creation is proposed - `/asset-placement-gate {asset name or description}` ### Natural Language Triggers (example user phrases) When unsure where to place a new asset or skill: | Example phrase | Intent | |---|---| | "Should I put this in a separate file?" | Asset necessity + placement decision | | "Can this pattern be shared across projects?" | FH cross-project value assessment | | "Is this only for our project, or can others use it too?" | cross-project vs local routing | | "What if I turn this into a skill and use it across projects?" | FH 4-criteria trigger | | "Where should I put this agent if I want to share it?" | Placement routing needed | | "Should I extract this to a separate file, or leave it?" | Asset necessity + placement decision | | "I'd like to manage this as a shared resource" | Cross-project shared management review | | "Decide whether this stays local or is available to other teams too" | cross-project vs local routing | | "I don't know where to save this" | Placement routing needed | | "Should this become a shared asset?" | FH 4-criteria trigger | ### Execution Order (summary) 1. Request full file path from user (or accept natural language description) 2. Load asset content via `Read` (if path provided) 2.5. Step 0.5 mechanical overlap pre-scan (g...