Virtual Team Init

Present detection results to user for confirmation via AskUserQuestion:

• Detected language: {lang}
• Detected framework(s): {frameworks}
• "Is this correct?"

Step 2: Basic Info

Ask via AskUserQuestion:

1. Project name — suggest dirname as default
2. Project path — suggest current directory as default, must be absolute path

Step 3: Architecture Pattern

Based on detected language and directory structure, suggest the most likely pattern. Ask via AskUserQuestion with options:

Step 4: Commands

Based on detected language, suggest default commands. Ask user to confirm or override:

Command Suggestions by Language

Command Allowlist

Validate commands match these allowed prefixes:

• JS/TS: npm run, npx, pnpm, yarn, bun, make, node, tsx
• Python: pytest, python, pip, poetry, pdm, ruff, mypy, black, isort, make
• Go: go, make, golangci-lint
• Rust: cargo, make, rustfmt, clippy
• Java/Kotlin: mvn, gradle, gradlew, make, java
• Ruby: bundle, rake, ruby, make
• C#/.NET: dotnet, make, nuget
• General: make, docker compose

If user enters a command not matching allowlist, warn and ask to confirm.

Step 5: Modules

Based on architecture pattern from Step 3, present the matching module structure. Ask user to fill in actual paths:

Module Templates

web-fullstack:

- frontend: {src/components/..., src/pages/...}
- backend: {server/..., api/...}
- shared: {shared/..., types/...}

backend-api:

- api: {routes/..., controllers/...}
- service: {services/..., domain/...}
- data: {models/..., repositories/...}
- shared: {utils/..., config/...}

cli-library:

- lib: {src/..., lib/...}
- cli: {bin/..., cmd/...}
- shared: {internal/..., utils/...}

monolith:

- app: {src/..., app/...}
- config: {config/...}
- shared: {utils/..., helpers/...}

ddd-layered:

- domain: {domain/..., entities/..., value-objects/...}
- application: {application/..., use-cases/..., services/...}
- infrastructure: {infrastructure/..., repositories/..., adapters/...}
- interface: {interface/..., controllers/..., api/...}
- shared: {shared/..., common/...}

Use Glob to scan actual directory structure and suggest real paths where possible.

Step 6: Requirements & Acceptance Criteria

Ask via AskUserQuestion:

1. Requirement description — "Please describe what you want to build (the more detail the better)"
2. Acceptance criteria — "List testable conditions (one per line, will become checklist items)"

Step 7: Constraints & Optional Sections

Ask via AskUserQuestion (all optional, user can skip):

1. Constraints — "Any files/modules that must NOT be modified?"
2. Forbidden operations — "Any operations to explicitly prohibit? (e.g., don't modify lock files)"
3. Coverage requirements — "Unit test coverage target? (e.g., 60%)"
4. Reference documents — "Any design docs or references to include?"

Step 8: Generate Document

Assemble the requirement document using this format:

# 需求文档

## 基本信息
- 项目名称: {from Step 2}
- 项目路径: {from Step 2}
- 语言/框架: {from Step 1}
- 架构模式: {from Step 3}
- 测试框架: {from Step 4}
- 构建命令: {from Step 4}
- 测试命令: {from Step 4}
- Lint 命令: {from Step 4}

## 需求描述
{from Step 6}

## 涉及模块
{from Step 5, formatted as module list}

## 验收标准
{from Step 6, each item as - [ ] checklist}

## 约束与注意事项
{from Step 7, or "无" if skipped}

## 禁止操作
{from Step 7, or "无" if skipped}

## 覆盖率要求
{from Step 7, or "默认" if skipped}

## 参考资料
{from Step 7, or "无" if skipped}

Write the document to the output path (from Arguments, default ./requirement.md).

Show the user the generated file path and suggest:

/virtual-team {output-path} --interactive

Guidelines

• Always use AskUserQuestion for user input — never assume
• Suggest sensible defaults based on auto-detection, but let user override everything
• If a marker file is not found, ask user to manually specify language and framework
• Keep the conversation concise — don't over-explain, just ask the questions
• Validate the output path is writable before generating
• If the user's working directory has no recognizable project markers, skip auto-detection and ask everything manually