メニュー
AI-powered sprint planning, velocity analysis, and capacity forecasting. Use for planning sprints, predicting outcomes, and providing agile recommendations based on historical data.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Integration between Git workflows and Jira issues. Generates branch names from issues, validates commit messages, and provides PR context from Jira specifications.
Git repository operations including branching, committing, pushing, and viewing history. Use for version control tasks. Destructive operations require explicit approval.
Read data from Jira including issues, comments, sprints, and execute JQL queries. Use when you need to fetch or search Jira data without making changes.
Create and update Jira issues, add comments, transition statuses, and manage sprints. Use when you need to make changes to Jira data. Supports dry-run mode for validation.
Coordinate multi-step workflows across skills with execution plans, state tracking, and rollback support. Use when tasks require multiple coordinated operations.
Create and manage GitHub Pull Requests with templates, reviewers, and labels. Use when code is ready for review. Merging requires explicit approval.
| name | devflow-planning |
| description | AI-powered sprint planning, velocity analysis, and capacity forecasting. Use for planning sprints, predicting outcomes, and providing agile recommendations based on historical data. |
| license | MIT |
| compatibility | Requires mcp-jira with configured Jira instance |
| metadata | {"author":"ximplicity","version":"1.0","category":"planning"} |
Sprint planning, velocity analysis, and predictive analytics for agile teams.
These require explicit user approval:
1. Analyze velocity → Get historical data
2. Calculate capacity → Team availability
3. Recommend load → Based on trends
4. Assess risks → Per-issue spillover
5. Validate plan → Sprint success prediction
| Metric | Description | Use For |
|---|---|---|
| Avg Velocity | Points completed per sprint | Baseline planning |
| Trend Direction | Increasing/Stable/Decreasing | Adjust forecasts |
| Completion Rate | Done vs Committed ratio | Risk assessment |
| Variance | Sprint-to-sprint deviation | Confidence levels |
For complete velocity patterns, see VELOCITY-PATTERNS.md.
Team Capacity = Sum(member availability × sprint days)
Recommended Load = Avg Velocity × (1 - Buffer%)
Buffer Guidelines:
- Stable team: 10%
- New members: 20%
- High uncertainty: 30%
For sprint planning details, see SPRINT-PLANNING-GUIDE.md.
| Context | Trigger | Action |
|---|---|---|
| Sprint >80% filled | Overcommit risk | Suggest scope reduction |
| Velocity declining 3+ sprints | Trend alert | Recommend retrospective focus |
| Issue blocked >2 days | Dependency risk | Escalate blocker |
| Unestimated work in sprint | Planning gap | Flag for refinement |
| Branch stale >5 days | GitFlow alert | Review or close |
When planning work:
developfeature/<issue-key>-<description>For GitFlow details, see GITFLOW-RECOMMENDATIONS.md.
For Scrum patterns, see SCRUM-BEST-PRACTICES.md.
Analyze velocity for project PROJ over last 5 sprints
Plan next sprint with 80% capacity buffer
Show spillover risks for current sprint items
Predict success rate for proposed sprint scope
Map dependencies between PROJ and INFRA projects