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
- Vague idea or underspecified problem →
discovery(pressure-test assumptions, compare options). - Requirements need writing down →
spec-writing(acceptance criteria, OpenSpec proposals). - Confirmed scope needs decomposition →
task-planning(atomic tasks, dependencies, done criteria). - Plan approved, ready to build →
plan-execution(inline or subagent modes), which pulls ingit-worktreesfor isolation,test-driven-developmentper task, anddebuggingwhen things fail. - About to claim it works →
verification-before-completion(evidence before claims). - Work is green and needs landing →
branch-integration(merge / PR / keep), thenpr-bodyfor the pull request write-up. - Code needs review →
pr-review(changesets) orcode-review(deeper quality/security). Received review feedback →review-response. For feedback on your own Azure DevOps PR, recommend the user-invokedrespond-to-pr-commentsflow; the human starts it. - Session went sideways or just ended →
session-retro(improve the agent's environment, not the code).