Replace the term 'spec' with 'requirement'

[navygao-tech]

I'd like to change 'spec' to 'requirement' because 'spec' is often misunderstood as including design, testing, and tasks, which leads to confusion

Let's use 'requirement' instead of 'spec'—'spec' tends to imply design, testing, and tasks, which is misleading

[navygao-tech]

 ✓ proposal.md — why we're doing this, what's changing
 ✓ **specs/**       — requirements and scenarios
 ✓ design.md    — technical approach
 ✓ tasks.md     — implementation checklist

[sourav7274]

Hi, I’m interested in picking up the task to rename 'spec' to 'requirement' throughout the project. I would like to have some clarifications before starting this.

I’ve noticed that 'spec' is used extensively in directory names, CLI commands, and internal logic. I'm concerned about how this might break existing projects that have nested folders within specs/.

Should I make changes when these files are generated: -

• proposal.md
• design.md
• tasks.md
• specs/

or whole codebase