AI IMPLEMENTATION PROMPT

# Haiku Protocol — Reusable AI Implementation Prompt

> **Purpose:** Copy the fenced code block below and paste it at the start of any AI session
> to direct the agent through implementing a specific version sub-part (e.g., `v0.0.1b`).
> Replace every `{placeholder}` with the actual values before submitting.
>
> **Maintained by:** Ryan (project owner)
>
> **Last Updated:** 2026-02-06

---

## How to Use

1. Open a new AI session (Claude, etc.).
2. Copy the entire fenced block below.
3. Replace every `{PLACEHOLDER}` with the real value for your target sub-part.
4. Paste it as your first message.
5. The AI agent will follow the workflow end-to-end.

### Placeholder Reference

| Placeholder | Example Value | Where to Find It |
|---|---|---|
| `{PHASE_NUMBER}` | `1` | `CLAUDE.md` → "Current Phase" |
| `{PHASE_NAME}` | `Environment & Tech Stack` | Phase overview README title |
| `{VERSION}` | `v0.1.2` | Parent version directory name |
| `{SUB_PART_LETTER}` | `c` | Sub-document letter (a, b, c, d) |
| `{SUB_PART_TITLE}` | `Configuration Module Implementation` | Sub-document H1 title |
| `{PARENT_VERSION_TITLE}` | `API Configuration & Secrets` | Parent version README H1 |
| `{SPEC_FILE_PATH}` | `docs/design/phase-1/v0.1.2/configuration_module_implementation.md` | Relative path to sub-doc |
| `{PARENT_SPEC_PATH}` | `docs/design/phase-1/v0.1.2/README.md` | Relative path to parent README |
| `{PHASE_OVERVIEW_PATH}` | `docs/design/phase-1/v0.1.0/README.md` | Relative path to phase overview |
| `{DELIVERABLE_SUMMARY}` | `src/config.py with Config class, .env loading, and validation` | One-sentence deliverable |
| `{USER_STORY}` | `As a developer, I want a Config class so that API keys load from .env automatically.` | From spec's User Story section |
| `{USE_CASE}` | `Developer clones repo, creates .env, imports Config, and calls Config.validate() — returns True if key is valid.` | From spec or your own summary |

---

## The Prompt