implement-speclisted

# Implement Spec Follows the `aiwork-protocol` skill. Don't enter plan mode: the spec and tickets are the plan. ## 1. Resolve input `$ARGUMENTS` is a spec/PRD or task folder path. With no args, find the most recently modified task folder (per `aiwork-protocol` conventions). Resolve it to an **absolute path** and use that everywhere, including in subagent prompts. Locate the `tickets/` subfolder: - **No tickets** → suggest `/to-tickets`, or `/implement <spec>` if the spec is small enough for one pass. Stop. - **All tickets `done` but no `review.md`** → go straight to Wrap-up (§5). - Nothing found → tell the user and stop. ## 2. Clarity gate Before touching code, check the spec is concrete enough for an unattended run. **Warn and stop for confirmation** if any hold: - Open questions, TBDs, or unresolved decisions - Key technical choices (data model, API shape, file targets) unspecified - Success criteria too vague to tell when "done" - Content is contradictory, out of order, or otherwise corrupted The gate runs **once**, against the spec, not per ticket. A badly specified ticket discovered mid-chain doesn't stop for confirmation: resolve it with best judgment and record the gap and resolution in `implementation-notes.md`. This gate is the **last stop**. Past it, run unattended to the end. ## 3. Task worktree Run the whole task in its own worktree so the user's checkout stays free. Skip this only when the session is already in a worktree or the user asked to stay in t