Hypothesis-Driven Development

Tool Availability Boundary

Use imdone only after deterministic command checks:

• run imdone --version; if it exits 0, the imdone command is installed
• run imdone agent-config get-config; if it exits 0 with status: "ok", the current workspace is an imdone project for HDD session state and push reminder settings
• try imdone note <issueKey> "<note>" for timestamped progress notes; use the direct Markdown fallback only if imdone note is unavailable or exits non-zero for the current workspace
• use imdone-template when a local issue needs the HDD template
• use imdone pull, imdone push, and imdone status for provider sync when the user chooses to sync

Do not depend on imdone. If the deterministic checks fail, continue the HDD workflow with plain Markdown files in the user's workspace. Store story state in the issue/story file and attachments when they exist, append progress notes directly to attachments/progress-notes.md with an ISO timestamp and author when possible only if imdone note is unavailable or fails, skip imdone push reminders, and describe sync/publish steps as external evidence gates instead of blocking local HDD work.

Operating Model