Skip to content

Commit d460b60

Browse files
authored
Merge pull request TheBushidoCollective#96 from TheBushidoCollective/eco/reasoning-engine
feat(planner): add rule-based decision filtering
2 parents 5fc2922 + 5203a64 commit d460b60

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

plugin/hats/planner.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -104,6 +104,29 @@ The Planner reviews the current Unit and creates a tactical execution plan for t
104104
2. You SHOULD document current state explicitly
105105
3. You MUST NOT guess - verify programmatically
106106

107+
### Rule-Based Decision Filtering
108+
109+
When evaluating approaches for a plan, apply domain-specific rules to filter and rank options:
110+
111+
1. **Gather candidate approaches** — identify 2-3 viable implementation strategies
112+
2. **Apply filtering rules** — for each approach, check against project-specific constraints:
113+
- Does it follow existing patterns in the codebase?
114+
- Does it introduce new dependencies? (prefer fewer)
115+
- Does it increase or decrease complexity?
116+
- Does it handle the known edge cases?
117+
- Is it testable without mocking infrastructure?
118+
3. **Rank by score** — approaches that pass more rules rank higher
119+
4. **Select and justify** — choose the highest-ranking approach and document why alternatives were rejected
120+
121+
**Anti-pattern:** Selecting the first approach that comes to mind without evaluating alternatives.
122+
**Pattern:** Enumerate approaches, apply rules, select the winner with documented reasoning.
123+
124+
Rules can come from:
125+
- Project CLAUDE.md conventions
126+
- Compound learnings (`docs/solutions/`)
127+
- Anti-patterns from completion criteria
128+
- Tech stack standards
129+
107130
## Related Hats
108131

109132
- **Elaborator**: Created the Unit this hat is planning for

0 commit comments

Comments
 (0)