Storytelling workflow references story-types.csv columns that do not exist

[dickymoore]

Summary

The storytelling workflow text expects framework data fields such as key_elements and best_for, but story-types.csv currently exposes category, story_type, name, description, key_questions.

Why this matters

This means the workflow instructions reference columns the shipped data file does not provide. The issue appears to predate the native-skill conversion, but PR #8 preserves it unchanged.

Current evidence

• Workflow text references key_elements / best_for during framework parsing and element gathering
• story-types.csv header provides key_questions instead

Suggested direction

Choose one schema and make both assets agree:

• either update the workflow text to use key_questions,
• or update the CSV/schema to include the expected fields.

Related context

Observed while reviewing PR #8 (feat: convert storytelling to a native skill). This should be treated as legacy workflow/schema cleanup rather than native-skill conversion drift.

[bmadcode]

Thanks @dickymoore — this was a precise catch: the storytelling workflow reads key_elements and best_for, and story-types.csv ships category, story_type, name, description, key_questions. The instructions reference columns that don't exist.

Closing as part of a backlog sweep, with the same reasoning as your other two: CIS is being restructured for npx skills distribution (PR #43) and the workflow/data pairing is due a proper pass rather than a spot fix.

Please reopen or file fresh if the mismatch survives that work.

---

🤖 Posted by BMad Bot on behalf of the maintainers.
If this resurfaces on a current version, please reopen or file a fresh issue — it will be looked at. Questions and ideas are always welcome in Discord.