- New skill: token-budget-report.md with MCP overhead and skill loading estimation model based on known file sizes and static overhead tables - Sprint-plan displays token report after planning complete - Sprint-close displays token report after lessons captured - Visual-output.md updated with token report format - .gitignore exception for token-budget-report.md (not API tokens) Helps identify which phases and components consume the most context budget. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2.7 KiB
2.7 KiB
description, agent
| description | agent |
|---|---|
| Start sprint planning with AI-guided architecture analysis and issue creation | planner |
Sprint Planning
Skills Required
- skills/mcp-tools-reference.md (frontmatter — auto-injected)
- skills/batch-execution.md (frontmatter — auto-injected)
- skills/branch-security.md
- skills/repo-validation.md
- skills/input-detection.md
- skills/lessons-learned.md
- skills/wiki-conventions.md
- skills/task-sizing.md
- skills/issue-conventions.md
- skills/sprint-approval.md
- skills/planning-workflow.md
- skills/label-taxonomy/labels-reference.md
- skills/sprint-lifecycle.md
- skills/token-budget-report.md
Purpose
Initiate sprint planning session. The planner agent validates prerequisites, gathers requirements, searches lessons learned, creates wiki pages, and creates well-structured Gitea issues with proper dependencies and labels.
Invocation
Provide sprint goals as natural language input, or prepare input via:
docs/changes/*.mdfile with frontmatter- Existing wiki proposal page
- Direct conversation
Workflow
Execute the planning workflow as defined in skills/planning-workflow.md.
Key steps:
0. Check Lifecycle State - Execute skills/sprint-lifecycle.md check protocol. Expect idle state. Set Sprint/Planning after planning completes. Warn and stop if sprint is in another active state (unless --force).
- Run pre-planning validations (branch, repo org, labels)
- Detect input source (file, wiki, or conversation)
- Search relevant lessons learned
- Create/update wiki proposal and implementation pages
- Perform architecture analysis
- Create Gitea issues with wiki references (respecting task sizing rules)
- Set up dependencies
- Create or select milestone
- Request explicit sprint approval
Visual Output
╔══════════════════════════════════════════════════════════════════╗
║ 📋 PROJMAN ║
║ 🎯 PLANNING ║
║ [Sprint Name] ║
╚══════════════════════════════════════════════════════════════════╝
Final Step: Token Budget Report
After displaying the planning summary and gaining sprint approval, generate a Token Budget Report per skills/token-budget-report.md.
- Phase: PLANNING
- List all skills that were loaded during this planning session
- Use the planner agent's model (sonnet) for agent overhead
- Display the formatted report