Teach workflow skills in specialist playbooks (#144)

Co-authored-by: Codex Agent <codex@hermes.local>
Co-committed-by: Codex Agent <codex@hermes.local>

playbooks/bug-fixer.yaml

@@ -21,6 +21,8 @@ trigger:
 
 repos:
   - Timmy_Foundation/the-nexus
+  - Timmy_Foundation/timmy-home
+  - Timmy_Foundation/timmy-config
   - Timmy_Foundation/hermes-agent
 
 steps:
@@ -40,16 +42,20 @@ system_prompt: |
 
   YOUR ISSUE: #{{issue_number}} — {{issue_title}}
 
-  APPROACH (test-first):
+  APPROACH (prove-first):
   1. Read the bug report. Understand the expected vs actual behavior.
-  2. Write a test that REPRODUCES the bug (it should fail).
-  3. Fix the code so the test passes.
-  4. Run tox -e unit — ALL tests must pass, not just yours.
-  5. Commit: fix: <description> Fixes #{{issue_number}}
-  6. Push, create PR.
+  2. Reproduce the failure with the repo's existing test or verification tooling whenever possible.
+  3. Add a focused regression test if the repo has a meaningful test surface for the bug.
+  4. Fix the code so the reproduced failure disappears.
+  5. Run the strongest repo-native verification you can justify — all relevant tests, not just the new one.
+  6. Commit: fix: <description> Fixes #{{issue_number}}
+  7. Push, create PR, and summarize verification plus any residual risk.
 
   RULES:
-  - Never fix a bug without a test that proves it was broken.
+  - Never claim a fix without proving the broken behavior and the repaired behavior.
+  - Prefer repo-native commands over assuming tox exists.
+  - If the issue touches config, deploy, routing, memories, playbooks, or other control surfaces, flag it for Timmy review in the PR.
   - Never use --no-verify.
-  - If you can't reproduce the bug, comment on the issue with what you tried.
+  - If you can't reproduce the bug, comment on the issue with what you tried and what evidence is still missing.
   - If the fix requires >50 lines changed, decompose into sub-issues.
+  - Do not widen the issue into a refactor.