Managing BB Conversations

Learn how to effectively manage conversations with BB for optimal results and cost efficiency.

When to Start New Conversations

Starting new conversations helps maintain focus and manage costs. Consider starting new when:

Switching to a different aspect of your project
After completing a significant task
When approaching token limits
When changing direction or strategy

Pro Tip:

Use markdown files outside of BB to document your plan and create clear instructions for new conversations. This helps maintain consistency across multiple sessions while keeping a historical record.

Using the Conversation Summary Tool

When to Use

Long conversations approaching token limits
After completing a major phase of work
Before starting a new but related task
When conversation context becomes too large

How to Use

The conversation summary tool can be accessed:

Via the toolbar button
By asking BB to summarize the conversation
Automatically when approaching token limits

Summary Options:

Short: Essential points only
Medium: Balanced detail
Long: Comprehensive record

Managing Token Usage and Costs

Token usage directly affects costs. Here's how to manage it effectively:

Cost-Saving Strategies

Remove unnecessary files from context
Use conversation summaries regularly
Break large tasks into smaller conversations
Start fresh conversations for new tasks

Things to Avoid

Keeping too many files in context
Running conversations too long
Mixing unrelated tasks
Ignoring token usage warnings

Using Markdown for Planning

Keep markdown files outside BB for better planning and documentation:

Maintain historical reference of decisions
Create clear instructions for new conversations
Document different aspects of complex tasks
Share plans and progress with team members

Workflow Example:

Start planning conversation with BB
Discuss options and approaches
Ask BB to document the plan in markdown
Save markdown file outside BB
Use markdown to seed new focused conversations

Example Templates

Below are examples of markdown templates that BB might create. These aren't meant for direct copying, but rather to show you what to expect when asking BB to document plans or create reference materials. You can also use these as inspiration when asking BB to create custom templates for your specific needs.

Template Examples

Below are some common template examples. For a complete library of templates covering various scenarios, visit our Planning Templates Library →

Basic Planning Template

# Project Task Planning Document

## Overview
- Task Description: [Brief description of what needs to be done]
- Estimated Scope: [Small/Medium/Large]
- Related Files: [List of key files that will be involved]

## Objectives
1. [Primary objective]
2. [Secondary objective]
3. [Additional objectives...]

## File Management
### Core Files
- `path/to/file1.ext`
- `path/to/file2.ext`

### Related Files
- `path/to/related1.ext`
- `path/to/related2.ext`

## Conversation Planning

### Initial Conversation
**Purpose:** [What this conversation will accomplish]
**Key Files:** [Files needed for this conversation]
**Instructions for BB:**
1. [First instruction]
2. [Second instruction]
3. [Additional instructions...]

### Follow-up Conversations
1. **Conversation: [Topic]**
   - Purpose: [What this conversation will accomplish]
   - Key Files: [Files needed]
   - Instructions: [Specific instructions]

## Notes
- [Important considerations]
- [Potential challenges]
- [Dependencies]

## Success Criteria
- [ ] [Criterion 1]
- [ ] [Criterion 2]
- [ ] [Additional criteria...]

Example: API Refactoring Plan

# API Refactoring Project Plan

## Overview
- Task Description: Refactor authentication API to support OAuth 2.0
- Estimated Scope: Large
- Related Files: Authentication system and API endpoints

## Objectives
1. Implement OAuth 2.0 support
2. Maintain backward compatibility
3. Update documentation
4. Add new test coverage

## File Management
### Core Files
- `src/auth/authenticator.ts`
- `src/auth/middleware.ts`
- `src/api/auth-routes.ts`

### Related Files
- `tests/auth/*.test.ts`
- `docs/api/auth.md`
- `config/auth-config.ts`

## Conversation Planning

### Initial Conversation: Architecture Planning
**Purpose:** Design the OAuth implementation approach
**Key Files:**
- `src/auth/authenticator.ts`
- `docs/api/auth.md`

**Instructions for BB:**
1. Review current authentication implementation
2. Analyze OAuth 2.0 requirements
3. Propose architecture changes
4. Document key decision points

### Follow-up Conversations
1. **Conversation: Core Implementation**
   - Purpose: Implement OAuth 2.0 authenticator
   - Key Files: `src/auth/authenticator.ts`, `config/auth-config.ts`
   - Instructions:
     1. Implement OAuth 2.0 flow
     2. Add configuration options
     3. Ensure backward compatibility

2. **Conversation: API Routes Update**
   - Purpose: Update API endpoints for OAuth
   - Key Files: `src/api/auth-routes.ts`, `src/auth/middleware.ts`
   - Instructions:
     1. Add OAuth endpoints
     2. Update middleware
     3. Add validation

3. **Conversation: Testing**
   - Purpose: Add test coverage
   - Key Files: `tests/auth/*.test.ts`
   - Instructions:
     1. Add OAuth flow tests
     2. Update existing tests
     3. Add integration tests

## Notes
- Must maintain existing session-based auth for legacy clients
- Consider rate limiting for OAuth endpoints
- Plan for token storage and refresh flows

## Success Criteria
- [ ] OAuth 2.0 flow working end-to-end
- [ ] Existing auth still works
- [ ] 90%+ test coverage
- [ ] Documentation updated
- [ ] Performance tests pass

Documentation Update Template

# Documentation Update Plan

## Overview
- Task Description: [Description of documentation changes needed]
- Motivation: [Why these changes are needed]
- User Feedback: [Summary of user feedback/issues]

## Documentation Scope
### Core Documents
- `path/to/doc1.md`: [Brief description of changes needed]
- `path/to/doc2.md`: [Brief description of changes needed]

### Related Documents
- `path/to/related1.md`: [Impact/changes needed]
- `path/to/related2.md`: [Impact/changes needed]

### New Documents Needed
- `path/to/new1.md`: [Purpose and content outline]
- `path/to/new2.md`: [Purpose and content outline]

## User Feedback Analysis
### Key Issues
1. [Issue 1]
   - User Impact: [Description]
   - Proposed Solution: [Solution]

2. [Issue 2]
   - User Impact: [Description]
   - Proposed Solution: [Solution]

## Conversation Planning

### Initial Conversation: Content Review
**Purpose:** Review current documentation and plan updates
**Files to Review:**
- [List of files]
**Instructions for BB:**
1. Review current documentation structure
2. Analyze user feedback points
3. Suggest improvements
4. Plan content organization

### Follow-up Conversations
1. **Conversation: Content Updates**
   - Purpose: Update existing documentation
   - Files: [List of files]
   - Instructions:
     1. Update content for clarity
     2. Add missing information
     3. Improve examples

2. **Conversation: New Content Creation**
   - Purpose: Create new documentation
   - Files: [List of new files]
   - Instructions:
     1. Create initial content
     2. Add examples
     3. Ensure consistency

3. **Conversation: Review & Integration**
   - Purpose: Final review and integration
   - Files: [All affected files]
   - Instructions:
     1. Review all changes
     2. Check cross-references
     3. Verify completeness

## Style Guidelines
- [Specific style requirements]
- [Formatting conventions]
- [Voice and tone guidelines]

## Success Criteria
- [ ] All user feedback points addressed
- [ ] New documentation created and integrated
- [ ] Existing documentation updated
- [ ] Cross-references and links verified
- [ ] Style guidelines followed
- [ ] Technical accuracy verified

## Follow-up Plan
- Plan for gathering new user feedback
- Schedule for regular reviews
- Process for maintaining updates

Remember: These templates show BB's capability to create structured documentation. You can ask BB to create similar templates tailored to your specific needs, or to document your current conversation's progress in a similar format.

← Back to How BB Works Understanding BB Guide