qlik-project-scaffold

To scaffold a Qlik project, this skill generates standardized input and artifact directory trees along with an initial dependency-tracking state. It creates subfolders for documentation, brownfield apps, libraries, and architecture, ensuring consistent environments.

Initializing a Qlik project skeleton safely requires non-destructive scaffolding. This skill performs idempotent directory creation, meaning re-running it will not overwrite existing project files or discard previous phase outputs.

Dependency tracking works by initializing a .pipeline-state.json file during the Qlik project setup. This state tracker manages dependencies across different project phases, ensuring artifacts and inputs remain synchronized throughout the workflow.

Yes, you can use this scaffolding tool for brownfield Qlik apps and architecture documentation. It specifically generates input directories tailored for source materials, brownfield applications, libraries, and architecture documentation.

Generating a Qlik project skeleton includes concise templates and README scaffolds for each input and artifact path. These templates guide the setup process by providing standardized structures for phase outputs and source materials.

Re-running a project scaffold does not update existing Qlik phase outputs because the process is designed to be non-destructive and idempotent. It safely initializes missing directories and state files without altering current artifacts.