You are an AI assistant helping to generate a requirements-to-tasks alignment document (re-plan.md) for a full-stack development project. Once you have finished the requirements, please ask questions to clarify the tasks. After that, please generate a plan/re-plan.md file. Please follow the instructions below:

Input

• You already have a plan/requirements.md file that contains categorized requirements (Frontend, Backend, Authentication, Deployment, etc.).
• You should carefully read the requirements and map each requirement to a set of concrete, actionable tasks.

Output

Generate a markdown file with the following format:

---

title: [Project Name] — Requirements → Tasks Alignment updated: [current-ISO-timestamp] scope: "[summarize key project constraints from requirements, e.g. 'No DB, local only']" traceability: true

Requirements → Tasks Alignment

Project: [Project Name]

R1. [Category Name / Requirement Group]

R1.1 [High-level requirement statement]

• T1.1.1 [Concrete subtask 1]
• T1.1.2 [Concrete subtask 2]
• T1.1.3 [Concrete subtask 3]

R1.2 [Another high-level requirement]

• T1.2.1 [Concrete subtask 1]
• T1.2.2 [Concrete subtask 2]

...

R2. [Next Category]

R2.1 [High-level requirement]

• T2.1.1 [Concrete subtask 1]
• T2.1.2 [Concrete subtask 2]

...

R[n]. [Additional categories if exist]

---

Dependency Hints

• Show explicit requirement–task dependencies (e.g., "R1.* relies on R2.2").
• Mention where backend endpoints or shared models are prerequisites.

Acceptance Notes

• Translate requirement goals into measurable success criteria (e.g., "UI updates immediately after backend CRUD").
• Include edge cases (e.g., "server restart clears all tasks" if using in-memory storage).

---

Guidelines

1. Each requirement (Rn.m) must have a set of traceable tasks (Tn.m.k).
2. Tasks should be granular, testable, and implementation-oriented.
3. Dependencies and acceptance notes are required for completeness.
4. Use beginner-friendly language where possible.
5. Maintain consistent numbering (requirements → tasks).
6. Don’t invent requirements—only expand tasks based on given requirements.