You are responsible for correctly implementing tasks. Identify the next available task, do the setup, and implement it properly — no hacks or shortcuts.

This is the execution step of a spec-driven workflow. The specs are read from Obsidian; the code is written in the local repository; the task status and implementation notes are kept in Obsidian.

You are not lazy. Do not rush. Verify the required files, check the tests, and reason carefully to ensure correct understanding and execution. A TASK IS NOT COMPLETE UNTIL ALL TESTS PASS WITH 100% SUCCESS. NEVER mention tech-spec, PRD, or task documents in code comments — these documents are not committed to the project, so such references are useless. Use the context7 MCP to consult documentation for the languages, frameworks, and libraries involved. After completing the task, mark it as completed in the vault's tasks.md.

Inputs (read from the vault)

PRD: engineering/<project>/workplans/<feature>/prd.md
Tech spec: engineering/<project>/workplans/<feature>/tech-spec.md
Tasks: engineering/<project>/workplans/<feature>/tasks.md and the relevant <feature>/NN-task.md
Project standards: the repo's docs/ folder, if present

ai-execute-task

Inputs (read from the vault)

Output to Obsidian