fix: incorrect tree structure in examples

[adam-paterson]

Important

Really critical update.

Once this step is completed, you should have a new branch created (e.g., 001-create-taskify), as well as a new specification in the specs/001-create-taskify directory.

spec-kit/README.md

Lines 192 to 211 in b4833cb

	Once this step is completed, you should have a new branch created (e.g., `001-create-taskify`), as well as a new specification in the `specs/001-create-taskify` directory.
	The produced specification should contain a set of user stories and functional requirements, as defined in the template.
	At this stage, your project folder contents should resemble the following:
	```text
	├── memory
	│ ├── constitution.md
	│ └── constitution_update_checklist.md
	├── scripts
	│ ├── check-task-prerequisites.sh
	│ ├── common.sh
	│ ├── create-new-feature.sh
	│ ├── get-feature-paths.sh
	│ ├── setup-plan.sh
	│ └── update-claude-md.sh
	├── specs
	│ └── 002-create-taskify
	│ └── spec.md

[Copilot]

Pull Request Overview

This PR fixes incorrect directory naming in the README documentation examples. The examples were showing 002-create-taskify instead of the correct 001-create-taskify directory name, which caused confusion for users following the documentation.

• Updates directory tree examples to use the correct spec directory naming convention
• Ensures consistency between the description text and the visual examples

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[shajebi]

✅ Participants enforcement implemented and documented comprehensively.

Implementation verified:

• 6 critical commands updated with participants support
• Shared reference pattern ensures consistency
• Graceful error handling with warn-and-continue
• Comprehensive documentation in README, handbook, and persona reference

Design decisions confirmed:

• /gbm.tasks deferred (inherits from plan.md)
• Warn-only for missing personas (intentional graceful degradation)

Ready to merge!