Write a feature spec — the "what & why" of a kandev product feature, before coding. Use ONLY for a product-feature surface (user-visible capability the app supports). Do NOT use for bug fixes, incident postmortems, refactors that preserve behavior, or infra-only work — those get ADRs (if a new convention emerged) and/or regression tests, not specs. Use when the user says "let's spec X" or starts a new product feature.
$npx -y skills add kdlbs/kandev --skill specInstalls into the current project.
Run `npx skills use "https://github.com/kdlbs/kandev" --skill "kdlbs/kandev/spec"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/kdlbs/kandev" that are relevant to the current task. Run `npx skills add "https://github.com/kdlbs/kandev"` and select the relevant skills, then follow their instructions.