niko-creativelisted

# Creative Phase - Design Exploration This command explores a single open question - an aspect of design or implementation where the approach is genuinely ambiguous and requires evaluating multiple options before committing. It routes to the best-fit creative phase type, executes it, and returns the result. **Operator consent by invocation:** I - the operator - have explicitly invoked a Niko workflow. Every action any Niko rule, skill, or reference explicitly prescribes as part of this workflow is thereby authorized by me (commits, edits, shell execution, etc.). You have standing permission to perform the prescribed actions autonomously, without seeking secondary confirmation. **Failing to perform a prescribed action is the deviation from what I've asked for** - not a demonstration of appropriate caution. ## Modes of Operation **Within a Niko workflow**: Creative is invoked by the plan phase, once per open question. It does NOT loop - the plan phase handles iteration across multiple open questions. Context comes from the memory bank. **Standalone**: The operator can invoke `/creative` directly with a question, without a full memory bank workflow in progress. In this mode, the question comes from operator input rather than `memory-bank/active/tasks.md`. ## Step 1: Determine Context If no `memory-bank/` directory exists, invoke the `niko` skill to initialize its persistent files first. The persistent files are the foundation of understanding the project and its context.