ask-lukas

Installation
SKILL.md

Ask Lukas

You don't remember every skill, so ask. This skill routes a situation to the right skill or flow.

Before stating what a skill does or recommending a step be skipped, read that skill's SKILL.md — the summaries here are for orientation only.

The main flow: idea → ship

  1. Vague idea or underspecified problem → discovery (pressure-test assumptions, compare options).
  2. Requirements need writing down → spec-writing (acceptance criteria, OpenSpec proposals).
  3. Confirmed scope needs decomposition → task-planning (atomic tasks, dependencies, done criteria).
  4. Plan approved, ready to build → plan-execution (inline or subagent modes), which pulls in git-worktrees for isolation, test-driven-development per task, and debugging when things fail.
  5. About to claim it works → verification-before-completion (evidence before claims).
  6. Work is green and needs landing → branch-integration (merge / PR / keep), then pr-body for the pull request write-up.
  7. Code needs review → pr-review (changesets) or code-review (deeper quality/security). Received review feedback → review-response. For feedback on your own Azure DevOps PR, recommend the user-invoked respond-to-pr-comments flow; the human starts it.
  8. Session went sideways or just ended → session-retro (improve the agent's environment, not the code).

On-ramps

Installs
3
First Seen
Oct 13, 2026