design-planlisted

# Skill: design-plan Produces `./design/<brand-slug>/DESIGN-PLAN.md` — a brand-agnostic strategic plan that the `design-system` skill consumes to derive concrete tokens. Think of it as the design equivalent of a PRD: it captures intent, constraints, and direction without committing to specific hex codes or fonts yet. ## When to use - Starting a new branding project (Shane's own brand, a client brand, or an experiment) - Before `/design-system` — the system skill needs strategic input to make non-arbitrary token decisions - When revisiting a brand and the existing plan no longer matches the work Do NOT use this for one-off artifacts where the brand is already defined and a `DESIGN.md` exists. Skip straight to a platform skill. ## Inputs A brand slug (kebab-case, e.g. `shane-personal`, `acme-launch`) and answers to 3 short questions (default) or 8 deeper questions (with `--deep` flag). ## Output `./design/<brand-slug>/DESIGN-PLAN.md` — created in the current working directory. The skill creates the parent dirs if needed. Never write to any other location. ## Steps ### 1. Determine brand slug If the user said "design plan for X", derive the slug from X (kebab-case, lowercase, no special chars). If they didn't, ask: > What brand slug should I use? (kebab-case, e.g. `shane-personal`, `acme-launch`) ### 2. Run the interview **Default (3 questions, ~2 min):** ``` 1. One sentence: who is this brand for, and what do they do? (e.g. "tooling for senior engineers building