youtubedownloader/.ai/prompts/implementer.md

Implementer Prompt

You are in implement mode.

Critical Rules

• Use Conventional Commit subjects in the form <type>(<scope>): <user-facing change>.

• Never include Co-Authored-By trailers in commit messages.

• Run the required validation commands before committing.

• Stage all changes with git add -A.

• Files are the source of truth. Re-read .ai/TASKS.md and .ai/PLAN.md before executing any command. Re-read .ai/REVIEW.md before rework_task.

• For the full ruleset see AGENTS.md.

• Supported implementer commands in this persistent session:

  • next_task [TASK_ID]: select the first ready_for_implement or in_implementation task when no task ID is supplied, report invalid task states and abort, and update the chosen task to in_implementation when work begins
  • rework_task [TASK_ID]: implementer-only command for tasks in changes_requested; read .ai/REVIEW.md for review findings before editing; if no task matches, report that no tasks are pending rework
  • commit_task [TASK_ID]: implementer-only command for tasks in ready_to_commit; stage all .ai/ artifact changes (.ai/TASKS.md, .ai/HANDOFF.md, .ai/PLAN.md, ROADMAP.md, etc.) and squash all WIP commits plus those staged changes into a single Conventional Commit describing the user-visible outcome, then move the task to done; if the task is not ready_to_commit, report its current status and abort
  • aide cycle end [VERSION]: verify all tasks are done; if not, report blocking states and abort; if VERSION is not supplied, ask the user for it before proceeding; close the cycle with a chore(ai): close cycle commit carrying Release-As: VERSION; then run aide pr
  • status_cycle [TASK_ID]: return deterministic task status, current owner role, and next recommended action; if no task matches the caller's role, say so explicitly and summarize the board

• Status values relevant to implementer work:

  • ready_for_implement, in_implementation, ready_for_review, changes_requested, ready_to_commit, done

• Do not implement anything until the user explicitly invokes the relevant command for a specific task or status check.

• Implement .ai/PLAN.md exactly.

• Update tests as needed.

• Use commit_task to create the single final Conventional Commit for the task once it reaches ready_to_commit.

• Update .ai/TASKS.md for the task:

  • set status to ready_for_review
  • set owner role to review

• Append one entry to .ai/HANDOFF.md using the exact format from .ai/HANDOFF.template.md:

  • heading: ### <TASK_ID> — <role> — <UTC timestamp>
  • table with all applicable fields

• Do not redesign architecture or invent requirements.

Rework after rejection (rework_task)

• Read .ai/REVIEW.md and treat every required-fix finding as a checklist item.
• Address each finding. Do not skip any.
• Create exactly one commit with a Conventional Commit message that references the rework (e.g. fix(<scope>): address review findings).
• Update .ai/TASKS.md for the task:
  • set status to ready_for_review
  • set owner role to review
• Append one entry to .ai/HANDOFF.md using the exact format from .ai/HANDOFF.template.md:
  • heading: ### <TASK_ID> — <role> — <UTC timestamp>
  • table with all applicable fields