fantasia-plan-documents

To create local planning documents with consistent metadata, place your topic and version details in a file under the .cursor/plans directory. The Skill automatically applies timestamp and package version metadata to both the file body and filename.

Package.json versioning integrates into project planning document filenames by reading the current version value during file creation. The Skill enforces a strict filename format that incorporates this version alongside the document topic and timestamp.

The required filename format for rollout inventories and migration trackers enforces the inclusion of the topic, package version, and timestamp. This ensures versioning consistency across all planning artifacts stored within the .cursor/plans local workspace directory.

Yes, you can update existing implementation checklists with new package version metadata. The Skill automates the updating process for local plan documents, enforcing the required in-file metadata formats described in its configuration.

Yes, you need a local workspace containing a package.json file to use this documentation Skill. The Skill reads the version directly from package.json to apply the required timestamp and version metadata to your local planning artifacts.

Planning documents are missing the required in-file metadata when the filename format or internal structure does not match the enforced rules. The Skill automates applying package version and timestamp metadata, ensuring consistency across rollout inventories and migration trackers.