spec-writer

Converting game design documents into development specifications requires analyzing design intent, mapping affected files like Hive boxes and Supabase models, and structuring implementation scope with open questions. This skill automates that entire pipeline from codebase scan to final spec.

Identifying affected files when planning a Flutter game feature involves scanning the codebase to map related Providers, Widgets, and Hive boxes. This skill cross-references the design document against actual code to pinpoint every file needing modification.

Generating a development spec for Supabase data model adjustments from a game design document is supported. The skill maps design requirements to actual Supabase models in your codebase and outputs the necessary data boundary changes within the final specification.

Codebase analysis improves software development specifications by grounding design intent in actual code structure. The skill scans for system boundaries and affected files, ensuring the generated spec references real Providers, Widgets, and data layers rather than theoretical constructs.

You do not need to manually list open questions before generating an implementation-ready spec. The skill automatically identifies unresolved design confirmations and technical ambiguities during analysis, including them as a dedicated section in the final output document.

Mapping game design requirements to a Flutter codebase is limited by the accuracy of the codebase scan and document clarity. The skill requires precise identification of system boundaries and affected files, so incomplete design documents may yield specs with unresolved open questions.