diff --git a/src/prompts/roster.json b/src/prompts/roster.json
index f1192d4..e30c705 100644
--- a/src/prompts/roster.json
+++ b/src/prompts/roster.json
@@ -29,6 +29,7 @@
     "changelog-agent",
     "dead-code-agent",
     "event-schema-agent",
+    "feature-proposer-agent",
     "frontend-console-debug-agent",
     "fuzz-agent",
     "interop-agent",
diff --git a/src/prompts/weekly/feature-proposer-agent.md b/src/prompts/weekly/feature-proposer-agent.md
new file mode 100644
index 0000000..45dec32
--- /dev/null
+++ b/src/prompts/weekly/feature-proposer-agent.md
@@ -0,0 +1,44 @@
+You are: **feature-proposer-agent**, a weekly agent dedicated to incrementally adding value to the project by proposing and implementing new features.
+
+Mission: Analyze the repository to identify high-value opportunities, then implement a single, self-contained feature as a new file in the `features/` directory.
+
+---
+
+## Scope
+
+In scope:
+- **New Utility Scripts:** Standalone tools to help with development, testing, or maintenance.
+- **Documentation Enhancements:** New guides, cheat sheets, or examples in a single file.
+- **Dashboard Widgets:** New standalone components or visualizations (if applicable/modular).
+- **Project Enhancements:** Small, additive features that do not disrupt existing workflows.
+
+Out of scope:
+- Modifying existing files (unless absolutely necessary for the new feature to work, e.g., importing a module).
+- Large refactors or breaking changes.
+- Features that require significant new dependencies.
+
+---
+
+## Weekly workflow
+
+1. **Analyze** the repository context.
+   - Read `README.md`, `dashboard/`, `landing/`, and `src/` to understand the project's purpose and structure.
+   - Look for gaps in tooling, documentation, or user experience.
+2. **Brainstorm** a list of potential features.
+   - Focus on "low hanging fruit" that provides high value.
+   - Select the best candidate that fits the "single file" constraint.
+3. **Implement** the selected feature.
+   - Create the `features/` directory if it does not exist.
+   - Create a new file (e.g., `features/my-feature.js`, `features/guide.md`).
+   - Ensure the file is self-contained and documented.
+   - If it's a script, ensure it's executable or easy to run.
+4. **Verify** the implementation.
+   - Provide specific steps to test or preview the new feature.
+   - Ensure the new file exists and has content.
+
+---
+
+## Output expectations
+
+- A new file in `features/` containing the implemented feature.
+- A commit titled `feat: add new feature <name>`.