Struct CreateSpecArgs 

pub struct CreateSpecArgs {
    pub project_name: String,
    pub feature_name: String,
    pub spec: String,
    pub notes: String,
    pub tasks: String,
}

Arguments for create_spec command

Fields

project_name: String

Project name to create spec for

Must be an existing project in ~/.foundry/ Use ‘foundry list-projects’ to see available projects

feature_name: String

Feature name in snake_case (e.g., user_authentication)

Used to create timestamped directory: YYYYMMDD_HHMMSS_feature_name Should be descriptive and use underscores, not spaces or hyphens

spec: String

Detailed specification content

Required Sections:

• Feature overview and purpose
• Functional requirements and acceptance criteria
• Technical implementation approach
• Testing strategy and edge cases
• Dependencies and constraints

Markdown Structure:

• Use # Feature Name as main header
• Use ## for major sections (## Overview, ## Requirements, ## Implementation)
• Use ### for subsections (### API Design, ### Database Changes)
• Include code blocks with ```language for examples
• Use bullet points and numbered lists for clarity
• Add tables for complex requirements or APIs

Goes into spec.md

notes: String

Implementation notes and considerations

Content Focus:

• Design decisions and rationale
• Technical tradeoffs and alternatives considered
• Dependencies on other features or systems
• Implementation constraints and limitations
• Future enhancement opportunities

Markdown Structure:

• Use ## headers for categories (## Design Decisions, ## Dependencies, ## Constraints)
• Use bullet points for lists of considerations
• Include code snippets for technical details
• Reference external documentation with links
• Keep it conversational but technical

Goes into notes.md

tasks: String

Task list content

Task Organization:

• Break feature into actionable, testable tasks
• Group related tasks under logical phases or components
• Include both implementation and validation tasks
• Consider setup, development, testing, and deployment phases

Markdown Checklist Format:

• Use ## headers for phases (## Phase 1: Setup, ## Phase 2: Core Implementation)
• Use - [ ] Task description for uncompleted tasks
• Use - [x] Task description for completed tasks
• Include estimated effort or complexity where helpful
• Add sub-tasks with indented checkboxes when needed
• Keep tasks specific and measurable

Goes into task-list.md

Trait Implementations

impl Args for CreateSpecArgs

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 CreateSpecArgs

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

Formats the value using the given formatter.

impl FromArgMatches for CreateSpecArgs

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 CreateSpecArgs

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