# 💡 3 Credit-Smart Strategies to Maximize Kiro’s Potential

Source: https://www.youtube.com/watch?v=kS2lnjrFw-M
Recap page: https://rapidrecap.app/video/kS2lnjrFw-M
Generated: 2025-11-11T21:32:06.492+00:00

---
## Quick Overview

Kiro's latest version introduces three productivity strategies to maximize credit usage: enabling Auto mode to save credits, creating custom steering documents for specific use cases like adding an MCP server, and explicitly marking unit tests as optional to avoid unnecessary credit consumption.

**Key Points:**
- The new Kiro version features an 'Auto mode' toggle at the bottom right, which the presenter recommends leaving on to save credits for general usage.
- The presenter demonstrated creating a detailed steering document named 'mcp-server-info' by clicking the plus icon in the Agent Steering section to guide Kiro on adding a weather system MCP Server.
- When creating steering documents, the user should be specific, such as instructing Kiro to 'Please start at task 1 and end at task 2.1' to define the scope of work.
- The implementation plan for the weather MCP server involves 25 sub-tasks across several major phases, including core setup, data modeling, API client infrastructure, and integration testing.
- The presenter showed how to explicitly mark tasks in the Implementation Plan as optional (e.g., comprehensive test suite) by clicking the 'Make task required' button, which defaults to required.
- The new version also allows users to leverage external resources like the Context7 MCP Server for documentation retrieval, configured via 'mcp.json'.

![Screenshot at 0:08: The presenter is shown in a small window next to a VS Code-like interface displaying Python code defining a weather-focused system prompt with HTTP capabilities, illustrating the core development context.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-00-08.png)

**Context:** This video, hosted by Erik Hanchett, a Senior Developer Advocate, demonstrates new productivity features in the latest version of Kiro, an AI coding assistant environment. The focus is on optimizing credit usage and structuring complex development workflows, specifically by leveraging Auto mode, creating detailed steering documents, and managing task dependencies within an implementation plan for a new weather MCP (Model Context Protocol) Server.

## Detailed Analysis

The video details three primary credit-saving and productivity strategies for the latest version of Kiro. First, the presenter advises keeping the 'Auto' mode toggle enabled (0:18) for general operation, as this saves credits compared to manual prompting. Second, the video emphasizes creating detailed steering documents to guide complex tasks, using the example of adding a dedicated weather MCP Server. This involves navigating to the Agent Steering section, clicking the plus icon, naming the document (e.g., 'mcp-server-info' at 1:37), and providing explicit rules, such as ensuring Kiro uses the Context7 MCP Server for documentation retrieval (1:45). Third, the presenter shows how to manage tasks within the automatically generated Implementation Plan (10:00). By clicking 'Make task required' (3:55), users can designate tasks as optional, thus preventing Kiro from consuming credits on unnecessary work like comprehensive unit testing, which the presenter marked as optional. The overall goal is to build a professional MCP server that enhances a weather agent with advanced caching, multiple weather services, and additional data types like air quality information, as detailed in the generated requirements and design documents (2:40).

### Kiro Productivity Features

- Auto mode enabled for credit saving
- Creation of custom steering documents for specific needs
- Ability to mark implementation tasks as optional

### MCP Server Implementation Plan

- Project setup and core foundation
- Development of core data models and configuration
- Building weather API client infrastructure
- Integration of the weather service router and fallback system

### Steering Document Customization

- Creating 'mcp-server-info' document
- Defining rules for MCP server documentation retrieval via Context7
- Prompting Kiro explicitly for task scope, e.g., 'start at task 1 and end at task 2.1'

### Implementation Plan Walkthrough

- Project structure setup (Task 1)
- Data modeling and validation (Task 2)
- Configuration management (Task 3)
- API client infrastructure (Task 4)
- Integration and testing phases (Tasks 5-7)

![Screenshot at 0:01: Video title card displaying 'KIRO 3 Productivity Tips' against a black background.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-00-01.png)
![Screenshot at 0:02: Erik Hanchett, Senior Developer Advocate, introduces the topic directly to the camera in his brightly lit studio setup.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-00-02.png)
![Screenshot at 0:08: The main workspace shows a Python file \('weather\_agent.py'\) being edited, with Kiro's assistant panel open on the right.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-00-08.png)
![Screenshot at 0:19: Close-up on the bottom right of the Kiro interface highlighting the new 'Auto' mode toggle switch.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-00-19.png)
![Screenshot at 0:36: The sidebar view showing the newly added 'mcp-server-info' under Agent Steering, following the creation of a new document.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-00-36.png)
![Screenshot at 1:10: The 'mcp.json' configuration file showing the setup for the Context7 MCP Server, including command details and library ID references.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-01-10.png)
![Screenshot at 2:40: The 'requirements.md' file generated by Kiro, detailing the overview, glossary, and specific requirements for the weather MCP server.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-02-40.png)
![Screenshot at 3:40: The 'tasks.md' file showing the comprehensive Implementation Plan, broken down into numbered start tasks and sub-tasks.](https://ss.rapidrecap.app/screens/kS2lnjrFw-M/00-03-40.png)