. d Development process for bugs

JayBazuzi · susanfung · JayBazuzi · commit ae7f3f383b6a · 2026-03-29T16:58:01.000Z
Co-Authored-By: Susan Fung &lt;38925660+susanfung@users.noreply.github.com&gt;
diff --git a/AGENTS.md b/AGENTS.md
@@ -6,4 +6,4 @@ Default STARTER_CHARACTER = 🧩
 - Use `./build_and_test.sh` for full build (this includes mypy and lint)
 - When writing code, follow the code style guidelines in `internal_documentation/code_style.md`.
 - When interacting with GitHub, follow `internal_documentation/github_guidelines.md`.
-- When building a new feature, follow the steps in `internal_documentation/feature_development_process.md`.
+- When building a new feature or fixing a bug, follow the steps in `internal_documentation/development_process.md`.
diff --git a/CLAUDE.md b/CLAUDE.md
@@ -6,4 +6,4 @@ Default STARTER_CHARACTER = 🧩
 - Use `./build_and_test.sh` for full build (this includes mypy and lint)
 - When writing code, follow the code style guidelines in `internal_documentation/code_style.md`.
 - When interacting with GitHub, follow `internal_documentation/github_guidelines.md`.
-- When building a new feature, follow the steps in `internal_documentation/feature_development_process.md`.
+- When building a new feature or fixing a bug, follow the steps in `internal_documentation/development_process.md`.
diff --git a/internal_documentation/development_process.md b/internal_documentation/development_process.md
@@ -1,10 +1,12 @@
-# Feature Development Process
+# Development Process
 
 STARTER_CHARACTER = 😎
 
+For each step below, ask the human for confirmation before proceeding.
+
 1. Create a micro feature document in `internal_documentation/micro_features/` describing the feature
 2. Write a failing test
-3. Implement the feature to make the test pass
+3. Implement the change to make the test pass
 4. Run `./build_and_test.sh` to verify everything passes
 5. Approve the `.received.` files that are correct
 6. Refactor as needed, re-running `./build_and_test.sh` after each change
