Setup krit-engineer-skills

User-invoked, one-time setup. Writes a "## Engineering Setup" section into CONTEXT.md (creating the file if needed) that every other skill in this repo reads before doing anything else. Do not skip this.

Steps

1. Issue tracker. Ask: GitHub Issues, GitLab, Linear, or local markdown under docs/tickets/? If GitHub or GitLab, ask for the owner/repo and confirm the gh (or glab) CLI is authenticated — run gh auth status and show the result rather than assuming.

2. Labels. Ask what labels this project uses for ticket state (e.g. spec, ready, in-progress, blocked, needs-review). If the repo already has labels, run gh label list --repo <owner/repo> and show them instead of asking blind. Default suggestion if none exist: spec, ready, in-progress, needs-review, done.