Living Prompts
Optional time analysis for complex tasks that may have drifted from the original context.
What Are Living Prompts?
Living prompts are an opt-in feature for complex tasks or bugs. When you request a living prompt, the system analyzes whether the task context is still relevant or if things have changed since the sprint was created.
When to Use Living Prompts
- • Complex features that span multiple files
- • Bugs that may be affected by recent changes
- • Tasks that have been sitting for a while
- • When you need deeper context analysis
Note: Living prompts consume more tokens and can be overkill for simple tasks. The basic task context from your sprint plan is usually sufficient.
How It Works
When you request a living prompt for a task, it can perform time analysis to check if the context is still accurate:
- →Checks if files have changed since the sprint was created
- →Identifies relevant commits that may affect the task
- →Updates the context if things have drifted
When You Don't Need Living Prompts
For most tasks, the context built during sprint generation is enough:
Standard Task Context Works For:
- • Simple features and small changes
- • Tasks you're starting right after sprint generation
- • Well-defined tasks with clear scope
- • Most day-to-day development work
Requesting a Living Prompt
You can ask the AI to prepare a living prompt for a specific subtask:
"Create a living prompt for subtask auth-001 with time analysis"
The AI understands the sprint context and can analyze whether the task context needs updating.
Token Considerations
Living prompts with time analysis consume more tokens because they:
- • Analyze commit history
- • Check file modifications
- • Generate updated context
Use them selectively for complex tasks where the extra context is worth the token cost.