feat: add structured requirements analysis step before task generation

[ChaizMaster]

What

Adds a structured requirements analysis phase (Step 2) that runs before parent task generation.

Why

Task lists occasionally had:

• Misordered tasks (dependencies not respected)
• Gaps in coverage against PRD requirements

How

The AI now explicitly:

1. Enumerates technical components (schema, API, UI, state, tests)
2. Validates dependency order between components
3. Checks that all PRD functional requirements map to planned work

This reasoning informs task structure but stays out of the final markdown.

[olitech1010]

I think the ai should save Schema, API and UI doc as md files for future references.

This is what I usually do. In that case. Switching between models does not affect the project no matter how different the models thinking is. They all follow the same rules.

EspeciallyUI doc.

[ChaizMaster]

This addition forces the AI to adapt AOT instead of COT, which has proven beneficial for me personally. Because you're giving explicit sub-steps rather than a vague "analyze." The concrete examples (schema, API, UI) and the dependency framing will nudge the model toward more systematic thinking.

[olitech1010]

Looks good.
The structured analysis step improves task quality and dependency ordering.
My earlier suggestion about persisting Schema/API/UI docs can be handled in a follow-up PR.

[olitech1010]

This update improves the Analyze Requirements step by adding clarity and rigor to the task-creation process. Listing technical components, mapping dependencies, and verifying PRD coverage ensures better task alignment and reduces omissions.

[victorjquinones]

@copilot review