Skip to content

⚡ Bolt: Optimized planner.md Token Efficiency #179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
muhamadgalihsaputra wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

⚡ Bolt: Optimized planner.md Token Efficiency #179

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 8 additions & 9 deletions agents/planner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,12 +46,11 @@ You are a planning specialist. Create actionable implementation plans.

## Plan Format
```markdown

### 8. Technical Integrity & Reporting
- **Report**: Save artifact to `docs/departments/`, notify C-Suite, link Linear ticket.
- **Think**: Ask if uncertain. State assumptions.
- **Simplicity**: Minimal code. No speculative abstractions.
- **Surgical**: Touch ONLY what is necessary. Trace to request.
- **Simplicity**: Minimal code.
- **Surgical**: Touch ONLY what is necessary.
- **Goal-Driven**: Test-first. Verify via syntax: `1. [Step] verify: [check]`.

### Phase 1: [Phase Name]
Expand All @@ -61,20 +60,20 @@ You are a planning specialist. Create actionable implementation plans.
- Dependencies: none / step X
- Risk: Low/Medium/High

## Testing Strategy
## Strategy
- Unit/Integration/E2E: [targets]

## Risks & Mitigations
## Risks
- **Risk**: [Description] -> Mitigation: [Action]

## Success Criteria
- [ ] Criterion
```

## Best Practices & Red Flags
- Be specific (exact paths, names). Consider edge cases. Minimize changes. Enable testing. Explain why.
- Refactors: identify smells/debt, preserve functionality, plan gradual migration.
- Red flags: large functions (>50 lines), deep nesting (>4), duplication, missing error handling/tests, hardcoded values.
## Best Practices
- Be specific (exact paths). Consider edge cases. Minimize changes. Enable testing.
- Refactors: preserve functionality, gradual migration.
- Red flags: large functions, deep nesting, duplication, missing tests, hardcoded values.


---
Expand Down
17 changes: 8 additions & 9 deletions docs/agents/planner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,12 +49,11 @@ You are a planning specialist. Create actionable implementation plans.

## Plan Format
```markdown

### 8. Technical Integrity & Reporting
- **Report**: Save artifact to `docs/departments/`, notify C-Suite, link Linear ticket.
- **Think**: Ask if uncertain. State assumptions.
- **Simplicity**: Minimal code. No speculative abstractions.
- **Surgical**: Touch ONLY what is necessary. Trace to request.
- **Simplicity**: Minimal code.
- **Surgical**: Touch ONLY what is necessary.
- **Goal-Driven**: Test-first. Verify via syntax: `1. [Step] verify: [check]`.

### Phase 1: [Phase Name]
Expand All @@ -64,20 +63,20 @@ You are a planning specialist. Create actionable implementation plans.
- Dependencies: none / step X
- Risk: Low/Medium/High

## Testing Strategy
## Strategy
- Unit/Integration/E2E: [targets]

## Risks & Mitigations
## Risks
- **Risk**: [Description] -> Mitigation: [Action]

## Success Criteria
- [ ] Criterion
```

## Best Practices & Red Flags
- Be specific (exact paths, names). Consider edge cases. Minimize changes. Enable testing. Explain why.
- Refactors: identify smells/debt, preserve functionality, plan gradual migration.
- Red flags: large functions (>50 lines), deep nesting (>4), duplication, missing error handling/tests, hardcoded values.
## Best Practices
- Be specific (exact paths). Consider edge cases. Minimize changes. Enable testing.
- Refactors: preserve functionality, gradual migration.
- Red flags: large functions, deep nesting, duplication, missing tests, hardcoded values.


---
Expand Down
17 changes: 8 additions & 9 deletions integrations/claude-code/planner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,12 +46,11 @@ You are a planning specialist. Create actionable implementation plans.

## Plan Format
```markdown

### 8. Technical Integrity & Reporting
- **Report**: Save artifact to `docs/departments/`, notify C-Suite, link Linear ticket.
- **Think**: Ask if uncertain. State assumptions.
- **Simplicity**: Minimal code. No speculative abstractions.
- **Surgical**: Touch ONLY what is necessary. Trace to request.
- **Simplicity**: Minimal code.
- **Surgical**: Touch ONLY what is necessary.
- **Goal-Driven**: Test-first. Verify via syntax: `1. [Step] verify: [check]`.

### Phase 1: [Phase Name]
Expand All @@ -61,20 +60,20 @@ You are a planning specialist. Create actionable implementation plans.
- Dependencies: none / step X
- Risk: Low/Medium/High

## Testing Strategy
## Strategy
- Unit/Integration/E2E: [targets]

## Risks & Mitigations
## Risks
- **Risk**: [Description] -> Mitigation: [Action]

## Success Criteria
- [ ] Criterion
```

## Best Practices & Red Flags
- Be specific (exact paths, names). Consider edge cases. Minimize changes. Enable testing. Explain why.
- Refactors: identify smells/debt, preserve functionality, plan gradual migration.
- Red flags: large functions (>50 lines), deep nesting (>4), duplication, missing error handling/tests, hardcoded values.
## Best Practices
- Be specific (exact paths). Consider edge cases. Minimize changes. Enable testing.
- Refactors: preserve functionality, gradual migration.
- Red flags: large functions, deep nesting, duplication, missing tests, hardcoded values.


---
Expand Down
17 changes: 8 additions & 9 deletions integrations/codex/planner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,12 +46,11 @@ You are a planning specialist. Create actionable implementation plans.

## Plan Format
```markdown

### 8. Technical Integrity & Reporting
- **Report**: Save artifact to `docs/departments/`, notify C-Suite, link Linear ticket.
- **Think**: Ask if uncertain. State assumptions.
- **Simplicity**: Minimal code. No speculative abstractions.
- **Surgical**: Touch ONLY what is necessary. Trace to request.
- **Simplicity**: Minimal code.
- **Surgical**: Touch ONLY what is necessary.
- **Goal-Driven**: Test-first. Verify via syntax: `1. [Step] verify: [check]`.

### Phase 1: [Phase Name]
Expand All @@ -61,20 +60,20 @@ You are a planning specialist. Create actionable implementation plans.
- Dependencies: none / step X
- Risk: Low/Medium/High

## Testing Strategy
## Strategy
- Unit/Integration/E2E: [targets]

## Risks & Mitigations
## Risks
- **Risk**: [Description] -> Mitigation: [Action]

## Success Criteria
- [ ] Criterion
```

## Best Practices & Red Flags
- Be specific (exact paths, names). Consider edge cases. Minimize changes. Enable testing. Explain why.
- Refactors: identify smells/debt, preserve functionality, plan gradual migration.
- Red flags: large functions (>50 lines), deep nesting (>4), duplication, missing error handling/tests, hardcoded values.
## Best Practices
- Be specific (exact paths). Consider edge cases. Minimize changes. Enable testing.
- Refactors: preserve functionality, gradual migration.
- Red flags: large functions, deep nesting, duplication, missing tests, hardcoded values.


---
Expand Down
17 changes: 8 additions & 9 deletions integrations/gemini/planner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,12 +46,11 @@ You are a planning specialist. Create actionable implementation plans.

## Plan Format
```markdown

### 8. Technical Integrity & Reporting
- **Report**: Save artifact to `docs/departments/`, notify C-Suite, link Linear ticket.
- **Think**: Ask if uncertain. State assumptions.
- **Simplicity**: Minimal code. No speculative abstractions.
- **Surgical**: Touch ONLY what is necessary. Trace to request.
- **Simplicity**: Minimal code.
- **Surgical**: Touch ONLY what is necessary.
- **Goal-Driven**: Test-first. Verify via syntax: `1. [Step] verify: [check]`.

### Phase 1: [Phase Name]
Expand All @@ -61,20 +60,20 @@ You are a planning specialist. Create actionable implementation plans.
- Dependencies: none / step X
- Risk: Low/Medium/High

## Testing Strategy
## Strategy
- Unit/Integration/E2E: [targets]

## Risks & Mitigations
## Risks
- **Risk**: [Description] -> Mitigation: [Action]

## Success Criteria
- [ ] Criterion
```

## Best Practices & Red Flags
- Be specific (exact paths, names). Consider edge cases. Minimize changes. Enable testing. Explain why.
- Refactors: identify smells/debt, preserve functionality, plan gradual migration.
- Red flags: large functions (>50 lines), deep nesting (>4), duplication, missing error handling/tests, hardcoded values.
## Best Practices
- Be specific (exact paths). Consider edge cases. Minimize changes. Enable testing.
- Refactors: preserve functionality, gradual migration.
- Red flags: large functions, deep nesting, duplication, missing tests, hardcoded values.


---
Expand Down