Struct AnalyzeProjectArgs 

pub struct AnalyzeProjectArgs {
    pub project_name: String,
    pub vision: String,
    pub tech_stack: String,
    pub summary: String,
}

Arguments for analyze_project command

Fields

project_name: String

Project name to create with your analyzed content

Must be in kebab-case format (lowercase letters, numbers, hyphens only) Cannot contain spaces, underscores, or special characters

vision: String

High-level product vision content (2-4 paragraphs, 200+ characters) based on your codebase analysis

Analysis Approach:

• Use Search, Grep, and Read tools to explore the codebase first
• Examine package.json, README files, main entry points, API routes
• Look for user-facing features, business logic, and data models
• Review existing documentation and configuration files

Content Structure & Markdown:

• Use ## headers (## Problem Analysis, ## Target Users, ## Product Goals)
• Base vision on actual code functionality discovered
• Include specific examples from the codebase
• Structure with bullet points and clear paragraphs
• Write in present tense, referencing actual implementation

Goes into vision.md

tech_stack: String

Technology stack and architecture decisions (150+ characters) based on your codebase exploration

Detection Strategy:

• Analyze package.json, requirements.txt, Cargo.toml, etc. for dependencies
• Check build scripts, Docker files, and deployment configurations
• Examine database connections, API integrations, and external services
• Review folder structure and architectural patterns used

Content Structure & Markdown:

• Use ## headers (## Languages, ## Frameworks, ## Database, ## Deployment, ## Build Tools)
• List detected technologies with versions where found
• Include rationale based on code patterns observed
• Add ### subsections for complex architectural decisions
• Reference specific files or configurations discovered

Goes into tech-stack.md

summary: String

Concise summary (100+ characters) combining vision and tech stack from your analysis

Should capture key insights from your codebase exploration for quick context loading Use this to understand the project essence before diving into implementation Goes into summary.md

Trait Implementations

impl Args for AnalyzeProjectArgs

fn group_id() -> Option<Id>

Report the ArgGroup::id for this set of arguments

fn augment_args<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate Self via FromArgMatches::from_arg_matches_mut

fn augment_args_for_update<'b>(__clap_app: Command) -> Command

Append to Command so it can instantiate self via FromArgMatches::update_from_arg_matches_mut

impl Debug for AnalyzeProjectArgs

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl FromArgMatches for AnalyzeProjectArgs

fn from_arg_matches(__clap_arg_matches: &ArgMatches) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn from_arg_matches_mut( __clap_arg_matches: &mut ArgMatches, ) -> Result<Self, Error>

Instantiate Self from ArgMatches, parsing the arguments as needed.

fn update_from_arg_matches( &mut self, __clap_arg_matches: &ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

fn update_from_arg_matches_mut( &mut self, __clap_arg_matches: &mut ArgMatches, ) -> Result<(), Error>

Assign values from ArgMatches to self.

impl McpToolDefinition for AnalyzeProjectArgs

fn tool_definition() -> Tool

Generate the MCP tool definition from the struct

fn from_mcp_params(params: &Value) -> Result<Self>

Convert MCP parameters to the CLI argument struct