kevinslin/dev.do

dev.do

Overview

Drive a single dev task from intake to completion: parse the task input, gather repo context, ask only necessary questions, then hand off to dev.loop for plan/execute/verify/cleanup.

Workflow

1) Intake and classify the task

• Identify the input type: file path, pasted description, or git issue/issue URL.
• Capture the goal and any acceptance criteria or constraints.
• If the task came in as a git issue, update the Status to In progress. Add the following comment: Starting task in session [llm_session]. Use dev.llm-session skill to get llm session id

2) Gather context

• If a file path: open it and skim adjacent/related files (imports, references, tests, configs).
• If a pasted description: locate relevant files using search (rg) and open the most likely targets.
• If a git issue: load the issue text. Use repo tools if available (e.g., gh issue view <id>), otherwise ask the user to paste the issue body.

3) Clarify only when needed

• Ask concise questions when any of the following are unclear:
  • Target repo or file(s)
  • Definition of done / expected output
  • Constraints (APIs, style, backwards compatibility)
  • Inputs/outputs or failure cases
  • Tests to run or skip
• If everything is clear, do not ask questions.

4) Execute with dev.loop

• Use $dev.loop skill to plan, implement, verify, and cleanup. You MUST FOLLOW every step of $dev.loop - this includes the Verify of the workflow which triggers a pr pushes and spawns subagents to check ci and do review. NEVER SKIP the verify phase
• Pass along the task summary, relevant files, and any constraints/acceptance criteria.
• When creating the PR, be sure to include the issue URL so that the PR can be linked to the issue
• Hard completion gate for code changes:
  • Do not stop at local edits/commit.
  • Ensure branch is pushed to remote.
  • Ensure a PR exists and capture its URL.
  • If no PR exists yet, run trigger:push-pr before final handoff.
  • If push/PR creation fails, report the exact command error and what retry was attempted.
  • Ensure Verify phase of $dev.loop is carried out

5) Cleanup

• If the task came in as a git issue and user invokes the merge-pr shortcut, update the Status to Done

Output expectations

• If questions are needed, ask them first and pause.
• Otherwise, immediately run dev.loop and complete the task end-to-end.
• For code changes, final report must include PR URL and confirmation that the branch was pushed.