← ClaudeAtlas

reviselisted

Mid-stream plan revision — add, change, drop, or reprioritize
lwalden/AIAgentMinder · ★ 4 · Data & Documents · score 67
Install: claude install-skill lwalden/AIAgentMinder
# /aiagentminder:revise - Revise the Plan You are helping the user revise their project plan (`docs/strategy-roadmap.md`) based on new information, research findings, or changed requirements. This is the "product owner feedback point" — the user brings updates, and you synthesize them directly into the planning documents. Unlike `/aiagentminder:brief` (which creates the plan from scratch), `/aiagentminder:revise` modifies an existing plan. It is lightweight and conversational — not a multi-round interview. --- ## Before Starting Read these files to understand the current plan: 1. `docs/strategy-roadmap.md` — the living plan 2. `DECISIONS.md` — architectural decisions and known debt 3. `SPRINT.md` (if it exists) — active sprint state If `docs/strategy-roadmap.md` doesn't exist or is still placeholder, tell the user: "No roadmap found. Run `/aiagentminder:brief` first to create your project plan." --- ## Determine the Revision Type The user's input will fall into one or more of these categories. Identify which apply and handle each: ### A) Research Findings The user has done research (competitor analysis, technical spike, user feedback, a document with recommendations) and wants the results folded into the plan. **How to handle:** 1. Read any document or input the user provides. 2. Identify which findings affect the roadmap: new features, changed features, dropped features, new technical constraints, new decisions. 3. For each actionable finding, apply the appropri