Enhance Amazon Q CLI agent behavior for more proactive coding assistance

## Issue Description

The Amazon Q CLI agent currently doesn't act as proactively as a coding assistant as desired. It tends to be more conservative rather than "eager to get hands on keyboard" when it comes to coding tasks.

## Desired Behavior
- More proactive code generation without excessive prompting
- Quicker to offer complete code solutions rather than just guidance
- Better at understanding when to jump straight to implementation
- More willing to make educated assumptions to move forward with coding tasks
- Improved recognition of coding contexts that warrant direct assistance

## Potential Solutions
- Investigate if there are configuration options in the Amazon Q CLI that can adjust this behavior
- Research if building from source (as mentioned in our dotfiles philosophy) would allow customization
- Consider creating custom prompts or aliases that encourage more direct coding assistance
- Look into whether there are environment variables or settings that influence agent behavior

## Related Context
This aligns with our "tracer bullet" development approach mentioned in our dotfiles philosophy, where we want tools that help us move quickly and iteratively.

## Next Steps
- Research Amazon Q CLI configuration options
- Test different prompting strategies
- Consider building from source if necessary to modify behavior

## References
- [Amazon Q Developer CLI GitHub Repository](https://github.com/aws/amazon-q-developer-cli)

No repository file, test, or entry point is identified. Start by checking Amazon Q CLI configuration options, then investigate the custom prompts, aliases, environment variables, and settings named in the issue. Done requires a defined proactive behavior change and validation through prompting or a source customization.

Written by the indexing model from the issue text.