Initialization

•
Track Progress
- •Use the TodoWrite tool to create a task list for all phases of this workflow.
- •Update the status of tasks as you complete each phase.

Phase 1: Environment Discovery

Goal: Understand the user's technology stack by detecting installed languages, tools, and package managers.

Actions:

•
Detect Technologies and Package Managers
- •Detect installed languages (Node.js, Python, Rust, Go, Java, Docker, etc.)
- •For languages with multiple package managers, detect all available options
- •Store detected information for later selection

Goal: Collect developer name and email for personalized configuration.

Actions: Ask for developer name and email using AskUserQuestion with 2 questions:

•
Question 1: "What is your name?"
- •Header: "Developer"
- •Option: {"label": "Skip name", "description": "Don't include name in configuration"}
- •Note: User inputs custom name via automatic "Other" option (no additional placeholder needed)
•
Question 2: "What is your email address?"
- •Header: "Contact"
- •Option: {"label": "Skip email", "description": "Don't include email in configuration"}
- •Note: User inputs custom email via automatic "Other" option (no additional placeholder needed)

Important: Only provide the "Skip" option. The "Other" option is automatically provided for direct text input.

Goal: Determine if Test-Driven Development requirements should be included in the configuration.

Actions: Ask if TDD should be included using AskUserQuestion:

•Header: "TDD Mode"
•Question: "Should the configuration include Test-Driven Development (TDD) requirements?"
•
Options:
- •{"label": "Include TDD (Recommended)", "description": "Add mandatory TDD workflow"}
- •{"label": "Exclude TDD", "description": "Generate without TDD requirements"}

Store the user's choice (true/false) for use in Phase 7.

Goal: Select technology stacks and preferred package managers for each language.

Actions:

Goal: Optionally search for and append latest 2026 best practices for selected technologies.

Actions: Ask if web search should be performed using AskUserQuestion:

•Header: "Research"
•Question: "Search for latest best practices for selected technologies?"
•
Options:
- •{"label": "Search and append (Recommended)", "description": "Find 2026 best practices"}
- •{"label": "Skip search", "description": "Use only base template"}

If enabled, search and extract 2-3 key sentences for each technology:

•Plain text only: Extract descriptive sentences about best practices
•No code snippets: Exclude bash commands, code examples, or command-line instructions
•No URLs: Remove all links and references to external resources
•Format as simple, readable paragraphs or bullet points

Goal: Determine emoji usage preference for the generated configuration.

Actions: Ask emoji preference using AskUserQuestion:

•Header: "Style"
•Question: "Should emojis be used in the configuration files?"
•
Options:
- •{"label": "No Emojis (Recommended)", "description": "Professional, text-only formatting"}
- •{"label": "Use Emojis", "description": "Add visual indicators using emojis"}

Goal: Assemble final configuration content from template fragments, developer profile, and technology sections.

Actions:

•
Assemble template using script:
- •Run: ${CLAUDE_PLUGIN_ROOT}/scripts/assemble-template.sh "${CLAUDE_PLUGIN_ROOT}/assets/claude-template-no-tdd.md" "<tdd_choice>" "<temp_output_file>" "${CLAUDE_PLUGIN_ROOT}"
- •Where <tdd_choice> is "true" if TDD was selected in Phase 3, "false" otherwise
- •Use a temporary file for the assembled template

•

Prepare Developer Profile Section

markdown

## Developer Profile
- **Name**: [User's Name or "Developer"]
- **Email**: [User's Email or omit if skipped]

•
Generate Tech Stack Sections
- •Generate configuration for each selected technology
- •Use selected package managers in all examples
- •Apply emoji preference
- •Append web search summaries if enabled
•
Assemble Final Content
- •Read the assembled template from step 1
- •Combine: header + developer profile + assembled template + tech stack sections

Goal: Validate that the generated configuration meets optimal length requirements (1,500-3,000 words).

Actions:

•
Validate content length
- •Write assembled content to a temporary file
- •Run validation script: ${CLAUDE_PLUGIN_ROOT}/scripts/validate-length.sh
•
Handle results:
- •ACCEPTABLE/OPTIMAL: Proceed to Phase 9
- •
  TOO_LONG/EXCESSIVE: Ask user via AskUserQuestion:
  - •Header: "Length"
  - •Question: "Configuration exceeds best practice length. How to proceed?"
  - •Options: Auto-trim / Keep as-is / Manual review
- •TOO_SHORT: Show info and proceed

Goal: Write the final configuration to the user's home directory with comprehensive summary reporting.

Actions: