skill-system-architect

To design multi-command skill architecture, establish formal shared state schemas and command routing logic before implementation. This prevents fragmented skill sets by producing a comprehensive blueprint defining directory layouts, state definitions, and command boundaries.

Consolidating overlapping skills requires analyzing existing functionality to merge them into a coherent system with a unified interface. This involves defining command maps, enforcing command boundaries, and establishing consistent interface design across the consolidated suite.

You need formal state management schemas when expanding single skills into complex, sub-command-driven suites. Establishing shared state definitions and command routing logic beforehand ensures structured boundaries and prevents overlapping functionality across your skill architecture.

Yes, this system design approach explicitly enforces command boundaries for complex skill suites. It produces an architecture specification that defines command contracts, routing logic, and consistent interface design to prevent overlap and ensure structured state management.

To specify directory layouts and command contracts for skill handoff, produce a comprehensive architecture blueprint. This blueprint defines the shared state schemas, command maps, and routing logic required for seamless implementation by the skill-creator.

Overlapping skills cause fragmented architectures because they lack formal state management and command routing logic before implementation begins. Without a defined system design, boundaries blur, resulting in inconsistent interfaces and poorly structured skill sets.