Compare commits

..

7 Commits

Author SHA1 Message Date
Drew Ritter
935de5d5ec Simplify Codex hook entrypoint 2026-05-14 15:51:53 -07:00
Drew Ritter
f5c43d6055 test: add Codex native hook drill coverage 2026-05-13 18:21:55 -07:00
Drew Ritter
51514f86c8 feat: support Codex native plugin hooks 2026-05-13 18:21:07 -07:00
Drew Ritter
a57b6c5dc1 docs: plan Codex native hooks implementation 2026-05-13 18:19:42 -07:00
Drew Ritter
de320dce01 docs: record Codex hook contract spike 2026-05-13 18:19:42 -07:00
Drew Ritter
62b64d1674 docs: refine Codex hooks spec after review 2026-05-13 18:19:42 -07:00
Drew Ritter
09f3871be2 docs: specify Codex native hooks parity 2026-05-13 18:19:42 -07:00
2 changed files with 4 additions and 4 deletions

2
evals

Submodule evals updated: e2b37138c8...29957de826

View File

@@ -102,15 +102,15 @@ These thoughts mean STOP—you're rationalizing:
When multiple skills could apply, use this order:
1. **Process skills first** (brainstorming, systematic-debugging) - these determine HOW to approach the task
1. **Process skills first** (brainstorming, debugging) - these determine HOW to approach the task
2. **Implementation skills second** (frontend-design, mcp-builder) - these guide execution
"Let's build X" → brainstorming first, then implementation skills.
"Fix this bug" → systematic-debugging first, then domain-specific skills.
"Fix this bug" → debugging first, then domain-specific skills.
## Skill Types
**Rigid** (TDD, systematic-debugging): Follow exactly. Don't adapt away discipline.
**Rigid** (TDD, debugging): Follow exactly. Don't adapt away discipline.
**Flexible** (patterns): Adapt principles to context.