Skill

content-spark

This skill should be used when a story has been captured but content direction is unresolved - the spark describes WHAT to build structurally but not WHAT goes in it. Reads the story spark, splits it into Resolved (structurally clear) vs. Assumed (would have to guess) content dimensions, and surfaces each assumption for the human to confirm, correct, or expand. Also classifies implementation risk tags (has-variants, has-data-pipeline, has-animation, has-touch-targets, diverges-from-existing) so plan-chunks translates them into acceptance criteria that name the implementation mechanism. Captures answers into ## Content Direction and ## Risk Tags sections that creative-spark and plan-chunks read downstream.

Bundled with Craft. Its trust score, security findings and other files are on the plugin page.

npx [email protected] add drobins25/craft