Best use case
openup-create-iteration-plan is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Plan iteration based on current state and roadmap
Teams using openup-create-iteration-plan should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/openup-create-iteration-plan/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How openup-create-iteration-plan Compares
| Feature / Agent | openup-create-iteration-plan | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Plan iteration based on current state and roadmap
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create Iteration Plan This skill generates an iteration plan from the OpenUP template. ## When to Use Use this skill when: - Starting a new iteration and need to plan work - In Construction phase planning iterations - Need to select tasks from roadmap for iteration - Assigning tasks to team members - Defining iteration success criteria ## When NOT to Use Do NOT use this skill when: - Looking to start iteration (use `/openup-start-iteration`) - Need to create roadmap (use project management) - Iteration plan exists and only minor updates needed (edit directly) - In Inception phase (use phase activities instead) ## Success Criteria After using this skill, verify: - [ ] Iteration plan file exists - [ ] Iteration goal is clearly defined - [ ] Tasks are selected from roadmap - [ ] Task assignments are made - [ ] Success criteria are specified ## Process ### Load Project Config (context + rules — do this first) Before drafting, layer in project-owned context and rules so the artifact reflects facts and standards the framework can't infer. Full mechanism + precedence: `docs-eng-process/project-config.md`. 1. If `docs/project-config.yaml` exists, read it. If it is **absent, skip this step** — framework defaults apply unchanged. 2. Inject `context:` into your working prompt wrapped in `<project-context>…</project-context>`, and `rules.<TYPE>` (if present) wrapped in `<project-rules>…</project-rules>`. For this skill `<TYPE>` is **`iteration-plan`**. 3. Project rules are **additive** to the framework rubric — precedence is **framework rubric → project rules → task-spec safeguards**. A project rule may add a criterion but may **not** waive a framework rubric criterion or a safeguard. 4. Before marking this artifact complete, confirm every injected `<project-rules>` item is satisfied alongside the framework rubric. ### 1. Read Project Status Read `docs/project-status.md` to get: - Current phase - Current iteration - Iteration goals ### 2. Read Roadmap Read `docs/roadmap.md` to identify: - Pending tasks appropriate for this iteration - Task priorities and dependencies ### 3. Determine Iteration Number Use `$ARGUMENTS[iteration_number]` or auto-increment from current iteration. ### 4. Copy Template Copy `docs-eng-process/templates/iteration-plan.md` to `docs/phases/<phase>/iteration-<n>-plan.md` ### 5. Fill in Iteration Plan Update with: - **Iteration number** and dates - **Iteration goal**: Derived from roadmap and phase objectives - **Selected tasks**: From roadmap, prioritized for this iteration - **Task assignments**: Which roles will handle each task - **Success criteria**: How to know the iteration succeeded - **Risk assessment**: Any iteration-specific risks ### 6. Validate Completeness Ensure the iteration plan includes: - Clear iteration goal - List of tasks to complete - Task assignments - Success criteria - Iteration timeline ## Output Returns: - Path to iteration plan - List of tasks planned - Recommended team composition ## Common Errors | Error | Cause | Solution | |-------|-------|----------| | Template not found | Template path incorrect | Verify `docs-eng-process/templates/iteration-plan.md` exists | | No tasks available | Roadmap is empty or all tasks complete | Review roadmap and add pending tasks | | Invalid iteration number | Iteration number conflicts or gaps | Verify current iteration from project-status | ## References - Iteration Plan Template: `docs-eng-process/templates/iteration-plan.md` - Project Manager Role: `docs-eng-process/openup-knowledge-base/core/role/roles/project-manager-4.md` ## See Also - [openup-start-iteration](../../openup-workflow/start-iteration/SKILL.md) - Begin new iteration - [openup-complete-task](../../openup-workflow/complete-task/SKILL.md) - Mark iteration tasks complete - [openup-construction](../../openup-phases/construction/SKILL.md) - Construction iteration planning
Related Skills
openup-transition
Initialize and manage Transition phase activities - deploy to users
openup-tdd-workflow
Guide Test-Driven Development cycle adapted for AI agents with a pragmatic approach
openup-sync-spec
Back-propagate pure refactors to stale artifacts; classify the diff, refuse behaviour-changes, propose targeted edits for approval (read-only by default)
openup-start-iteration
Begin a new OpenUP iteration with proper phase context and task selection
openup-shared-vision
Create shared technical vision for team alignment
openup-retrospective
Generate iteration retrospective with feedback and action items
openup-request-input
Create an input request document for asynchronous stakeholder communication
openup-readiness
Compute the change-folder dependency DAG and print READY/BLOCKED/collision report for PM intake
openup-quick-task
Fast iteration mode for small changes - simplified workflow with minimal overhead
openup-plan-feature
Generate iteration plan and roadmap entry for a feature idea
openup-phase-review
Check phase completion criteria and prepare for phase review
openup-orchestrate
Run a full orchestrated iteration — PM decomposes the goal, delegates to specialist roles, collects outputs, and synthesizes results