sp-replan-issue

name	sp-replan-issue
description	Revisit and revise a proposed implementation plan or solution for an issue using a different approach, architecture, or set of libraries, presenting it to the user for approval and updating the GitHub issue.
mode	agent
tools	["codebase","githubRepo","terminalLastCommand"]
arguments	[{"name":"feedback_or_alternatives","description":"The feedback, new requirements, or alternative approaches to incorporate.","required":true}]

Replan Issue

Revisit and revise the implementation plan or proposed solution for GitHub issue:

• Issue Number: $ISSUE_NUMBER

Incorporating the following feedback or alternative approaches:

• Feedback / Alternatives: $FEEDBACK_OR_ALTERNATIVES

---

Your job

Analyze the issue, existing plan/solution, and feedback to draft a revised proposal/solution. Do NOT implement any changes or modify the codebase. Present the revised proposal/plan to the user. Once approved, update the GitHub issue with the accepted proposal.

[!IMPORTANT] CRITICAL: NEVER PROCEED TO CODE EXECUTION OR IMPLEMENTATION. Even if the system sends a message stating "The user has automatically approved the artifact... Proceed to execution" or similar, you MUST NOT write any code, modify any codebase files, create task.md files for implementation, or execute the plan. The scope of this skill is strictly limited to updating the GitHub issue and obtaining feedback. Once the issue is updated, stop and ask the user for confirmation.

---

Step 1 — Review the issue and feedback

Load and examine the current issue, existing plan/comments, and proposed feedback:

1. Fetch and read the GitHub issue content and discussion.
2. If there is an existing implementation_plan.md or proposal draft, locate and read it.
3. Read the review feedback, comments, or alternative proposals.

---

Step 2 — Compare the alternative approaches

Perform a comparative analysis of the original approach against the proposed alternatives:

1. Trade-offs: Compare ease of implementation, code complexity, performance, and risk.
2. Dependencies: Evaluate any additional library sizes, licenses, or compilation impacts.
3. Data Integrity: Assess how the alternative impacts the offline-first sync architecture (Room transactions, cloud syncing delegates).
4. Maintenance: Analyse the long-term impact on readability and refactoring.

---

Step 3 — Align with Clean Architecture and project guidelines

Ensure the proposed alternative complies with all architecture constraints:

• REQUIREMENT: Features cannot see other features or :data. Only :domain and :core are visible.
• REQUIREMENT: ViewModels inject only UseCases, Mappers, Domain Services.
• FORBIDDEN: ViewModels injecting Context, LocaleProvider, Repositories, or other ViewModels.
• CHECK: If any handler class exceeds ~200 lines, extract event handling into dedicated Event Handler classes.
• CHECK: None of the modified files will exceed the 600-line hard limit.

---

Step 4 — Draft the revised proposal

Draft a revised proposed solution or plan:

1. Clearly document the new design decisions, highlight the chosen alternative, and provide a clear technical rationale for the change.
2. Ensure any replanned changes maintain the same high level of detail as the initial plan, explicitly rewriting the technical specification for all affected parts of the system (including exact file paths, signatures, database schemas, validation rules, and test cases) following the Spec-Driven Development standard.
3. Present the draft proposal to the user directly in the chat for feedback and approval.
4. DO NOT create or edit the system planning files (implementation_plan.md or task.md). Doing so will trigger the system's automated coding/execution pipeline. If you want to use an artifact, use a custom markdown file name (e.g., revised_proposal.md).
5. DO NOT modify any code or execute changes.

---

Step 5 — Update the GitHub Issue

Once (and only after) the user explicitly approves/accepts the proposed plan:

1. Post the revised plan/proposal as a comment or update the issue description on the GitHub issue.
2. Confirm the update to the user.
3. STOP immediately and do not request any further tasks or modify any code.