docs: fix directory hierarchy in README examples

[hot666666]

Description

In the README.md (specifically under "📋 Detailed Process" Step 2: Create project specifications and Step 4: Generate a plan), the directory tree diagrams show the specs/ directory nested under .specify/:

.specify/
├── memory/
├── scripts/
├── specs/
│   └── 001-my-first-feature/
└── templates/

However, in actual project initialization, the specs/ directory is created at the project root level, and .specify/ contains memory/, scripts/, and templates/:

.
├── .specify/
│   ├── memory/
│   ├── scripts/
│   └── templates/
└── specs/
    └── 001-my-first-feature/

Testing

• Tested locally with uv run specify --help
• Ran existing tests with uv sync && uv run pytest
• Tested with a sample project (if applicable)

AI Disclosure

• I did not use AI assistance for this contribution
• I did use AI assistance (describe below)

Used Gemini for hierarchy visualization.

[Copilot]

Pull request overview

Fixes the README’s “📋 Detailed Process” directory tree examples to reflect the actual project layout created by spec-kit, specifically that specs/ is created at the repository root (not nested under .specify/).

Changes:

• Update Step 2 example tree to show .specify/ and specs/ as siblings at the repo root.
• Update Step 4 example tree similarly, keeping generated spec artifacts under specs/<feature>/.

Show a summary per file

File	Description
README.md	Corrects the documented directory hierarchy so specs/ is shown at the project root instead of under .specify/.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 2