groundworklisted

<!-- Copyright 2026 IamK77 — Licensed under the Apache License, Version 2.0. See ./LICENSE and ./NOTICE · https://www.apache.org/licenses/LICENSE-2.0 --> # groundwork !`checklist init ${CLAUDE_SKILL_DIR} --force` Building the wrong thing well is the most expensive mistake in software, and an agent's strongest instinct — implement the literal ask — walks straight into it. This skill is the discipline that runs *before* code: discover the real need, the people it touches, the unspoken constraints, and the explicit edges of scope. Requirements work is a collaboration — you supply systematic rigor, the user supplies domain truth and the stakes. This skill walks an explicit five-stage flight plan and will not fly past a **GATE** until it is cleared. **Discipline:** finish every GATE before entering the next stage. GATEs are hard — never skip, batch past, or self-certify a stage you have not actually done. The `checklist` tool enforces the order; let it. Commands address stages by **name**, so you never have to track a number. **The agent's special handicap:** you cannot walk the floor, run a workshop, or interview the silent stakeholder. So you must enlist **the user as proxy** for everyone the requirement touches, and you must read what *can* be read — the existing code, docs, tickets, competitors. Read [references/agent-blind-spots.md](references/agent-blind-spots.md) first; it names the failure modes this skill exists to stop. **Speak the user's language, or the proxy br