Initialize spec-kit in existing project root instead of creating nested directory

[hashimwarren]

When initializing spec-kit within an existing project directory, the tool creates a nested folder structure. I was expecting it to create files at the root of my existing project.

Running the initialization command within an existing project creates:

my-existing-project/
├── existing-files...
└── [project-name]/
    ├── .github/
    │   └── prompts/
    │       ├── plan.prompt.md
    │       ├── specify.prompt.md
    │       └── tasks.prompt.md
    ├── memory/
    └── scripts/

Expected Behavior

The initialization should respect the existing project structure and place spec-kit files in the current directory:

my-existing-project/
├── existing-files...
├── .github/
│   └── prompts/
│       ├── plan.prompt.md
│       ├── specify.prompt.md
│       └── tasks.prompt.md
├── memory/
└── scripts/

Proposed Solution

Consider adding a command-line flag such as:

• --in-place or --current-dir to initialize in the current directory
• --no-nested to prevent nested directory creation
• Or make this the default behavior when run in a directory that already contains project files

[jameshopkins]

--here is an existing flag for this