Update Implementation Plan

An AI skill that revises and updates existing implementation plans based on new information, completed work, discovered challenges, and changed requirements, keeping project plans accurate and actionable throughout the development lifecycle.

What Is This?

Overview

This skill takes an existing implementation plan and updates it based on current project state. It marks completed tasks, adjusts estimates, incorporates new requirements, re-sequences work around blockers, and adds tasks for issues found during implementation. The updated plan reflects reality rather than original assumptions.

Who Should Use This

Ideal for tech leads maintaining living project plans, scrum masters updating sprint backlogs, and developers who need to adjust their implementation approach based on what they learned during initial coding. Useful for any team that treats plans as evolving documents.

Why Use It?

Problems It Solves

Implementation plans become stale within days of creation. Tasks take longer than expected, new dependencies emerge, requirements change, and technical discoveries reshape the approach. Teams either abandon their plans entirely or spend excessive time manually updating them. Stale plans mislead stakeholders and cause coordination failures.

Core Highlights

• Progress Integration marks completed work and adjusts remaining estimates
• Blocker Management re-sequences tasks around discovered blockers
• Scope Updates incorporates new requirements without losing existing context
• Risk Reassessment updates risk levels based on implementation experience
• Dependency Tracking adjusts task ordering when prerequisites change

How to Use It?

Basic Usage

Provide the current plan and update information, and receive a revised plan.

## Updated Implementation Plan:

Auth System

### Phase 1:

Database Schema [COMPLETED]
- Created users table with all required fields
- Added sessions table (was not in original plan)
- Migration tested in staging

### Phase 2:

Auth Endpoints [IN PROGRESS]
- Login endpoint: complete
- Register endpoint: complete
- Password reset: blocked (email service not configured)
- [NEW] Added MFA endpoint (requirement added by security team)

### Phase 3:

Frontend Integration [REVISED]
- Original estimate: 3 days -> Revised: 5 days
- Reason: MFA flow adds complexity to login UI

Real-World Examples

Mid-Sprint Plan Revision

A team was three days into implementing a payment integration when they discovered that the third party API had rate limits not mentioned in the documentation. The skill updated their plan to include a caching layer, re-estimated the remaining work, and shifted the launch date accordingly.

updates:
  - task: "Integrate payment API"
    status: in_progress
    blocker: "API rate limited to 100 req/min"
    
  - task: "Add response caching layer"
    status: new
    priority: high
    reason: "Required to stay within API rate limits"
    estimate: "2 days"

  - task: "Load testing"
    status: revised
    note: "Must validate cache hit rates under expected traffic"

impact:
  original_completion: "2025-03-10"
  revised_completion: "2025-03-13"
  reason: "Caching layer and additional testing needed"

Advanced Tips

Update plans at natural checkpoints like the end of each phase or sprint boundary. Include the reason for every change so the team understands what drove the revision. Archive previous plan versions to track how estimates evolved over time.

When to Use It?

Use Cases

• Sprint Adjustments update plans based on actual velocity and discoveries
• Requirement Changes incorporate new or modified requirements mid-project
• Blocker Resolution re-sequence work when tasks become blocked
• Stakeholder Updates produce accurate progress reports from living plans
• Retrospective Input compare original and final plans to improve estimation

Related Topics

When updating implementation plans, these prompts activate the skill:

• "Update my implementation plan with current progress"
• "Revise the plan based on what we learned"
• "Add new tasks and adjust the timeline"
• "Mark completed items and re-estimate remaining work"

Important Notes

Requirements

• An existing implementation plan in any structured format
• Current status information for completed and in-progress tasks
• Description of any new requirements, blockers, or discoveries
• Works with markdown, YAML, or JSON plan formats

Usage Recommendations

Do:

• Update plans regularly at defined checkpoints rather than sporadically
• Document reasons for changes so the team understands what shifted
• Keep stakeholders informed when updates affect timelines or scope
• Archive previous versions to improve future estimation accuracy

Don't:

• Delay updates until the plan is completely irrelevant
• Remove completed context as it helps team members understand progress
• Change estimates without explanation since transparency builds trust
• Treat updated plans as commitments without team review and agreement

Limitations

• Cannot predict future blockers or requirement changes not yet known
• Estimate adjustments are based on reported information and may still be inaccurate
• Very large plans with hundreds of tasks may need manual prioritization guidance
• Cannot resolve conflicting updates from multiple team members automatically