Agent skill
plan-address-feedback
Address design review feedback and revise the implementation plan
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/plan-address-feedback
SKILL.md
Plan Address Feedback
Uses Planner. Parse reviewer feedback on an implementation plan, revise the plan document, and verify the revision passes the Plan Quality Contract before re-review.
Prerequisites: Review feedback available (in conversation or linked issue comment), plan document path known
Phase 1: Parse Feedback
Categorize All Feedback Items
- Read the complete review feedback
- Identify the plan document being revised (path in
docs/notes/) - Categorize each item:
| Category | Definition | Action |
|---|---|---|
| Blocking | Must be resolved before plan can be approved | Address now |
| Suggestion | Would improve the plan but not blocking | Consider |
| Nitpick | Minor clarity improvement | Optional |
- List all blocking items explicitly before proceeding
⛔ CHECKPOINT
STOP. Confirm understanding of blocking items before revising:
- List each blocking issue and the proposed resolution
- If any blocking issue is unclear, ask for clarification before editing
Phase 2: Determine Revisions
For Each Blocking Issue
- Identify which section of the plan the issue affects
- Determine what specifically needs to change:
- Missing content to add
- Vague content to specify
- Incorrect content to replace
- Note the exact file path and section name
Phase 3: Revise the Plan
Update the Plan Document
- Open the plan in
docs/notes/ - Address each blocking item in order
- Address suggestions where they improve clarity without scope creep
- Preserve all content not identified as problematic
Phase 4: Verify Against Plan Quality Contract
Re-check All Criteria
After revision, verify the plan now satisfies:
- Problem statement present
- Constraints listed
- Scope explicitly defined with file paths
- Ordered steps numbered, specific, actionable
- AC mapping — each AC traced to steps
- Verification steps — each step verifiable
- Open assumptions listed explicitly
- No vague verbs without specifics
- No files referenced without paths
- No ambiguous choices left for the Implementer
Phase 5: Present for Re-Review
Output
## Context Anchors
- **Issue:** #<number> - <title>
- **Plan:** <docs/notes/path>
- **Phase:** Plan Revision
## Feedback Addressed
### Blocking Issues Resolved
1. **<Issue>** — <how it was resolved>
2. **<Issue>** — <how it was resolved>
### Suggestions Incorporated
- <suggestion and what changed>
### Suggestions Deferred
- <suggestion and why deferred>
## Plan Quality Contract
- [x] Problem statement present
- [x] Constraints listed
- [x] Scope specified with file paths
- [x] Steps numbered and actionable
- [x] AC mapping complete
- [x] Verification steps included
- [x] Open assumptions listed
## Next Step
Request re-review of the revised plan.
**Approval Required:** Yes
⛔ CHECKPOINT
STOP. Before presenting the revised plan for re-review:
- Confirm all blocking items from the original review are resolved
- Confirm Plan Quality Contract checklist passes
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?