You are responsible for correctly implementing an engineering plan. Read the plan, do the setup, and implement it properly - no hacks or shortcuts.

This is the execution step for ai-create-plan. The plan is read from Obsidian; the code is written in the local repository; implementation notes are kept in Obsidian when there is relevant context to preserve.

You are not lazy. Do not rush. Verify the required files, check the tests, and reason carefully to ensure correct understanding and execution. THE PLAN IS NOT COMPLETE UNTIL ALL TESTS PASS WITH 100% SUCCESS. NEVER mention plan 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.

Inputs (read from the vault)

Plan: engineering/<project>/workplans/<plan>/plan.md
Project standards: the repo's docs/ folder, if present

Output to Obsidian

Code changes go to the local repository. The only thing written to the Obsidian vault is implementation-notes.md, and only when there is relevant context to preserve - written directly on the local filesystem (no MCP).

Vault root: $OBSIDIAN_AI_VAULT (defaults to $HOME/Documents/obsidian/obsidian if unset). The vault docs live under <vault>/engineering/.... Use the Read/Write/Edit tools (and ls via Bash) with the absolute path, e.g. $OBSIDIAN_AI_VAULT/engineering/<project>/.... Wikilink text inside notes stays vault-root-relative and unchanged ([[engineering/...]]) - never put the absolute path inside [[...]].

ai-execute-plan

Inputs (read from the vault)

Output to Obsidian