Skill Producer

This handles the production side of design artifacts and calls out to skill-consumer in the test-project, so you're looking at a producer-consumer pattern split across two skills. It outputs a design-document artifact when it runs. Honestly, the value here depends entirely on what skill-consumer does and how they interact, since this is clearly one half of a coordinated workflow. If you're building systems where design generation needs to be decoupled from design consumption or validation, this separation makes sense. Otherwise, you might wonder why these aren't combined into a single skill.