Sepehr 1fdfefe631 Initial commit: BMAD framework + Story 1.1 Component Trait Definition

Features:
- BMAD (Build Modular AI-driven Development) framework setup
- BMM, BMB, CIS, Core modules configured
- Story 1.1: Component trait with error handling
- Workspace Cargo.toml with components crate
- 31 tests passing (19 unit + 12 doc tests)

Technical:
- Component trait with compute_residuals, jacobian_entries, n_equations
- ComponentError enum with thiserror
- JacobianBuilder for sparse matrix construction
- Object-safe trait supporting Box<dyn Component>
- Comprehensive documentation and examples

2026-02-14 13:54:04 +01:00

2.4 KiB

Raw Permalink Blame History

name	description	nextStepFile
step-02-context-gathering	Quick context gathering for direct mode - identify files, patterns, dependencies	./step-03-execute.md

Step 2: Context Gathering (Direct Mode)

Goal: Quickly gather context for direct instructions - files, patterns, dependencies.

Note: This step only runs for Mode B (direct instructions). If {execution_mode} is "tech-spec", this step was skipped.

AVAILABLE STATE

From step-01:

{baseline_commit} - Git HEAD at workflow start
{execution_mode} - Should be "direct"
{project_context} - Loaded if exists

EXECUTION SEQUENCE

1. Identify Files to Modify

Based on user's direct instructions:

Search for relevant files using glob/grep
Identify the specific files that need changes
Note file locations and purposes

2. Find Relevant Patterns

Examine the identified files and their surroundings:

Code style and conventions used
Existing patterns for similar functionality
Import/export patterns
Error handling approaches
Test patterns (if tests exist nearby)

3. Note Dependencies

Identify:

External libraries used
Internal module dependencies
Configuration files that may need updates
Related files that might be affected

4. Create Mental Plan

Synthesize gathered context into:

List of tasks to complete
Acceptance criteria (inferred from user request)
Order of operations
Files to touch

PRESENT PLAN

Display to user:

**Context Gathered:**

**Files to modify:**
- {list files}

**Patterns identified:**
- {key patterns}

**Plan:**
1. {task 1}
2. {task 2}
...

**Inferred AC:**
- {acceptance criteria}

Ready to execute? (y/n/adjust)

y: Proceed to execution
n: Gather more context or clarify
adjust: Modify the plan based on feedback

NEXT STEP DIRECTIVE

CRITICAL: When user confirms ready, explicitly state:

y: "NEXT: Read fully and follow: step-03-execute.md"
n/adjust: Continue gathering context, then re-present plan

SUCCESS METRICS

Files to modify identified
Relevant patterns documented
Dependencies noted
Mental plan created with tasks and AC
User confirmed readiness to proceed

FAILURE MODES

Executing this step when Mode A (tech-spec)
Proceeding without identifying files to modify
Not presenting plan for user confirmation
Missing obvious patterns in existing code

2.4 KiB Raw Permalink Blame History