[selvathiruarul]

Summary

Adds dev-workflow under skills/tools/: a ticket-to-PR development loop that works
with any tracker, PR host, and coding agent.

Why

Agents working a ticket freehand tend to fail in the same four ways. The skill answers
each with one mechanism:

Failure	Mechanism
Coding before the plan is agreed	Plan is shown, agent stops until approved
"Looks done" without proof	Every subtask carries a command that proves it works
Acceptance criteria silently dropped	Each numbered criterion maps to a subtask and to a row in the PR
Context lost between sessions	Gitignored task file (.agents/tasks/<KEY>.md) holds subtasks, decisions, next action

What's included

• skills/tools/dev-workflow/SKILL.md — the workflow: understand → plan → approve →
  implement → test → PR, plus resume and close
• skills/tools/dev-workflow/evals/evals.json — two cases:
  1. planning a ticket produces a covered, testable plan and stops for approval
  2. resuming checks git state before trusting the task file
• README.md — new Available skills table with this skill as the first row

Contributing checklist

• Documents behavior using only real tools (git, gh, the agent's tracker integration). No invented APIs
• No absolute or machine-specific paths. Everything is repo-relative
• name frontmatter matches the folder, lowercase-hyphenated
• Includes ## Validation commands and ## Realistic usage boundaries
• Within the 130–340 line guideline (309 lines)
• At least two portable eval cases
• README table row added

How to verify

node scripts/verify-skills.mjs
node scripts/verify-manifests.mjs
node scripts/check-internal-links.mjs
node scripts/verify-evals.mjs
npx markdownlint-cli2 README.md skills/tools/dev-workflow/SKILL.md